During usability testing, one user entered a field name with a spelling error, and was really, really irritated that they couldn't change it. Although I fully understand locking (machine readable) field names when there's content, it seems like CCK could potentially drop and add the table/columns in the background if there's zero rows in them - after all that's what people are going to do themselves manually if they quickly realise they chose a bad name.

Comments

dopry’s picture

dopry commented

I'm tempted to won't fix this issue. The user can restart the add field workflow by clicking on the add field tab. They should hopefully recognize their typographic error before completing the field creation process...

moshe weitzman’s picture

moshe weitzman commented

This annoys me too. It is a real need. The fact that we don't offer this is a developer/complexity matter, not a deliberate UI choice. I think it is a valid request, though possibly a dupe.