Hi gang, love the plugins that you guys are producing, and love even more that Gravitate Blocks offers the use of native Foundation styles! So my question:
We’re using a custom column count in our version of Foundation (instead of the standard 12 columns that’s native to Foundation). I can see where the column styles are in each of the blocks in /grav-blocks/<blockname>/<filename.php> — if we were to customize these values, I expect they’ll be overwritten when a plugin update is released.
Would you advise that we work around it by duplicating the block folders and inserting our own values? Will those new blocks be replaced when a plugin update is run?
If you have a different idea for tackling that, I’d love to hear it. My method would result in both the originals and our new blocks being displayed for selection — and ideally I’d like to hide the standard 12-column versions from our users.
Thanks!
]]>For those who don’t know how to do this yet, you can include this in your template to output the blocks to the front end in your theme templates:
<?php GRAV_BLOCKS::display(); ?>
Needing to gain access to $fields['background_colors'] (from Gravitate Blocks) to use in another part of my application. It appears to be an ACF field, but I’m not sure if there are any special IDs I may need in order to target (and fetch) that field.