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 ----------------------------------------------------------------
