Not sure if this is a bug or a feature request.

1. I've added a gmapfield to a content type and set a default gmap macro, set 1 required value and set disable macro input.

2. Create some nodes.

3. Go back into the content type and modify the macro (change the size of the map)

When I do this the existing nodes don't reflect the new map size and because i've disabled the macro input I can't manually change the macro on a per node basis.

Ideally if disable macro input is selected it seems like a change in the default macro should force an update to all of the existing nodes.

thoughts?

thanks!!

Comments

zzolo’s picture

zzolo commented
Category: bug » feature

Yeah. This is a tough one (though a good one). The only way I know how to do this is to update all the fields in the DB with the new value (manually). It would have to only change maps that were the old default, too, since there are ways to have a default map field with old custom maps. Its not too bad, but a little more than I can take on right now.

zzolo’s picture

zzolo commented
Title: change in default macro doesn't update existing nodes » Allow Default Macro to Update Existing Values
locomo’s picture

locomo commented

Thanks for your response.

I'll look forward to the fix when you have time. As my site starts to get bigger its becoming quite a chore to go in and change a lot of nodes if I have to tweak the layout and change maps sizes etc.

not_Dries_Buytaert’s picture

not_Dries_Buytaert commented
Title: Allow Default Macro to Update Existing Values » Allow selecting "macro per node" or "macro per node TYPE"

I suggest changing the values of the field to:
set macro per node (i.e. by node author)
set macro per node type (i.e. applies to existing nodes reactively and to new nodes proactively)

zzolo’s picture

zzolo commented

--
Please note that I do not have any serious time to devote to this module. Patches and co-maintainers are welcome.