Skip to content
Discussion options

You must be logged in to vote

Fixed in v0.129.4. Please reload (or upgrade) the CMS and the issue should be gone.

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
1 reply
@kyoshino
Comment options

Comment options

You must be logged in to vote
1 reply
@wabarr
Comment options

Answer selected by kyoshino
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants