search

statamic / ideas

💡Discussions on ideas and feature requests for Statamic
https://statamic.dev
32 stars 1 forks source link

Optionally update all data using a blueprint when renaming a field handle #143

Open philsturgeon opened 4 years ago

philsturgeon commented 4 years ago

Bug Description

After creating https://github.com/statamic/cms/issues/1676 (a field called url will lose its value in the Content API) I tried to rename the field to external_url to avoid the clash via the Fields interface in the CP. When I navigated to the collection to see if it worked, the "URL" field was empty.

I'd expect it to rewrite the field in the entry markdown.

jasonvarga commented 4 years ago

Debatable, I know, but this is probably feature request territory. I'll move over to statamic/ideas.

philsturgeon commented 4 years ago

Ha yeah I do a lot of product planning and support. The old feature vs bug thing is often debatable but whatever you go with, I think a lot of folks will consider this unexpected behavior. Renaming a field should probably rename the field, not just vanish the data from the CP.

jasonvarga commented 4 years ago

The blueprints are a way to model your data but (right now, at least) they don't really touch your data. If we were to make it update your data, we'd probably add a checkbox or some sort of opt-in thing rather than it just happening.

I still think it'd be a useful thing to have though. 👍

philsturgeon commented 4 years ago

Sounds like a great feature. I would click that. 🙌

MadJack-3 commented 4 years ago

This would be a nice feature. The data is retrievable from the backend but a CP only user will think they just blew the content away. I can see support calls for this in my future from content managers. It was this way in v2 as well.

duncanmcclean commented 7 months ago

If we get to this, we could probably do it for Replicator/Bard set handles too.