Re: [Zope-dev] Can I get rid of standard_template.pt?
--On Freitag, 10. Mai 2002 08:27 -0700 Andy McKay [EMAIL PROTECTED] wrote: But... when you restart Zope it recreates them all again for you :) However you can delete the Examples and not have them come back ;) I think it was Matt who pointed out to me that I could create harmless substitute objects (say, Files) for the things I do not want autocreated. -) Delete session_data_manager -) Add File named session_data_manager -) Voila, core sessions disabled This will however not help you if your intention is to unclutter the root folder... Regards, Stefan -- Things work better when plugged in. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: ZPT and else
Brent Hendricks [EMAIL PROTECTED] wrote: Another way to do this is to use the python test() function inside tal:replace to conditionally replace the if content with the else content. For example: div id=edit-area tal:define=editItems python:here.getMenuItem(...) h3Edit Menu Items/h3 form action=Delete method=post name=actForm tal:replace=python:test(editItems, default, 'No menu items available') ... (form and table elements, and a loop over editItems contained in here if there were results) ... /form /div This technique works well when you have one case which is more involved and can be the default, and another case which is simple text (like an error message). This is very ugly, even if probably tempting for a PHP programmer :) Also if i18n comes into play, you'll have to use two different ways to internatonalize things... Florent -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 87 http://nuxeo.com mailto:[EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [ZPT] Order of attribute execution Feature Request
Jim Penny [EMAIL PROTECTED] wrote: I also have not found a convention that I am comfortable with on handling check-boxes and radio buttons in error processing. But I expect to! Are you referring to what I call magic boolean attributes ? http://lists.zope.org/pipermail/zpt/2002-March/003013.html Florent -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 87 http://nuxeo.com mailto:[EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] restrictedTraverse
With an object path /A/B/C where C has a local role allowing a user to
view C but where B disallows acquisition of the View permission, the
publisher correctly allows the user to see C.
However restrictedTraverse('/A/B/C') fails (You are not allowed to
access B in this context). This is because restrictedTraverse checks
the security (using validate) at *every* step, and obviously the
user is not allowed to see B. Is there a reason for this ? Why not
simply validate only at the last step ?
I have the need to programatically access object protected in such a
way. The workaround I'm going to use in my code for now is to call
unrestrictedTraverse and validate() by hand the resulting object. But
I'm concerned that there may be a more profound security reason I'm
missing.
Florent
--
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 87 http://nuxeo.com mailto:[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Betreff
index.htm Description: Binary data attachment: klee.jpg attachment: tassegross.jpg attachment: foto2.jpg attachment: automat.jpg
