You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using 8.0.0b1 (with a few patches on top) and when trying to upgrade to latest stable (8.4.2) we are getting the usual KeyError from plone.registry as prefix_wildcard option was added on #271.
As there is no upgrade step, when one updates their website with a newer version of c.solr all usages of Solr are broken until one manually creates the record 😕
Since #271 is already 2 and a half years old and it has been in a release since 8.2.0 I guess this is way too old news? 🤔
Testing it locally one can create a fake record prior to upgrading to +8.2.0:
fromploneimportapifromplone.registryimportRecordfromplone.registry.fieldimportBoolregistry=api.portal.get_tool('portal_registry')
key='collective.solr.prefix_wildcard'# the registry has a prefix, see https://github.com/collective/collective.solr/blob/main/src/collective/solr/profiles/default/registry.xml#L3registry.records[key] =Record(Bool(title=''), False)
After running this, one can then safely update to +8.2.0 🎉
The text was updated successfully, but these errors were encountered:
We are using 8.0.0b1 (with a few patches on top) and when trying to upgrade to latest stable (8.4.2) we are getting the usual
KeyError
from plone.registry asprefix_wildcard
option was added on #271.As there is no upgrade step, when one updates their website with a newer version of c.solr all usages of Solr are broken until one manually creates the record 😕
Since #271 is already 2 and a half years old and it has been in a release since 8.2.0 I guess this is way too old news? 🤔
Testing it locally one can create a fake record prior to upgrading to +8.2.0:
After running this, one can then safely update to +8.2.0 🎉
The text was updated successfully, but these errors were encountered: