We migrated the spaces form server to Cloud. In the migrated pages the forward slash on migrated pages is not working and only the { sign. When we generate a new page, the forward slash is working.
Most probably your pages still use the old editor. This happens often for complex pages which have lots of nested bodied macros
Good day @Michel Feddema.
Adding here to Alex Medved's reply. The most likely cause is due to the migrated pages still using the old editor (default in Data Center), and which is still partly supported in the Cloud (to prevent broken content after migrating).
Here, you can convert these pages to the new editor (default now in Cloud) to ensure they work with the slash key.
Hope this helps.
With friendly regards
Rodrigo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Take a look here: https://community.atlassian.com/t5/Confluence-questions/forward-slash-shortcut-isn-t-functioning/qaq-p/2746070
Also are these Confluence pages linked with some of your Jira issues? If yes, you would need to contact Atlassian support in order for them to apply the new links for your Confluence pages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.