Re: Supposed behaviour of the "visible ids" setting

On Tue, Dec 24, 2013 at 11:37 AM, robert rottermann <[email protected]> wrote:
> Am 24.12.2013 11:16, schrieb Timo Stollenwerk:
>> Am 23.12.2013 23:07, schrieb David Glick (Plone):
>>> On 12/23/13, 1:58 PM, Dylan Jay wrote:
>>>>
>>>> On 24 Dec 2013 08:06, "Eric Steele" <[email protected]
>>>> <mailto:[email protected]>> wrote:
>>>>> On 23 Dec 2013, at 10:44, Luca Fabbri wrote:
>>>>>> On Mon, Dec 23, 2013 at 10:59 AM, Timo Stollenwerk tisto-z4DKO/[email protected]
>>>> <mailto: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.
>>>>> That's correct. The control panel checkbox controls access to the
>>>> personal preferences setting. You're basically saying "People are
>>>> alloChangingee the id field if they want to." It doesn't automatically
>>>> turn it on sitewide. Does anyone turn on the id field by default?
>>>>
>>>> Anyone know the original idea why setting the id is so many steps to
>>>> enable?
>>>> Given the user can do it by actions rename anyway. Btw Changing URL
>>>> via rename is a extra training step we always have to do since its not
>>>> intuitive.
>>>>
>>> I think we should get rid of the preference and the global setting, and
>>> have the Short Name field always appear on the Settings tab when editing
>>> an item. That way it's a bit out of the way (not cluttering up the
>>> initial edit page), but it's also easier to access than either the
>>> rename dialog or turning on the visible ids preference.
>> +1
>>
>>
> -10
> I am very much against giving people easy access to changing the short ID.
> The short ID should not be changed, as soon as the object it points to
> is referred to from outside Plone.
> Which for any "serious" Plonesite that is mentioned in newsletters,
> Download sections ans such is surely the case.
>
> So once created and communicated to the world, its URL (aka short ID)
> should NEVER change.
> And people WILL change it, if they can do it easily.
>
> And no, you cant educate people not to do it!
>

Can't we simply pair this new feature to a new permission (is
dexterity easiliy supporting field permission like archetype was?)?

-- 
-- 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