Hi folks - we used to use the old Confluence CamelCase option, but turned it off a couple of years ago. The CamelCase option created thousands of Undefined Pages in our instance, and those remained even after we turned off the feature.
Now we're upgrading from v3.5 to v5.5, and reviewing what's being brought across. I was surprised to see that the thousands of Undefined Pages are still there; I figured (hoped?) this would be something that was cleaned up in the migration scripts.
Has anyone else faced this issue? Any clever ways of cleaning up this mess?
What type of upgrade have you tried? I'd be interested to see if it brought over the pages in an XML backup/restore upgrade path.
If yes, I'd be inclined to say they are going to stick around. The best option is probably going to be a manual solution...
I imagine they are doing in place upgrades then. There are likely a couple options to clean up the undefined pages - manually via database queries or manually via modifying an xml backup.
When you say "undefined pages" - can you elaborate? How are you identifying these pages? In the UI? or in the database? What constitutes a page being undefined?
Hi my Community friends! For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...
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