On Thu, 2008-01-10 at 03:04 -0500, Hedley Roos wrote: > Those are not bugs. The INFO in the log is just info. It would say > ERROR otherwise.
My bad. What I meant was, based on what the message said, I need to make a change some > > For the "Home → Member Profiles → ahsmember.2008-01-09.6353804714" > breadcrumb the URL has a portal_factory in the path. It means the > object is not yet in its final location, and the rename has not yet > kicked in. portal_factory is a volatile place to create objects just > in case you don't want the object anymore and never click Save. It > keeps the ZODB clean. This has gone away as well as the redirect to the registration page. > > As for the "def view(self, REQUEST):". Maybe it is not needed anymore > since AHSMember now subclasses BrowserDefaultMixin. Take it away and > see what happens when you navigate to a AHSMember object. No need - after packing the db, rebooting, and closing/opening browsers, all is well with the world. > > As for the destination page after login - you'll have to verify that > the login actually works (ie you are really logged in and your nav bar > changes). Yes, the user is actually logged in. > Plone remembers where you wanted to go before you were > prompted to login, and cookies are shared between different instances > of a browser with the same domain. So alias say admin to localhost in > /etc/hosts and login as an admin on http://admin:8081/mysite. Also > alias public to localhost and login as a normal member on > http://public:8081/mysite. > > Then logout everywhere, close your browsers, open a new one and try > logging in now. That fixed everything!!! Thanks again for all your efforts. If I may ask one more question. How did you debug the problem down to the way the Boolean field was handling 1 and True? I have to admit, debugging a product in a plone site is still a mystery to me. I come from the Java/Servlet/EJB world, and I can pretty much debug/fix any bugs in that space. I still do not have a firm grasp on (1) how to debug and (2) the best tools to use to debug for a plone site. How does one single step through the code? Set break points? Set good ol'fashion print statements to the console to see what is happening? I have not found a lot of good tutorials or books on this particular part of plone. Any suggestions on good tutorials on creating unit tests for plone products as well? I have used JUNit tests in my java servlets/classes and I like having test cases to run as well. Thanks again!!! I feel I owe you a beer or two for all the time you spent helping me. BTW, the site is at http://www.ahsnews.com. The students at Arcadia High School have yet to design a better look and feel for the site, but at least it is working now! Cheers! Mark > > H > > _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
