Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration option for lookUpTable.useUniqueCache_conf.spaceCharacter is missing #530

Open
cumuru opened this issue Sep 13, 2017 · 0 comments

Comments

@cumuru
Copy link

cumuru commented Sep 13, 2017

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant