In order to change the author of a page/blogpost you will need to apply some database manipulation as there's no straightforward method to achieve that currently:
Just be sure to take a database backup and involve your DBA in this process before changing anything.
note: this is still a feature request that is being tracked in http://jira.atlassian.com/browse/CONF-4063, feel free to cast your vote there and add yourself as a watcher to receive further updates.
Hope it helps!
Here is a recent process I used to transfer page and space ownership so I could delete particular users from Confluence:
Here's the workaround for this. It's not pretty. This must be done as admin and backup of current config is highly recommended.
Hi all, the way this is done has changed somewhat in recent versions. Please see this page for detailed instructions: https://confluence.atlassian.com/display/CONFKB/How+to+change+the+creator+of+a+page
This is not accurate any longer either as the database schema has changed and the update content set creator = (select user_key from user_mapping where lower_username = '<lowerusername>')
doesn't work as it now uses user_key references instead of the actual username. Even then I've seen no proof on my system that it actually updates the creator of the page on the ones I've tried.
I created some confluence projects and then shortly after migrated them to crowd and wanted to change the ownership of the users from the confluence internal to the crowd user. I didn't really like the idea about messing about with SQL queries (even though I am a developer so quite happy with SQL). In the end what I did was export the entire space as XML, delete the space. Then edit the XML (keeping a backup in case you mess this up!) and change the ownership persmissions, the structure is fairly obvious, I had renamed the internal users to have an "_confluence" suffix so I identified those user ids and globally search replaced them with the new user I wanted them to have. I did this on about 10 spaces and it worked fine. The only problem was that sometimes I would end up with duplicate "touched" entries if the new user had touched a file that the old one had, my answer to this is simply to delete any "touched" entries which were problematic, and failing that just delete all of them. I guess I'll lose popular and recently viewed history but that didn't really matter to me.
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
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