@1. i dont know how your deploy process looks like, but we always try not to delete the files that magnolia creates at first start. Otherwise they are missing after another deploy. A Module reinstall recreates the files, so the behaviour you decribed seems to be the expected one.
@2. i once thought the 3.6.3 cache flush doesnt work properly, and then recognized, that it s the browser who caches (and shouldnt do that). Just try "ctrl+F5" - and let us know. If thats the problem there was an issue on this list shortly. @3. i am interested in that too, but cant say anything. @4. i guess yes. but hope someone else can explain how... ;) regards rainer Joshua Portway-2 wrote: > > > sorry i've been off this list for a while, some of these questions may > have been answered before but I couldn't find the answers from a quick > look through the archives : > > several behaviours seem to have changed in 3.6.3 (i was using 3.5.8 > before) which are causing problems : > > 1) mgnl-files doesn't seem to work properly. At least the sample > templates etc. aren't installing for me. They install and work > correctly the first time that I deploy my application to my app server > (glassfish) - but if I then redeploy the app they seem to get deleted > and don't seem to be recreated when the app starts up again.....or > something. Deleting the config/modules/samples node and then > restarting my app server seems to fix the problem (the sample files > get re-installed) - but this is a real pain, and I'm pretty sure I > didn't have to do this before. Presumably anything that uses mgnl- > files will be having similar problems (not just the samples module), > so I'm a little worried I might also have more subtle problems that > I'm not aware of. > > 2) The cache doesn't seem to flush in response to things like changing > user permissions. If I change the permissions of a user group then > some pages may appear or disappear from the site (and therefore from > site menus etc.) but the cache doesn't seem to recognise this and > continues to used cached versions of pages which contain stuff that > should not be visible according to the current permissions. The only > way to fix this seems to be to manually flush the cache, which is also > pretty tedious. > > 3) I'm having problems setting up secured parts of the site - if i > change the "anonymous" role so that it doesn't have permissions for > certain subtrees of the site, then (afaik) when a user attempts to go > to those pages they should get the standard magnolia login dialog. > Instead I'm getting an error from the app server saying that those > pages require http authentication. What am I doing wrong? Do I need to > do additional configuration ? > > 4) not strictly a 3.6 problem, but.... Is there a way to detect in a > workflow whether the user belongs to a particular group? It seems to > me the most obvious default activation workflow should check whether > the user initiating the action is in the "publisher" group, and if so > just activate the content directly rather than going through a more > complex workflow. > > anyone else run into these issues ? Are there fixes or workarounds > that are better than the one's I've described ? > > thanks, > Josh > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > -- View this message in context: http://www.nabble.com/problems-upgrading-to-3.6-tp21805707p21807065.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
