Re: Supposed behaviour of the "visible ids" setting
Luca Fabbri <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAGfGq=Yn9pczwDyNs3O_wxEQoRTb1-XHN6sjxBF6xtr5PHC1yA@mail.gmail.com> |
On Mon, Dec 23, 2013 at 10:59 AM, Timo Stollenwerk <tisto-z4DKO/[email protected]> wrote: > Hi, > > I'm currently working on the PLIP to move all control panels in Plone to > use z3c.form/p.a.registry and I was wondering about the supposed > behaviour of the "visible_ids" setting. > > On a vanilla Plone 4.2/4.3 it seems this setting does not have any > effect at all. If it is enabled, there is no additional id field on the > edit view of a content object and it is always possible to edit the id > of a content object through the folder_contents view. > I used this few days ago on PLone 4.2 and it was working as expected: remember that you must enable both the site general setting *and* the same preference in the user's preferences. > So what is the supposed behaviour of this setting? Should we show an id > field on the edit view? Is the current behaviour a bug in Plone 4.x? Do > we want to get rid of that setting in Plone 5/p.a.contenttypes? > To be honest: is a nice feature, but probably a very unused ones. I will not miss it. -- -- luca twitter: http://twitter.com/keul linkedin: http://linkedin.com/in/lucafbb blog: http://blog.keul.it/ ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk