I beleive I have found why the pages are not activating on the public instance
once they are cached. It appears that the magnoliaPublic instance cannot find
the cache directory when an existing page is activated. Notice in the stack
trace below that the CacheImpl class is trying to create a file in:
D:\jboss4.0.4.CR2\server\default\.\deploy\magnoliaPublic.war\cache\
Notice that the above path is an absolute path but that "\." is included right
in the middle. After looking at the code I think Magnolia is confused about
whether the cache directory is a relative or absolute path. I can follow the
code and see that it determines this in the CacheImpl class by utilizing the
Path class. However, I could not move any further without compiling the code.
On the Wiki it describes how to compile the code inside of Eclipse. But when I
checked out the code from the svn as the Wiki describes, the magnolia-project
was not in the magnolia directory structure. If I download the source from
sourceforge, will I be able to use it instead of the source code from the svn?
I am willing to try and debug this problem and fix it, but I am going to need a
little help getting this code compiled, so any help would be appreciated.
*************************************************************
Stack Trace of Error when update to a page is activated:
*************************************************************
23:23:41,234 INFO [STDOUT] INFO info.magnolia.cms.cache.BaseCacheManager Base
CacheManager.java(streamFromCache:243) 03.08.2006 23:23:41 Streaming from cache
/, not compressed
23:23:41,281 INFO [STDOUT] INFO info.magnolia.cms.cache.simple.CacheImpl Cach
eImpl.java(cacheRequest:56) 03.08.2006 23:23:41 creating file D:\jboss4.0.4.CR2
\server\default\.\deploy\magnoliaPublic.war\cache\
23:23:41,281 INFO [STDOUT] ERROR info.magnolia.cms.cache.simple.CacheImpl Cach
eImpl.java(cacheRequest:88) 03.08.2006 23:23:41 D:\jboss4.0.4.CR2\server\defaul
t\.\deploy\magnoliaPublic.war\cache\ (The system cannot find the path specified)
java.io.FileNotFoundException: D:\jboss4.0.4.CR2\server\default\.\deploy\magnoli
aPublic.war\cache\ (The system cannot find the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream .<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at info.magnolia.cms.cache.simple.CacheImpl.cacheRequest(CacheImpl.java:
64)
at info.magnolia.cms.cache.DefaultCacheManager.cacheRequest(DefaultCache
Manager.java:65)
at info.magnolia.cms.cache.ManageableCacheManager.cacheRequest(Manageabl
eCacheManager.java:43)
at info.magnolia.cms.cache.CacheFilter.doFilter (CacheFilter.java:80)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 03, 2006 12:49 PM
To: [email protected]
Subject: Re: [magnolia-user] Problem activating pages
I tried your suggestions here are my thoughts:
"1. If I only modify page properties, it will not not consistently
activate the changes on the public instance."
Per points 1 & 2: By "page properties" do you mean "paragraph properties" or do
you mean something else? Isn't this cumbersome for you? I assume you mean that
you delete a paragraph and then add it again in order to get the activation to
work. If this is the case isn't it a pain to recreate paragraphs all the time?
If this is Magnolia's default behavior why have the "edit" button at all?
Per points 3 through 3.4 I tried as you suggested. However, with version 3.0 I
do not see the same type of URL in the Browser window showing AdminCentral.
Note that the "&pathSelected" is not there. The URL is:
http://localhost:8080/magnoliaAuthor/.magnolia/adminCentral.html?mgnlCK=1154630634891
I have tried this on both Linux and Windows platforms and see the same
behavior. I suspect there is a serious problem with magnolia 3.0 RC2 in this
regard. Is there anyone using v3.0 that is not having this problem?
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 02, 2006 10:39 AM
To: [email protected]
Subject: Re: [magnolia-user] Problem activating pages
Sean McMains wrote:
> I concur. In our case, a shift-reload (which should force clearing of the
> client-side cache) didn't cure the problem, but deleting stuff in the cache
> directory on the server did.
>
> Sean
>
> On 8/2/06 8:36 AM, "James Frankman" <[email protected]> wrote:
>
>
>> I don't think this is a client side caching issue, I think it is a
server side
>> caching issue. I beleive I have cleared the temporary internet files from my
>> browser and I still do not see changes made to any page. I only see the
>> original as it was first created.
>>
Michael Davis,
Sharing some things I've discovered when there are problems activating
pages with Magnolia version 2.1:
1. If I only modify page properties, it will not not consistently
activate the changes on the public instance.
2. If I add/remove elements on a page, it will usually activate the
changes on the public instance.
3. Sometimes, I've found that using Internet Explorer works best when
activating pages (instead of Firefox)
3.1. Open a page and edit something in it
3.2. Click the "AdminCentral" button at the top of the page
3.3. Note that newly spawned window now has a specific ID and path
parameter appended to the URL, for example
mgnlCK=1154531045758&pathSelected=/index
3.4. Right click on the node you edited and activate
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
