2
Vote

Duplicate Part name on creation by UI is handled the hard way, proposed improvements

description

The handling of a duplicate part name when creating a new Part with UI triggers an exception -> Oooops something....

This is not very nice, I propose to handle it normally with an error message.

I also propose to force all parts created by the UI to end with 'Part' avoiding any collision with a ContentType name necessitating an implicit Part with same name as content for Fields.

So if the Part name does not end with 'Part', Orchard adds it.


To continue allowing some parts name not ending with 'Part', I suggest allowing a special '*' marker on the end of input name which will be removed to obtain the final Part name not ending with 'Part'.

file attachments

comments

sebastienros wrote Dec 3, 2013 at 7:35 PM

Ensure validation

The other suggestion will be discussed separately