resources/page: Fix slugorcontentbasename for section pages #14126
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.
Summary
This PR fixes the
slugorcontentbasenamepermalink token creating an extra subdirectory for section pages (_index.mdfiles).Problem
When using
slugorcontentbasenamein permalinks for section pages, an extra subdirectory was created. For example:With content at
content/foo/bar/_index.md, this would generate/bar/bar/index.htmlinstead of the expected/bar/index.html.The deprecated
slugorfilenametoken worked correctly by returning an empty string for_index.mdfiles.Solution
Added special handling in
pageToPermalinkContentBaseNameto return an empty string for section pages (_index.mdfiles), matching the behavior ofpageToPermalinkFilename.Testing
TestIssue14104to verify the fix🤖 Generated with Claude Code
Fixes #14104