Yes please. I belive this would not have happened if we were using cmfsetup. Add that quesiton to your issue "would this have happened if I was using CMFSetup?" To remind person to answer that question when they look at issue
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Rene Pijlman > Sent: Wednesday, November 09, 2005 12:50 PM > To: [email protected] > Subject: [Setup] Solved: 404 on /login_form after 2.0.5 > 2.1.1 > > After I migrated from 2.0.5 to 2.1.1 I got a Plone 404 when I > tried to access /login_form > > The cause of this problem turned out to be that my own layers > were missing from the custom skins that were defined in portal_skins. > > Before the migration I had two skins, each consisting of the > regular stack of standard Plone layers and two of my own > layers on top of that. Those layers were Filesystem Directory Views. > > After the migration the layers still existed on the Contents > tab of portal_skins and the skins still existed on the > Properties tab, but the skins contained only the standard > Plone layers, not my own layers. Plone did seem to pick up my > customized files in those layers on the file system though (weird). > > When I redefined my skins with Plone's standard layers and my > own layers, the 404 problem on /login_form was gone. > > Should I report this in the issue tracker? > > -- > Rene Pijlman > http://www.applinet.nl/ > > _______________________________________________ > Setup mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/setup > _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
