In case you need to reinitialize userroles (or other workspace like
config) you may set the magnolia.bootstrap.force property found in
magnolia.properties file. This enforces a flush on the workspace and
bootstraps this workspace only.
Atttention: do not forget the set the property back!
Philipp
I am having some troubles (most likely) with the import process of the
userroles repository. The other repositories that I have
exported/imported (config, website, users, usergroups and dms) work
just
fine. After I import userroles (after an apparently successful export,
according to the logs), however, everything appears to be fine and
I can
continue to work as normal and log out. When I try to log back in with
the same credentials (superuser account is used most often as this
is a
test environment on my local machine, but I have tried the other
Magnolia default accounts and my own accounts as well), I get a 403
error: Access to the specified resource () has been forbidden.
The logs show that the export/import procedures were successful
without
error. Since I am unable to log into adminCentral for the Author
instance at all, I am forced to reestablish the repository directories
to the state they were before the failure. This is an
inconvenience, to
say the least, for my local environment, but it is unacceptable to
hand
a project over to the client with this major flaw instated.
I am running the test environment on Windows, but the production
machine
is Linux as is having the same issues.
Any help will be much appreciated!
Justin Pizzala
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
