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
Configuration option for lookUpTable.useUniqueCache_conf.spaceCharacter is missing in 2.x.
This was a feature in 1.x which was dropped for the 2.x rewrite. While one could argue if it makes sense to configure spaceCharacter different from the 'global' space character the missing feature blocks updates to 2.x when it‘s set.
I know of #271 where the documentation for the feature was dropped but that does not solve the problem.
I suggest to reimplement the old behaviour. Should be easy and have no impact on performance (because it‘s cached anyway).
Possible workarounds:
Move to new URIs and do rewrites (downside: adds load to every request, can be tricky)
Implement own encodeTitle_userProc which isn‘t nice either
The text was updated successfully, but these errors were encountered:
Configuration option for
lookUpTable.useUniqueCache_conf.spaceCharacter
is missing in 2.x.This was a feature in 1.x which was dropped for the 2.x rewrite. While one could argue if it makes sense to configure
spaceCharacter
different from the 'global' space character the missing feature blocks updates to 2.x when it‘s set.I know of #271 where the documentation for the feature was dropped but that does not solve the problem.
I suggest to reimplement the old behaviour. Should be easy and have no impact on performance (because it‘s cached anyway).
Possible workarounds:
encodeTitle_userProc
which isn‘t nice eitherThe text was updated successfully, but these errors were encountered: