As it it quoted here I allow myself to open a new thread because of its importance. The whole extended config handling is related to this.cmb wrote:I refactored the handling of config and text forms for the core and the plugins. The display and saving is now handled by a class hierarchy in cmsimple/classes/FileEdit.php. This greatly reduced the required code, which basically was duplicated in adm.php and pluginloader/index.php; in addition this file is only included, if it is actually required. Additional benefits: both the core and the plugin config etc. now have identical look and feel; it should be easy to introduce any "typed" config (some basics are already in place); it's easy to extend the class hierarchy for special needs of plugins.
What I miss a bit is the message handling. I don't see a success message when a file is updated after form submit. As the page is forwarded after a successfull update it's not so easy to display a message because of the forwarded page.
How about to set a message GET variable in the forward URI/query string? The value of this key could be used as a key for some standard messages (with placeholders). This message could be displayed by the FileEdit->form() method.
Or the key could be a standard key in the plugin tx file.