Am 30.06.2010, 14:12 Uhr, schrieb yuppie <[email protected]>: > ??? I just did a brand-new checkout and still can't see any properties.
Double ??? Those properties get set automatically when I create new files. I can see them on my system and svn status reports nothing fishy: fuchsia:~ charlieclark$ cd Sites/cmf-svn/CMF.buildout/trunk/src/Products.CMFDefault/Products/CMFDefault/browser/ fuchsia:browser charlieclark$ svn status utils.py fuchsia:browser charlieclark$ Doesn't seem to matter whether I delete and add them again. >>>> * the preferences form points the user in the direction of the >>>> password >>>> change form. Shouldn't this also be a user action? >>> I usually disable the preferences action completely and use >>> change_password and change_email actions instead. But I was never in >>> the >>> mood to start a discussion about the CMFDefault policy. >> > I had *visible* actions in mind, but you didn't say that you want to add > a *visible* action. Me, too. > +1 for an invisible change_password action Why do you think it should be kept invisible? To avoid clutter? Or minimise the effect on the existing layout? >> If we're linking to other forms like change_password then we should do >> the >> same here. This has to be local_roles form for the member's folder, >> hasn't >> it? Although I don't see how you can hide your folder there. > Now I see what you mean. And I also have no idea how a normal member > could make his home folder inaccessible. Right. I'll ignore this for the view and remove it from the PythonScript. Was struggling with an elegant way of getting a "object/localroles" action for a member's home folder anyway! Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 _______________________________________________ Zope-CMF maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
