Macros renaming issue

[MS Anjum]

Hi there,
We are using Confluence Server 7.13 on our two separate environments, i.e. Pre-release and Production.
We use the pre-release instance for editing purposes, and export the final content (space) on the production instance for our customers.

The issue we have been facing is that everything runs smoothly on the pre-release environment, but when we export a space to the production instance, all the page macros (be its the built-in ones or our custom user macros) are renamed to "Children Display". Though they work differently as per their type, but when we edit any page, all the macros are shown with the "Children Display" name. Like if we are using 5 different macros on a page, we get to see "Children Display" five times on that page when we edit it.

Is there any turnaround to fix that issue?

Many thanks.

Regards,

Salman

[Nic Brough -Adaptavist-]

How re you doing the "export a space to production"?

Also, when you edit one of the affected pages, how do the macro calls appear in the editor?  Do they display as "children display" as well?

[MS Anjum]

@Nic Brough -Adaptavist- 

We use the "Full XML Export" option from our pre-release instance to create an XML of that space, and then import that XML in the production instance via General Configurations>Backup & Restore. Furthermore, for the XML files that are less than 25MB, we use the Upload a site or space export file section, while for 25MB+ files we use Import from the home directory.

The used macros inside a page work fine on production as per their intended purpose (in non-edit mode), for exp, a Live Search macro allows you to search, a Recently Updated macro shows you recently updated pages, and so on. The problem starts, when we edit a page, all the used macros start appearing as "Children Display". 

Here are the screenshots of a test page:

Non-Edit view of the page

Editor view of the page

  

[MS Anjum]

@Nic Brough -Adaptavist- 

The problem seems weird as we were previously using the Confluence 7.4.12 version on the production and pre-release environments and facing this issue.

But now we are using Confluence 7.13 versions on both the pre-release and production instances.

Before upgrading the production, we cleaned up all the confluence data (database, cache, etc) from the production and went for a fresh installation of 7.13 from the scratch.

And the problem still persists on the production.. :( :)

[Nic Brough -Adaptavist-]

Ok, that is screaming "bug" to me.  (Probably in the import, my guess is that the import is writing the wrong thing into the name of the macro in the page body, and Confluence is then defaulting to showing the name of the first macro it finds).

  I think this needs to go to Atlassian for investigation