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.

Styling issues while using local patterns

  • krempel-und-co

    I created a local pattern for a hero element, containing multiple containers:

    1. Container with background image
    2. Container with transparent gradient
    3. Container wrapping a grid
    4. Container in grid with white text (instead of default black)

    When adding the local pattern (Hero Full Width Image) via the / in gutenberg the background-image doesn’t show behind the gradient in the editor (but it shows in preview). Additionally other containers below are somehow affected by adding this local pattern and showing the same gradient and getting (some) white headlines.

    This also happens when copying and pasting the elements into the page.

    Is this because of the new global styles? Or changes to the local patterns?

  • Hi there,

    I’ve been trying to log in to your site to see the issue, but the login credentials are not working. Could you please check them?

  • krempel-und-co

    Hello Alvind, thanks for getting back to me! Sorry for the mixup! The credentials work now. 😊

  • Sorry, but I’m not quite understanding your first issue. Do you mean you want the image to be positioned behind the gradient?

    As for the second issue, you can duplicate the affected container and delete the old one to regenerate its element ID. It shares the same element ID with the pattern container, which is why the pattern styling affects the layout.

  • krempel-und-co

    Hello Alvind,

    the issue was that when pasting the template into the page it wasn’t displayed correctly. I guess this was because of the shared element ID. I duplicated the container in the template (local pattern) to regenerate its ID there. Now I can import it without issue. 😊

    Thanks for your help!

  • Great to hear that!

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