collective.lineage refactoring
Johannes Raggam <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
hello all, collective.lineage is an awesomely fantastic package to manage subsites. together with some addons lineage.themeselection and lineage.registry it's quite a powerful tool for having more sub plone sites live within a main plone site. power users love this feature. however, it didn't work with dexterity. mostly because of it's dependency on p4a.subtyper, which defined an folderish content type descriptor, which was done pre-plone.folder ages. i needed that to work with dexterity, so i did a refactoring of collective.lineage. here is the pull-request: https://github.com/collective/collective.lineage/pull/23 to upgrade, you have to manually uninstall collective.lineage and p4a.subtyper. i did not write an upgrade step for that. best, johannes raggam -- programmatic web development di(fh) johannes raggam / thet python plone zope development plone framework team member mail: office-//[email protected] web: http://programmatic.pro http://bluedynamics.com ------------------------------------------------------------------------------ _______________________________________________ Plone-developers mailing list Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-developers
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEABECAAYFAlM97sYACgkQW4mNMQxDgAcuWwCfVBEeD6ohUQAWmzA+1LSHkfOU 75UAn1Fcv51FTSOdSJQtFfjR8HmB8yql =Nu50 -----END PGP SIGNATURE-----