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 (GeneratePress, GenerateBlocks).

Want to become a premium user? Learn more below.

Edit synced pattern does not apply to previous pattern

  • Hmmh, looks like gb pro has some issues.

    I made a synced pattern and implemented it on 4 posts. Afterwards I wanted to change the text-color of a link in this pattern, so I edited the synced pattern. But it does not apply to the synced pattern.
    So, I tried next possibility and made the link as a global style. Also – no effect on the pattern.
    So, it looks like you just cannot make a synced pattern, which can be edited afterwards.
    Any suggestions how to make a synced pattern which can be edited afterwards?

  • Hi there,

    for now you would need to insert the Synced Pattern via the WordPress Pattern inserter, see here:

    As the GB Pattern Inserter isn’t currently allowed to insert synced patterns, which i have marked as a bug.

  • The pattern is saved to wp-pattern, and also inserted with the common wp-pattern. The pattern is edited with the common wp_block editor, but as you can see – all 3 patterns are different and not synced.
    So how can I edit a synced pattern so that the style will affect every inserted synced pattern?

  • Can you try inserting the Patterns using the core method to the page. NOT the GB Patter Library.
    Then you should be able to see if they are still Synced ( they have a purple icon in the List View )

  • ok, purple was gone. Looks like somehow the sync-state has gone, and so of course sync was not possible.
    Made a new one, and what should I say, works as expected. Thanks anyway.

  • Ok glad to hear that!

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