If you have a field on one content type, you can easily add it to another content type using the 'Add existing field' option. This is great, and the fact that they can have different settings is cool too (e.g. 'field_image' on a post can save to 'files/blog' and be a large size, while the same field on a client content type can save to 'files/clients' and be a smaller size).
However, there are times when it's necessary to have the same settings for a field across all content types where its used (e.g. an ID number with certain min/max values, a postal address restricted to the site's country, etc.).
In this case, it'd be nice not have to manually copy over all the settings each time a field is added to a new content type. I'd therefore like to suggest a way whereby settings from another content type can be copied over with a field. These can then be changed for the new content type if necessary (i.e. nothing needs to change database-wise), but it prevents the same settings needing to be copied over manually.
I'm not sure how to implement this or what the UI/UX would look/act like, but thought to put the idea out there...
Recent comments
So the implication is that another module is causing the trouble. Now for the slow process of elimination... Sounds plausible. And good luck with digging...
How to troubleshoot interactive image cropping modules?
I’ve just set up a clean install in MAMP and Focal Point works fine. *sighs So the implication is that another module is causing the trouble. Now for the slow process of elimination...
How to troubleshoot interactive image cropping modules?
Here’s the edit screen with the Focal Point instructions below: If I click on the Preview link, I get this: And no errors in the console.
How to troubleshoot interactive image cropping modules?