Using the standard include page macro with scroll versions produces mixed results. Sometimes the included pages appear, regardless of version no.; other pages do not work; a message appears indicating the included page cannot be found. What am I doing wrong?
Scroll Versions bundles an extension to the standard include macro which is called include+ . Only the include+ macro is able to resolve the correct version of an included page. I think this explains the 1st of your described results.
The other issues might be related to standard include issues tracked by Atlassian such as CONF-24785. With the introduction of allowing special keys such as % / @ : in Confluence page titles the standard include macro was not adopted... As the include+ renders the resolved page version using the standard include macro internally, the macro is impacted by almost the same issues. However Scroll Versions already bundles a fix for ':'.
I am not sure if my answer point you to the right direction... so it might be a good idea to contact the support team (email@example.com).
Thank you Tobias, I think you are saying that I should use the include plus macro and not the standard page include, and that I should avoid any special keys in page titles except for ':'. Is that right? I have sent a request to support team regarding trouble with the include plus macro; it is not working at all; produces a 'error loading children' message.
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs