Actually, you must delete (or keep it in an other place, in the case it
fails) the /repositories because it's the bootstrapped datas which are
in there. And the goal of the procedure I described is to make Magnolia
re-bootstrap the public instance to take all the new datas.
It's the way I currently update the server version of my modified
Magnolia : backup the datas (all the datas, of all the repositories) in
xml files, then removing the /repositories dir, importing back the xml
in the WEB-INF/bootstrap/common/ and restarting the public instance. It
will bootstrap and re-integrate all the datas (and by the way, you got a
backup with your xml files, which are full compatible with all the
Persistence Manager you'll choose for the future).
Hope that helped,
Anthony
Ben Brock a écrit :
Wow, that's pretty complicated. I hope there's an easier way! This might be a good lead for backing up and restoring users, however. I really would like to do this without manually deleting repositories though.
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: 30 November 2006 16:54
To: [email protected]
Subject: Re: [magnolia-user] changing superuser and securitymanager passwords
What's the problem exactly ?
If it's changing the superuser password, you "just" have to change it while
you're logged in superuser in the Author instance, then,
* go to Tools > Development tools
* select the "users" repository
* "/" as "parent path"
* whatever you like as root dir (in order to find it later)
* Click on "backupChildren"
* Go on the server, get the users.superuser.xml file
* Backup all your datas in the Public instance with that method
(creating xml files)
* Stop the public instance
* Replace the users.superuser.xml of the backed up xml files with
the one from Author
* remove the "repositories" directory and perhaps the datas if your
persistence manager is a DB
* Re-bootstrap the public instance, based on the xml files you backed up
And finally you're done !
... I think there is a simplier way anyway ... :-/
Anthony
Ben Brock a écrit :
I see that this has been covered, but I'm having no luck changing the
password or deactivating the superuser and securitymanager users in
either the Author or Public Instance in 3.0. I had no problems in
2.1.5, so it looks like something's changed. Is this on the Wiki?
1. I'm logged in as a new user assigned the superuser role (I tried as
a security manager as well) 2. /config/server/admin set to true in
both Author and Public 3. subscriber nodes are set to false
Thanks in advance,
Ben
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
