You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am currently trying to find a way to switch from metadata macro to page properties macro.
Basically Comala metadata is used with scroll versions in exporting confluence pages. We use metadata for placeholders, for example: "<documentcontributor> = John" in confluence page; and in the scroll export templates: "$metatada.documentcontributor" (the exported page will show John).
Therefore, we would like to replace all the existing pages, that we have in our Confluence Data Centre, which include metadata macros to page properties. Manual change is not optional as we have more than 5000 pages that make use of this functionality.
We have a database query that changes the bodycontentid from ac:name="metadata"' to 'ac:name="details" (page properties) however, this occurs at DB level, and via API the change is visible, but within the confluence page GUI, it still shows metadata plugin.
Information on the macro:
Comala Metadata: https://marketplace.atlassian.com/apps/5295/comala-metadata?hosting=datacenter&tab=overview
Installed version: 3.5.6
Page Properties: default with Confluence
Thanks in advance!
@Jael Busuttil I believe the reason you are not seeing the changes in the actual application is because of the content indexes. If you have a test instance you could make the DB change there and then rebuild the content index to see if this fixes the issue. https://confluence.atlassian.com/confkb/how-to-rebuild-the-content-indexes-from-scratch-on-confluence-server-110035351.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.