Are you a GenerateCustomer?

Do you have an active GP Premium or GenerateBlocks Pro license key?

Create a GenerateSupport account for GeneratePress and GenerateBlocks support in one dedicated place.

Create an account
Already have a GenerateSupport account? Login

Just browsing?

Feel free to browse the forums. Support for our free versions is provided on WordPress.org (GeneratePress, GenerateBlocks).

Want to become a premium user? Learn more below.

Asset Management Through Un-synced Patterns

  • Sometimes, I find that after copying and pasting GB Blocks, when you edit the new iteration, it also updates the old one. I have learned that using Duplicate changes the GB containers to avoid this issue. For a site, if I build out unsynced patterns, can these be used without needing to go through the duplicate process? The idea is to avoid changing future iterations without affecting previously used instances.

    Thoughts on the best to manage this?

  • Are you referring to the WP patterns?

    If so, the unsynced pattern would still contain the same ID, so it would still affect blocks that have the same ID on the same page.

  • Hi Ying, I see. What is we build these inside GB’s Local Pattern using Global Styles. Would this prevent things from changing if newer instances were updated?

    Add-On: Noticed you used “the same page”. If using the WordPress unsynced pattern, would the problem still happen if these were dropped into different pages?

  • What is we build these inside GB’s Local Pattern using Global Styles. Would this prevent things from changing if newer instances were updated?

    This should work, unless you update the global style, otherwise, the inserted local patterns should not affect each other.

    If using the WordPress unsynced pattern, would the problem still happen if these were dropped into different pages?

    It should be fine theoretically, haven’t tested myself.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.