List of Issues and FAQ for magnolia 2.0 (Build 041110)
- Magnolia ceases to publish after superuser password change without activation of the changes
- Problem: If one changes a user's password without activating the change then the password will differ between the different instances (author and public). It is a feature that if the passwords differ, the user in question will not be able to activate. The superuser account is treated exactly the same, which means that if you have only one account that has the rights of a superuser, and change the password of that account, then close the browser, you will not be able to activate these changes later on.
- Workaround (if any): One thing you can do is to have more than one user, so that you have a backup in case something goes wrong, but that is only a very basic backup. Instead, if you forgot to activate the changes of credentials, you should change the password on the authoring server back to the old password (the same password that the subscribed servers have), then close the browser (thus ending your session with the Magnolia authoring environment) and log in again with the former password. This means that the original state is reached, where all systems have the same password. Now change the password to the new one and activate the change. We could warn about this behaviour in the install readme file. See also http://jira.magnolia.info/browse/MAGNOLIA-190.
- I would propose an Javascript alert. That's guaranteed to be seen!
- Magnolia stores its data on the filesystem. Why doesn't it use an RDBMS instead?
- Magnolia uses a Java Content Repository (JCR) as defined by JSR-170. How the JCR stores the information is not defined, left up to the implementation and should not matter. Magnolia is currently using Apache Jackrabbit
In its previous incarnation on JspWiki, this page was last edited on Feb 9, 2007 10:25:05 AM by 212.38.183.156
Other known authors include :
