-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Add support for language exclusion in sitemap.xml #7778
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
Open
bambuca
wants to merge
3
commits into
nopSolutions:develop
Choose a base branch
from
bambuca:feature/7777-sitemap-exclude-languages
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code does not need to be removed. By default, the main address is the address without localization
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the feedback! However, I'd like to clarify why we replaced this part:
with this one:
Why this change?
Even though the original version uses
getRouteParamsAwait(null), thatnulldoes not eliminate language context. In fact:LanguageIdis passed explicitly (e.g.,news.LanguageId).GetSeoRouteParamsAwait(...), theLanguageIdis not provided, and the system falls back to the current language fromIWorkContext, resolved in_urlRecordService.GetSeNameAsync(...).This makes the result dependent on the active user/session, which is undesirable for sitemap generation.
In addition to that, the default
IOutboundParameterTransformerimplementation inLanguageParameterTransformer.csalso:RouteValuesIWorkContextThis behavior is not fully deterministic and leads to inconsistencies in the resulting URLs.
That’s why we explicitly select a
languagefor sitemap URL generation:And finally, we use this condition:
to ensure the generated URL reflects the explicitly chosen language, overriding whatever may have been implicitly applied via
IOutboundParameterTransformer.This guarantees that all sitemap entries are generated consistently and intentionally, regardless of the current user context or route state.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I understand your idea and the problem you are solving, but it is not related to the ticket itself. Let's create a separate ticket and a separate pull request for this task. I will review everything again. As for the task #7777 itself, we decided not to implement it in the core for now