I would like to suggest the introduction of some kind of user-accessible validator.
My suggestion by example:
Right now I have some views, some panels etc. which have been created some time ago. Ctools, panels and views has been updated in the meantime and everything seemed to work well. Now I decided to create new view panes and insert them into existing panel pages. Unfortunately something breaks, the views panes are displayed as missing/broken and even the existing pane from the same view is affected. This is not the first time something like this occurred to me, where I cannot directly link a certain update at date X to a problem at date Y.
From my perspective its a real pain, but I guess it is the price you pay when you use dev versions. The real problem is different: to recreate everything and find out whether it was panels, views or the exported code which is now inserted by hooks from my code takes hours. I cannot see, what the reason was, everything broke down, but I can imagine it was just some missing variable or minor field change conflicting with the data saved in the DB or in code. Probably this would not be to difficult to fix directly inside the database instead of going through the whole delete and recreate thing again.
My suggestion is to create some tests for common tasks on the data (eg. read the schemes provided by the hook_default_* or stored in the DB), perform some non-data-altering operations and display any warnings.
The expected benefit is that administrators can detect errors introduced by various updates and versions directly instead of having to recreate the whole stuff.
Comments
Comment #1
japerryClosing this issue as outdated as Drupal 6 ctools is not supported. If this issue is relevant for Drupal 7, feel free to re-open and mark for Drupal 7 (or 8)