This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
[BUGFIX] Add current hostname to "additionalParametersForChash" (#47) #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…um#47) The internal chash cache (database table tx_realurl_chashcache) maps a given combination of query string and query parameters to a single chash value. It's intended to not recalculate chashe values when resolving GETvars from SEO URLs but to just look them up. This can conflict when common non-page records should be displayed on different detail pages on different root pages that share the same language and by accident the same page path to the detail page.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The internal chash cache (database table tx_realurl_chashcache) maps
a given combination of query string and query parameters to a single
chash value. It's intended to not recalculate chashe values when
resolving GETvars from SEO URLs but to just look them up.
This can conflict when common non-page records should be displayed on
different detail pages on different root pages that share the same
language and by accident the same page path to the detail page.