Essentially, that must mean the repository is lost, one or another, and thus 
recreated at startup. If Magnolia doesn't find nodes under /modules/ in the 
configuration workspace, it assumes the module it's looking for needs to be 
installed (which is correct).

If you create content, say, in the website workspace, it's also lost after a 
restart, right ?

If so, I'll go ahead and assume there's something wrong with your 
configuration, but without further details, it's hard to guess ;) Aren't you 
log files giving you any clue ? Otherwise, log files and configuration files 
would help. Use something like pastie.org or some uploading service if you want 
to share them.

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=2258c5c0-b1ae-426b-b73f-a6465670ebb9


----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

  • [magnolia-user] Oracle 11g Magnolia Forums (on behalf of ?ric Gagnon)
    • [magnolia-user] Re: Or... Magnolia Forums (on behalf of Gr?gory Joseph)

Reply via email to