Hi Thomas
That did the trick even though I do not quite understand why. But it
seems to be another hassle like the issue with the 'superuser' password
that needs to be set back to the default value in order to activate to a
new repository or to close your browser because one cannot log out on
the admin page.
-Andy
Thomas Ferris Nicolaisen wrote:
I also had some problems with this. After having deleted all content
in magnoliaPublic, it simply wasn't possible to activate anything from
magnoliaAuthor. So I...
1) re-installed magnoliaPublic (letting the bootstrap run again)
2) made sure the subscriber settings were correct
3) created a bogus features node in magnoliaAuthor/website
4) Activated the features node and some other nodes
After that, it's worked smoothly. Just avoid having an empty
magnoliaPublic with no corresponding nodes in magnoliaAuthor.
On 3/6/06, Andreas Schaefer <[email protected]> wrote:
Hi Geeks
I just wanted to upgrade to 2.1.5 but ran into a little snag here. I
activated all the necessary content from 2.1.3 to 2.1.5 Author site but
when I try to activate from Author to Public then it fails.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
