Hello,
I'm aware that Overrides are not necessarily dangerous; most of the time, they are simply misused, just like I did. However, I believe there is a lack of documentation on this topic. So, I would love some clarity on Overrides, as I think I might have misunderstood the concept. Here's what I've gathered:
I created a FieldsetPage fieldtype named Hero, with the following fields: image, text, body, and URL.
I added the Hero field to the basic-page template.
I created three pages: A, B, and C, all using the basic-page template.
Now, here's where it gets interesting.
On page A, I made no changes to the Hero. I used it as it is.
On page B, I overrode the label of the image field to "logo".
On page C, I overrode the Hero by adding an extra field, such as a textarea.
Now, the changes made on page B and C will affect page A, correct? Is there a way to allow overrides by individual pages, rather templates? This would provide us with a lot of flexibility, wouldn't it?
My issue happened when I started adding extra fields and removing some, like I did on page C. I forgot it was one template-based page, so I ended up messing up the other pages.
One last thing. I don't understand the warning: " WARNING: enabling settings beyond those specified by the Fieldtype/Inputfield module may not always work, or may cause problems"
So, folks, I'd be extremely grateful for any insights regarding overrides, perhaps some best practices and what to avoid.
Cheers!