while developing our theme on site with content in already (bad idea, i know) i fiddeled with the creation of a separate viewletmanager in plone.portaltop.
After running into issues, i copied the theme to a separate, fresh plone 4.3.18 install and fixed the issue. The viewletmanager shows up when our theme is installed, and everything goes back to normal when i uninstall our theme and activate a plone default one.
After copying the fixed theme to the production system, the custom viewletmanager does not show up at all. I uninstalled the theme with the old, unfixed version, stopped plone, copied the fixed theme over, restarted plone and installed the theme - the viewletmanager does not show up at all under /@@manage-viewlets. There are no errors showing up on run bin/client1 fg when installing/uninstalling the theme or calling @@manage-viewlets. The viewletmanager with its new viewlets does not show up at all.
My guess is i messed up the plone database with my broken viewlets.xml. Is there a way to clean the database from any generic setup stuff and regenerate everything by executing all gs profile steps in a row ?
We have quite some content in the site. Exporting the content, clean up the instance, an Importing the content i do want to avoid if there is an easier solution in fixing the database in place.
Thanks for any advice. And Keep up the good work !