dorsetdigital

The rate-limiting should work with just configuration.. I don't think you'll need any custom code

dorsetdigital

You could use the proper SilverStripe rate limit middleware, or even just do something as simple as set a submission time in the session, and check against it to make sure multiple requests aren't being sent

dorsetdigital

If it's deliberate, then you need to be more aggressive in the approach, and some kind of rate limiting might be in order

dorsetdigital

If it's impatience, then some improved user feedback and disabling the button would probably cure it.

dorsetdigital

It depends what you're protecting against. Is it deliberate, or just user impatience?

dorsetdigital

Maybe I haven't understood what you're trying to do

klemen

I’d like a config file inside a theme folder. I am guessing they’re processed in the root (module) folders. So I need to get the active theme and see if the file is there, and parse it via the API.

dorsetdigital

Have you tried adding a _config directory to the theme and putting it in there?

dorsetdigital

Isn't that how the configuration system works anyway? If a file is there it will be processed