Commit 5757d6e1 authored by Andreas Jung's avatar Andreas Jung

documentation for manage_convertIndexes

parent 8547d5c0
...@@ -395,7 +395,8 @@ Zope Changes ...@@ -395,7 +395,8 @@ Zope Changes
- Collector #1595: same as in Collector #1132 for indexes derived from - Collector #1595: same as in Collector #1132 for indexes derived from
UnIndex. Exisiting ZCatalog instances must be converted manually UnIndex. Exisiting ZCatalog instances must be converted manually
by calling the "manage_convertIndexes" method through-the-web for by calling the "manage_convertIndexes" method through-the-web for
every single ZCatalog instance. every single ZCatalog instance. See also doc/FAQ.txt (Installation,
question #4)
- Collector #1457: ZCTextIndex's QueryError and ParseError - Collector #1457: ZCTextIndex's QueryError and ParseError
are now available for import from untrusted code. are now available for import from untrusted code.
......
...@@ -194,6 +194,33 @@ Zope Installation Frequently Asked Questions ...@@ -194,6 +194,33 @@ Zope Installation Frequently Asked Questions
(yay) it's var/z2.pid, for pcgi (not so yay), it's (yay) it's var/z2.pid, for pcgi (not so yay), it's
var/pcgi.pid. var/pcgi.pid.
4. After moving my old Data.fs to Zope 2.8 I get an
"AttributeError, _length" when trying to use the ZCatalog?
In Zope 2.8 we cleaned up the index implementations and therefore
you need to migrate every single ZCatalog manually:
- go to the ZMI
- click on your ZCatalog instance (or portal_catalog inside
your CMF or Plone instance)
- you will get an "AttributeError, _length"...don't panic
- call the "manage_convertIndexes" method of the ZCatalog
(by replacing the "manage_main" part of the URL with
"manage_convertIndexes")
- depending on the size of your ZCatalog the migration may
take a while
- after the conversion a message will appear: "Indexes
converted and reindexes"
- Notice: **YOU SHOULD BACKUP YOUR var/Data.fs file before
starting the migration**
General General
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment