-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Neos.Seo: TASK: Improve ESCR Compatibility #171
Labels
Comments
Already known issue with Neos 9.0: Solution: |
ahaeslich
moved this from Prioritized for Sprint
to In Progress
in Neos 9.0 Release Board
Mar 7, 2023
ahaeslich
changed the title
9.0 TASK: Improve ESCR Compatibility
9.0 FEATURE: Improve ESCR Compatibility
Mar 8, 2023
ahaeslich
changed the title
9.0 FEATURE: Improve ESCR Compatibility
9.0 TASK: Improve ESCR Compatibility
Mar 11, 2023
skurfuerst
changed the title
9.0 TASK: Improve ESCR Compatibility
9.0 TASK: Improve ESCR Compatibility of Neos.Seo
Mar 31, 2023
skurfuerst
changed the title
9.0 TASK: Improve ESCR Compatibility of Neos.Seo
Neos.Seo: TASK: Improve ESCR Compatibility
Mar 31, 2023
ahaeslich
added a commit
to neos/Neos.Demo
that referenced
this issue
Apr 1, 2023
…ed header To activate the language in the dropdown menu the refactored header relies on the generation of alternate language links which are generated via `Neos.Seo` package. Relates: neos/neos-seo#171
ahaeslich
added a commit
to neos/Neos.Demo
that referenced
this issue
May 1, 2023
…ed header To activate the language in the dropdown menu the refactored header relies on the generation of alternate language links which are generated via `Neos.Seo` package. Relates: neos/neos-seo#171
github-project-automation
bot
moved this from In Progress 🚧
to Done ✅
in Neos 9.0 Release Board
May 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current v4 branch was introduced for Neos 9.0.
ToDo's:
node.context
usages 9.0: FEATURE: Improve ESCR Compatibility - Part 1 #172robots.txt
to properly use ESCRXmlSitemapUrlsImplementation
to use the ESCR api FEATURE: Refactor XmlSitemap and robots.txt to work with the new ESCR #173Related issues / pull request in neos/neos-development-collection to support all features again:
node.context.inBackend
andnode.context.isLive
neos-development-collection#4074Neos.Dimension
helper neos-development-collection#4085Neos.Dimension
helper functions to returnContentDimensionValue
neos-development-collection#4249The text was updated successfully, but these errors were encountered: