• Thank you for a very nice plugin! What would make it even better for my use case is if I was able to filter all settings both on the plugin- and the form-level.

    For example if I know that nonces will not work due to caching or GDPR affects if submissions should be saved or not. Instead of having to make sure I change the settings in the GUI and still risk that the client changes them back, it would be nice to be able to set them using code, thus preventing unwanted side effects from erroneous setting values.

    If added, the related setting in the GUI should either be removed or disabled. And maybe a note saying that the setting is controlled using code.

    I am up for helping adding it and/or discussing further if you want to.

Viewing 1 replies (of 1 total)
  • Plugin Support bjplink

    (@bjplink)

    I’ll need to think about it some more. If I understand you correctly, the simplest way would be to add a filter for settings. Then you could override anything you want, and the settings UI would just naturally follow course (and ignore any user changes). Again, I’m not sure if that’s something I want to add, but I will give it some thought. Thanks for your feedback.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.