Il 17.06.2011 10:49, Magnolia Forums (on behalf of Tristan Zwingelstein)
ha scritto:
[quote]Il 16.06.2011 14:01, Magnolia Forums (on behalf of Tristan Zwingelstein)
It seems to be a cache issue.
[/quote]
It is not a navigator cache problem.
For my own, the .war of my magnolia site should be compiled to get the
modifications.
Ok, you say you are using a .war approach.
This can be the issue (to doublecheck):
1) The war "explodes" all files (no JSP, they are exploded on point 3)
2) Tomcat starts and Magnolia install its module
3) Each module extracts all the jsp files on the filesystem, overwriting
the original ones (if any)
4) Magnolia says: "ok, I've finish my installation"
5) Now you shut down tomcat. The exploded folder can be removed by tomcat.
6) Later, you start again tomcat, if folder has been removed at point 5,
there is a new war explosion.
7) At this time, Magnolia (I suppose configured with an external DB)
says: "I do not need any installation, everything has been done before"
and doesn't extract anything.
Can you check if you are in this case?
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
