I wasn't sure if this issue should be here or in plone.behavior, but since the problem resides in a file that's inside profiles/default/types I'm posting it here.
What I did:
1 - Created a new Plone 5.2 package using plonecli. Add a default content_type setting all default behaviors.
2 - Ran plonecli build and bin/instance fg in the new created package.
3 - Installed the new Plone package in plone control panel.
4 - Stopped the instance.
5 - Edited the type xml in the package leaving just one behavior and the purge=false attribute.
6 - In the ZMI, reinstalled the package (I know this practice is deprecated, but it's easier to test the problem in this issue).
What I expect to happen:
Viewing the portal_types for this content type in the ZMI should show all behaviors when I installed the package in the first place.
What actually happened:
It's showing only one behavior, the one that I left on 5 above.
What version of Plone/ Addons I am using:
The first time I saw this problem was in a Plone 4.3.18 installation, but I did the test in the last Plone version, 5.2:
BUG/PROBLEM REPORT (OR OTHER COMMON ISSUE)
I wasn't sure if this issue should be here or in
plone.behavior
, but since the problem resides in a file that's insideprofiles/default/types
I'm posting it here.What I did:
1 - Created a new Plone 5.2 package using
plonecli
. Add a defaultcontent_type
setting all default behaviors.2 - Ran
plonecli build
andbin/instance fg
in the new created package.3 - Installed the new Plone package in plone control panel.
4 - Stopped the instance.
5 - Edited the type xml in the package leaving just one behavior and the
purge=false
attribute.6 - In the ZMI, reinstalled the package (I know this practice is deprecated, but it's easier to test the problem in this issue).
What I expect to happen:
Viewing the
portal_types
for this content type in the ZMI should show all behaviors when I installed the package in the first place.What actually happened:
It's showing only one behavior, the one that I left on 5 above.
What version of Plone/ Addons I am using:
The first time I saw this problem was in a Plone 4.3.18 installation, but I did the test in the last Plone version, 5.2:
Products.CMFPlone-5.2.0 plone.app.contenttypes-2.1.2 plone.behavior-1.3.0