Avoiding 'Illegal shortcode state' (Hugo v0.102.2)#1211
Merged
deining merged 2 commits intogoogle:mainfrom Sep 2, 2022
Merged
Conversation
df77087 to
91d543d
Compare
91d543d to
c8fb9b3
Compare
Contributor
Author
|
Rendering of user guide failed due to a regression introduced in hugo v0.102.0, fixed with recently released version hugo v0.102.3. |
Collaborator
|
Agree it's easier to read - I think we have some stuff in shortcodes (not sure about this one) that were added for compatibility with multiples of versions of Hugo ago. |
Collaborator
|
This version renders properly with the previous version of Hugo, right? |
Contributor
Author
Yes, it I tested it with hugo v0.101 and v0.102.x, and the result was always fine. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR avoids an Ìllegal shortcode state`, thrown by Hugo version 0.102.x