Hi there, I am not sure if anyone had a try the problem I encountered. No replies so far except Boris' reply about FCKeditor. I guess you are all too busy and can not find a time to try this out.
I just want to say, to reproduce the problem is easy. If you have already had magnolia running, all you need to do is changing /server/secureURIList in author instance(in step 2). After a restart of Tomcat and your browser, you will have problem to activate page(s). It's only about 10 minutes or less. Looking forward to hearing from you. Richard ([EMAIL PROTECTED]) On 3/8/06, Richard Zeng <[email protected]> wrote: > Hi, > > I hope you, especially magnolia developers, have a look this post. > This is a problem puzzled me for a long time, and took me a long time > to find out where the problem is. I hope you can help me to find out > why. > > Here are steps to reproduce the problem: > > 1. Let's begin from a clean magnolia. Version doesn't matter, 2.1.3 or > 2.1.5 are both ok. Make necessary change to default configuration. > Because I am using Tomcat on port 8080, what I need do is changing > /subscribers/SubscriberConfig/0001/address to > localhost:8080/magnoliaPublic, and > /subscribers/SubscriberConfig/0001/senderURL to > http://localhost:8080/magnoliaAuthor on author instance. That's all. > Make sure activation works. > > 2. Let's change something. By default, /server/secureURIList for > author instance is /*, means all request are secured. Let's change /* > to /m*, AND add another 2, which are /admintemplates/* and > /.magnolia/* . So basically, under /server/secureURIList, we will have > content node 0001, 0002, 0003, under each, we have node data URI, the > values are /m*, /admintemplates/*, and /.magnolia/* . I'll explain why > I do this later. > > 3. Let's stop tomcat (or whatever you are using), exit from your > browser (for me it's firefox). Then start tomcat and your browser > again. > > 4. You can try to activate a page now. What do you get? You can do > this without any problem??? REALLY??? I don't know why you can, but I > do know I can't. If you can, please stop reading, and I am sorry for > wasting your time. > > 5. Let's go on. Web develper > (http://chrispederick.com/work/webdeveloper/) is really a good tool > for firefox. I am using 1.0.2. Click "Cookies -> Clear Session > Cookies". Then, try to activate again. What happens? (I spent a long > time to find this secret.) > > Sorry I didn't write down what's happening in step 4 and step 5. If > you have a try, you will know what happens, and if you don't have any > problem on activation (after follow my steps), I am sorry for wasting > your time. I hope I can hear from some of you, tell me that they can > not activate any page in step 4. > > The reason I have this configuration is: in FCKeditor, you can use > smileys. But the problem with smileys is the links are always pointing > to author instance, even you are in public instance. So a login dialog > will display even on public instance. For my project, all top level > pages are beginning with m, so I use /m* in secureURIList, with > others. > > I have posted here about this problem a long time ago. But at that > time, I didn't know how to reproduce this problem, basically I didn't > know what's wrong. This time, I think I have found where the problem > is, tho I don't know why. > > I don't know why the secureURIList will effect activation, I hope > someone can tell me. > > FYI > > My environment: > > Windows XP pro, with sp2 > JDK 1.5.0_06 > Tomcat 5.5.15 > > Look forward to hearing from you. > > Richard > ([EMAIL PROTECTED]) > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
