Please do, we should be using the unrestricted
CMFPlone.utils._createObjectByType and *not* invokeFactory.
Stefan
On 9. Nov 2005, at 19:38, Rene Pijlman wrote:
I'm repeating this message that I posted when the setup list had
only just started.
I'd appreciate some advice from one of the experts whether it's
useful to report this problem in the issue tracker.
Rene Pijlman:
[2.0.5 > 2.1.1]
The upgrade from 2.1-rc2 fails with: "Error value: Disallowed
subobject type: Topic". The entire trace is below.
I found the solution: in the ZMI, I opened portal_types of my Plone
2.0.5 site, clicked "Plone Site", and in the listbox next to "Allowed
content types" I selected "Topic". After that the upgrade succeeded.
I'm not sure if this is a bug in the upgrade process. AFAIK I never
used Topics because of the opinion in The Definitive Guide To Plone
("topics are quite complicated, have a rather unfriendly interface,
and are recommended for only advanced users"). It's a petty the
upgrade
fails on a piece of functionality that was never used in the pre-
upgrade site.
If it's necessary for the upgrade to create topics in the portal
root,
I guess it can be made more robust by allowing this type in type
Plone
Site, or requiring the user more explicitly to allow it before the
upgrade runs. Does it make sense to report this in the Plone issue
tracker?
--
Rene Pijlman
http://www.applinet.nl/
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
--
Anything that happens, happens. --Douglas Adams
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
