Alex,
Also, is there a way for the plug-ins to "update" missing config options, while leaving existing ones set? So that if an update to a plug-in is setting up, it tests to see if the config options exist before setting them? To preserve existing settings?
In case you missed the other post, (this has been a fragmented weekend... little sleep)
1) Errors: How can a plug-in report errors to the install program. ie: fields not set, missing user input, conflicting user input, SQL errors, etc.
2) Also, I'm having problems with the _pre and _post hooks. They don't register correctly, so you need to "EDIT" the plug-ins user options, and just "update" them. That ensures they are reset properly. There should be a way to trigger this to make sure things are "updated" before install exits.
3) An official way of adding custom fields to the Admin. Such that, a field can have a meta-data attached that puts a link in the field_name box (the way alternate categories in links 1.1x did). That way, you can trigger a function or operation for a field that may need special setup. In this case, to view an image/link that is attached to the record, but it has wider scope.
4) Adding in directory management similar to FileMan so that routine maint can be done through the server without telnet or permissions conflicts (ie:nobody).
5) Plug-in clean up on aborted (error) installs... it leaves the plugin_name.pm file around in many cases, which causes an error on the next attempted install (plug-in exists but is not registered, or something similar).
6) A pop-up text window for editing the plug-in code, similar to the template editor?? :) The window is awefully small and limited, but it's really cool to be able to make changes. Also, since the changes are made directly-- an option to keep say -- 7 back-ups in case you have to roll back. It's kind of scarey making the changes on-line, then realizing there are no backups and that is your only 'working' copy!
7) There are other little things in getting the plug-ins to communicate (and vice versa) but I'll wait for the docs to see if they are addressed. I traced out the logic and figured some out, but still have lots of questions.:)
PUGDOGŪ PUGDOGŪ Enterprises, Inc.
FAQ: http://pugdog.com/FAQ