开发者_C百科Plone 4 contains a new folder implementation (in the plone.app.folder package) which is much more efficient for folders with many items. Is it possible to upgrade a Plone 3 site to use this folder implementation without doing a full upgrade of the site to Plone 4?
If so, what steps are required to do so? Any caveats I should be aware of?
I just tested a Plone 3.3.5 site with plone.app.folder==1.0.3 (newer version depends on Products.CMFPlone, i.e. Plone 4).
Extend a Plone 3 buildout with this one:
[buildout]
extends =
your-plone3-buildout.cfg
eggs +=
plone.app.folder==1.0.3
[instance]
zcml +=
plone.app.folder
zcml slug is important because plone.app.folder doesn't use z3c.autoinclude.
After running buildout and launching your instance, install the products as a regular Plone product and migrate existing folder by opening this URL:
http://localhost:8080/plone/@@migrate-btrees
You'll get an output like this one:
2011/03/03-17:24:31 migrating btree-based folders from <PloneSite at /plone>:
2011/03/03-17:24:32 intermediate commit (0 objects processed, last batch in 0.289s)...
2011/03/03-17:24:32 processed 0 object(s) in 0.289s (0.290s cpu time).
Hope this helps
We used the Plone 4 folders in a Plone 3 site when they were under development, but i don't know if recent development for them have made them depend on other parts of Plone 4.
We still have them running in Plone 3 sites in production, so it is possible.
Not a clue. But Plone 3 has a "Large Folder" which also is based on BTrees and handles large folders well. It's not as slick though. I would use that one under Plone 3, I like to keep my Plone sites as standard as is humanly possible. :-)
精彩评论