Uninstalling Silva Layout does not remove silva-layout metadata set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Silva |
Fix Released
|
Undecided
|
Eric Casteleijn |
Bug Description
After uninstalling Silva Layout and removing it from the Products directory an Attribute Error will be returned when accessing the tab_settings (tab 'properties' > button 'settings...') of the Silva root or a publication. This is probably due to the fact that uninstalling Silva Layout does not remove its metadata sets 'silva-layout' and 'silva-
Traceback (innermost last):
Module ZPublisher.Publish, line 112, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 40, in call_object
Module Shared.
Module Shared.
Module Products.
Module Products.
Module Products.
- <FSPageTemplate at /dlcms/
Module TAL.TALInterpreter, line 206, in __call__
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 424, in do_optTag_tal
Module TAL.TALInterpreter, line 406, in no_tag
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 711, in do_useMacro
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 734, in do_defineSlot
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 426, in do_optTag_tal
Module TAL.TALInterpreter, line 411, in do_optTag
Module TAL.TALInterpreter, line 406, in no_tag
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 677, in do_condition
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 426, in do_optTag_tal
Module TAL.TALInterpreter, line 411, in do_optTag
Module TAL.TALInterpreter, line 406, in no_tag
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 426, in do_optTag_tal
Module TAL.TALInterpreter, line 411, in do_optTag
Module TAL.TALInterpreter, line 406, in no_tag
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 711, in do_useMacro
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 426, in do_optTag_tal
Module TAL.TALInterpreter, line 411, in do_optTag
Module TAL.TALInterpreter, line 406, in no_tag
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 426, in do_optTag_tal
Module TAL.TALInterpreter, line 411, in do_optTag
Module TAL.TALInterpreter, line 406, in no_tag
Module TAL.TALInterpreter, line 250, in interpret
Module TAL.TALInterpreter, line 477, in do_setLocal_tal
Module Products.
- URL: file:Silva/
- Line 17, Column 2
- Expression: <PythonExpr view.get_
- Names:
{'container': <DirectoryViewS
'context': <DirectoryViewS
'default': <Products.
'here': <DirectoryViewS
'loop': <Products.
'modules': <Products.
'nothing': None,
'options': {'args': ()},
'repeat': <Products.
'request': <HTTPRequest, URL=http://
'root': <Application at >,
'template': <FSPageTemplate at /dlcms/
'user': admin}
Module Products.
- __traceback_info__: view.get_
Module Python expression "view.get_
Module Products.
Module Shared.
Module Shared.
Module Products.
Module None, line 91, in get_metadata
- <FSPythonScript at /dlcms/
- Line 91
Module Products.
Module Products.
Module Products.
Module Products.
Module Products.
Module Products.
Module Products.
- Expression: <PythonExpr [('not set (acquire setting)', '')] + modules[
- Names:
{'default': <Products.
'field': <ListField at /dlcms/
'form': <MetadataElement at /dlcms/
'here': <MetadataElement at /dlcms/
'loop': <Products.
'modules': <Products.
'nothing': None,
'repeat': <Products.
'request': <HTTPRequest, URL=http://
Module Products.
- __traceback_info__: [('not set (acquire setting)', '')] + modules[
Module Python expression "[('not set (acquire setting)', '')] + modules[
AttributeError: 'module' object has no attribute 'SilvaLayout'
Changed in silva: | |
milestone: | none → 2.0 |
status: | Fix Committed → Fix Released |
Unfortunately there's no API in place to easily remove metadata sets. Usually that's no problem, because by themselves they really shouldn't be doing anything. I think that's the case here too, and there's something else that's not removed that is triggering this. Looking at that now.