-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to remove or show an uploaded *invisible* theme? #107
Comments
I think this a duplicate from plone/Products.CMFPlone#1622. |
Yes, @3dogMcNeill and I were trying to figure this out this morning. She filed the software issue and I filed the documentation issue, but now I'm trying to be thorough and cover all the other related problems. This is related to her issue, but not (I think) a duplicate. |
It's only possible to recover from the bug by remembering which URL to browse to. There should be a way for @@theming-controlpanel to show all themes, even if they don't have a manifest.cfg. Or, I guess, fix the bug so it's not possible to upload a theme without manifest.cfg or to auto generate a manifest.cfg, but that still leaves some people in the position of having an invisible theme that prevents them cryptically/silently from uploading a new theme with the same name. |
The theme is only invisible because manifest.cfg isn't there, so if it gets autogenerated I believe we won't have the silent fail anymore. There's no "invisible theme" concept. Btw another way to recover is going to /portal_resources and deleting the "theme/YOURTHEME" folder. |
Probably the upload mechanism needs to create a default |
Could replicate this code that creates a |
There is a template generation of manifest file. This solves the problem? |
I started a PR to do the checking for a manifest.cfg and to add a default one if it is missing. Not sure when I can finish it. |
related to #105, I have a site in which I uploaded a barebones theme but because it is missing manifest.cfg I don't see it in the top-level @@theming-controlpanel and cannot therefore remove it.
...if I retained browser history I can go back to /++theme++MYTHEMEID/@@theming-controlpanel-mapper
The text was updated successfully, but these errors were encountered: