Creating new TranslatablePage gives: keyerror: 'canonical_page'
See original GitHub issueMy issue is basically identical to #54 but I’m using Wagtail 2.0.1, WagtailTrans 2.0.1 and Django 2.0.4.
Followed the docs precisely and I have these as my settings:
WAGTAILTRANS_SYNC_TREE = False
WAGTAILTRANS_LANGUAGES_PER_SITE = True
As far as I can tell, the fixes from pull 55 are still in place though. https://github.com/LUKKIEN/wagtailtrans/pull/55/commits
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Creating new TranslatablePage gives: keyerror ... - GitHub
From an empty database, I have performed migrations and created a ... Creating new TranslatablePage gives: keyerror: 'canonical_page' #54.
Read more >Why do I get a KeyError? - Stack Overflow
You forgot a comma: urls = ( '/', 'index' # ^ '/runs', 'runs' ). Without the comma, Python concatenates the two consecutive strings, ......
Read more >A language switch for multilingual Wagtail sites - PythonEatsTail
Creating a language switch that returns to the home page in the ... except KeyError: # if for some reason the previous page...
Read more >5 common mistakes with rel=canonical - Google Developers
Conclusion. To create valuable rel=canonical designations: Verify that most of the main text content of a duplicate page also appears in the canonical...
Read more >Canonical Tags: A Simple Guide for Beginners - Ahrefs
Google, Microsoft and Yahoo united to create them. ... If new pages tend to be crawled the same day they're published, crawl budget...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In case anyone else stumbles across this, I found the cause. One of the mixins we use modifies the settings tab on the Wagtail edit page, half way through this we were getting the settings panels from Page
settings_panels = Page.settings_panels
to inject our own. Switching this to load them fromTranslatablePage
fixes it.I knew it would be my own fault 😉
That’s good to hear! Thanks for coming back to this, let us know if you’re running into any other issues!