Hi!
We have just moved our Cloud instance of Confluence into Self-hosted one and faced with the problem, that macro, that shows children pages doesn't work with the pages, that was migrated. It looks like this:
We concider, that it's a problem with links, cause it can't find the pages. We already made connection between Jira and Confluence, changed everywhere links to new instances, but we don't know how to decide this problem only in Confluence. We cleared cache, made re-index of content, it didn't work. What should we do with it?
Hi @korotichas,
You mentioned that you migrated from Cloud to Self-hosted. So, I have a few questions that might help us better understand your challenges and, perhaps, these questions can help you with that too.
Cheers,
IL.
Answer to your questions:
We migrated to version 7.7.3.
All of pages have children pages, i checked.
I tried using this macro on another page, it still doesn't work with pages, that hsd been migrated from Cloud instance. But it works great with pages, that i added into new instance after migration. I checked source code of page, but still have no ideas why it doesn't work. Source code looks the same in macros.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Even though you mentioned that it works for new pages, another possible reason that I can think of is that it could be either a user macro that was not brought over or a specific module disabled on the managed apps settings page. Typically, messages similar to the one you shared relate to that.
For example, in the screenshot below, the first one is the "Children Display" macro that I disabled the respective module. The second, a user macro that I've created and deleted so that we can see the missing reference.
These are the initial checks that I can think of at this point. I would be interested in hearing what others have experienced around this.
I hope that this can shed some extra light on that but, in the meantime, I would suggest raising a ticket with Atlassian support so that they can check your logs and likely find the actual cause of that.
IL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.