Thread Rating:
07-31-2026, 07:34 PM
Always call rebuild_settings() after changing settings programmatically.
Nice thread, following for the replies.
Nice thread, following for the replies.
07-31-2026, 07:39 PM
Nice plugin, testing it on my dev board now.
Whitelist-based hooks debugging in class_plugins.php helped me a lot.
Interesting — I will have to try that.
Whitelist-based hooks debugging in class_plugins.php helped me a lot.
Interesting — I will have to try that.
07-31-2026, 08:00 PM
The gid=0 trick keeps plugin settings out of the ACP — neat.
07-31-2026, 09:05 PM
Whitelist-based hooks debugging in class_plugins.php helped me a lot.
Thanks for sharing, saved me a lot of time.
Thanks for sharing, saved me a lot of time.
07-31-2026, 09:37 PM
Always call rebuild_settings() after changing settings programmatically.
That hooks explanation finally made it click for me.
Good point, I had not thought of it that way.
That hooks explanation finally made it click for me.
Good point, I had not thought of it that way.
226
23
May 2026
07-31-2026, 10:45 PM
Always call rebuild_settings() after changing settings programmatically.
Thanks for sharing, saved me a lot of time.
Thanks for sharing, saved me a lot of time.
07-31-2026, 11:12 PM
(07-31-2026, 10:45 PM)QuietQuokka Wrote: Always call rebuild_settings() after changing settings programmatically.The gid=0 trick keeps plugin settings out of the ACP — neat.
Always call rebuild_settings() after changing settings programmatically.
I disagree slightly, but I can see where you are coming from.
« Next Oldest | Next Newest »
Users browsing this thread: 1 Guest(s)
