RTE link picker throw error after upgrade to 7.15.0 / 8.1.0
See original GitHub issueAfter upgrading af site on Umbraco Cloud from 7.12.4 to 7.15.0 to RTE link picker seems to throw an 417 (Missing token)
error.
- Select some text in RTE
- Select a node in content tree, e.g.
My Page
. Previously the link picker then showed/my-page
underLink
, but now it shows something like this/{localLink:umb://document/afcc3d4df40d4d1eb8f2c43fdc592b58}
- Submit with the selected node
- When you then set the cursor at the link in the RTE and click link picker (edit), then it show the following error.
/umbraco/backoffice/UmbracoApi/Entity/GetUrlAndAnchors?id=umb://document/afcc3d4df40d4d1eb8f2c43fdc592b58
- status code: 417 Missing token
The link does however seems to work on frontend.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
v8.1.1
Upgrading from older versions ... Bugfixing on the 8.1.0 release. ... 5849 - RTE link picker throw error after upgrade to 7.15.0 /...
Read more >Compare Releases
4905 - Update picker in Multi Node TreePicker to match other pickers ... 5849 - RTE link picker throw error after upgrade to...
Read more >Gliffy Diagrams for Confluence - Version history
CollapsedExpandedCloudConfluence Cloud2023-08-10Minor version update ... CollapsedExpanded8.1.0Confluence Server 5.10.0 - 6.10.32018-06-22Gliffy for ...
Read more >What's New - Playbook Design System
We've updated our PhoneNumberInput so that it's more react-friendly. You can now pass a ref directly to the PhoneNumberInput kit, giving you more...
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 Free
Top 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
Ah that is very unfortunate… sorry about that, have removed the v7 label now. Unfortunately we’re currently only providing security fixes for v7, so this will be a known issue for the rest of the duration for v7.
Ahh, it seems you also have applied the changes in v8. Great, thanks @Shazwazza 👍