Black Friday Sale! Get up to $40 off GP Premium!Learn more

GP Premium 1.11.0 – Block Elements!

Welcome to GP Premium 1.11.0! This is a huge update that includes new features, performance improvements and tons of bug fixes.

As you might have noticed, we’ve been working very hard lately to offer more functionality and modernize our products. With the introduction of GenerateBlocks this summer, we’re updating GP Premium and GeneratePress to be better than ever before. GPP 1.11.0 is the first step!

Block Elements

Our Elements module has been a favorite of our users since it was introduced in GPP 1.7.0, and it just got a whole lot better. Block Elements!

Block Elements work just like our other Elements, but they allow you to use the block editor to build your Element content instead of needing to use HTML. When combined with GenerateBlocks, you can now build custom headers, sidebars, and footers. You can also use the Block Element as a regular hook to add content anywhere throughout your website!

A custom sidebar built in the block editor with GenerateBlocks.

What makes Block Elements extra powerful is you still have access to the Display Rules. This means you can build conditional sidebars, footers etc..

Use Display Rules to build conditional Block Elements.

Block Elements open up endless possibilities. Another example is building a site footer, which has always been somewhat limited in GeneratePress. Now, there are no limits.

A custom site footer build with Block Elements and GenerateBlocks.

This is just the beginning. We have big plans for Block Elements moving forward!

Layout Elements

Layout Elements are super powerful and allow you to set things like your sidebar layout and content width across your entire site. However, before 1.11.0, your Layout Element settings didn’t apply to the block editor.

This was always an annoyance for me personally. If I disabled sidebars within all of my pages, I want the editor to reflect that change so I can get a realistic view of what my content will look like.

As of 1.11.0, your Layout Elements will take effect in the block editor!

External File Dynamic CSS

If you’ve been using GeneratePress for a while, you have probably noticed that the CSS generated by your Customizer options is added inline below the main theme stylesheet.

Inline dynamic CSS

You can now choose to generate this CSS in an external file instead of displaying it inline. Not only will this clean up your HTML, but there are also performance benefits to doing so. Once the CSS is generated, it’s added to the file which is cached by your browser. That means the CSS doesn’t have to generate on every page load, which is a big bonus!

External dynamic CSS

While inline dynamic CSS is still necessary in some cases, this should help further improve performance, especially when you’re using a lot of options. This option can be turned on and off in the Customizer.

Preparing for GeneratePress 3.0

That’s right, GeneratePress 3.0 is right around the corner. GP Premium 1.11.0 has tons of tweaks to all of its modules to prepare for 3.0, so be sure to update before you start testing/using 3.0 in the near future.

Both versions are the beginning of a new generation when it comes to GeneratePress. We’ve been in the game for a long time now, and things have changed. GP Premium 1.11.0 is step one, and we’re excited to get things in motion!

Full Changelog

1.11.0

  • New: Block Elements
  • New: Apply Layout Element options to the block editor if set
  • New: Generate dynamic CSS in an external file
  • Blog: Separate CSS and load only when needed
  • Blog: Add column width classes to stylesheet
  • Blog: Disable featured image itemprop if microdata is disabled
  • Blog: Add generate_blog_masonry_init filter
  • Blog: Add generate_blog_infinite_scroll_init filter
  • Blog: Fix archive page header overlap when using no featured image padding/one container
  • Blog: Replace screen reader text with aria-label in read more buttons
  • Disable Elements: Add option to disable the Mobile Header
  • Disable Elements: Disable top bar disables it even when combined with Secondary Nav
  • Disable Elements: Use generate_show_post_navigation filter to disable single post navigation
  • Elements: Use full hook name with generate_ prefix in dropdown
  • Elements: Rebuild how Element types are chosen
  • Elements: Add chosen hook under type column in edit.php
  • Menu Plus: Add generate_after_mobile_header_menu_button filter
  • Menu Plus: Add sticky placeholder only when nav becomes sticky
  • Menu Plus: Add class to sticky nav when scrolling up
  • Menu Plus: Fix navigation branding/mobile header layout when using RTL languages
  • Page Header: Prevent PHP notices
  • Secondary Nav: Clean up CSS
  • Secondary Nav: Add generate_after_secondary_navigation hook
  • Secondary Nav: Add generate_before_secondary_navigation hook
  • Secondary Nav: Integrate with future flexbox option
  • Secondary Nav: Add has-top-bar class if needed
  • Secondary Nav: Add screen reader text to mobile menu toggle if no text exists
  • Secondary Nav: Remove microdata if disabled
  • Secondary Nav: Add generate_secondary_menu_bar_items hook
  • Spacing: Set sidebar width in Customizer for future flexbox option
  • WooCommerce: Add generate_woocommerce_show_add_to_cart_panel filter
  • WooCommerce: Integrate with future flexbox option
  • WooCommerce: Ensure WC()->cart is set
  • WooCommerce: Remove left margin from SVG menu cart icon
  • WooCommerce: Show sticky add to cart panel on sold individually products
  • WooCommerce: Remove bottom margin from related/upsell products
  • WooCommerce: Fix cart menu item spacing in RTL languages
  • WooCommerce: Fix menu item cart dropdown design in RTL languages
  • General: Update selectWoo
  • General: Update select2
  • General: Run all CSS through PostCSS
  • General: Fix various text domains
  • General: Fix JS error when toggling nav as header option without Colors/Typography modules
  • General: Update all translations over 90% complete
  • General: PHP cleanup/coding standards
  • General: Add off_canvas_desktop_toggle_label to wpml-config.xml

37 thoughts on “GP Premium 1.11.0 – Block Elements!”

  1. So cool. I’m really very pleased. Gutenberg is the future, and that you’re going with it. Please keep up the good work. The direction is really exciting and great and I am really happy.

    Reply
  2. Ooohh, super excited about this update, and future plans. Love the idea of using Gutenberg to build headers/footers etc.

    Does that mean that there will be a menu block for adding to the site header block type?

    Reply
  3. I’ve had a few hours now to play around with the GP Premium 1.11.0 alpha3. I’ve said it before, but my first impressions with the alpha just reinforces it… I absolutely love the direction you’re headed with GB and GP.

    GPP Element hooks and headers currently accept shortcodes and template tags. Both very useful, if not indispensable, for creating things like category or post heroes/headers that display current page and/or other related info. For example, category descriptions, post title/author/date, terms attached to the chosen taxonomy, or custom fields and other post meta.

    I noticed that shortcodes are not executed and template tags are not available in Block Elements of any type. So say I have a single post page hero Element, for example, using {{post_title}}, {{post_date}}, a shortcode, etc… If I wanted to replace this Element with a Block Element hook, I’d have to manually display that dynamic information and create a new Block Element (or several) for each post, which could get unwieldy pretty fast.

    I know you’re very early in the first phase of this, with GP 3.0 right around the corner and much to come yet. I’m just curious to know if shortcode or template tag functionality is something we might see with Block Elements in GPP or GB? Or, do you envision Block Elements existing along side current Element hooks that manually display html with dynamic content from shortcodes and template tags?

    Regardless, fantastic work with this! I haven’t encountered any issues with alpha.3 so far.

    Reply
  4. i dont know much about this platform since i just bought the premium version last month….. feels like its a cool feature , cant wait to play with it.

    Reply
  5. Hi Tom,

    It would be great if you include social sharing buttons along with the theme. I have tested few plugins and I was not happy with any of them.

    Reply
  6. Really great stuff Tom.

    Quick question: would the new GP Pro have a stickey footer? That’s something I’d love to see as optional. I know I can customize with CSS but it adds horizontal scroll for me…

    Reply
  7. I’ll be so happy once I can ditch all pagebuilders for GP + GPP + GBP. Knowing how you focus on clean and lightweight code I can only hope for some major improvements to my sites once they have transitioned.
    And with this blocks element its almost time to make the switch. I’m eager to transition my shop to the full GP experience – and so the only thing I’m still waiting for is for WooCommerce to use blocks for the product pages.
    It’s gonna be a wild ride. Thanks for Generatepress. We love it and we’re here to support you.

    Reply
  8. I update to GP Premium 1.11.0 today and use dynamic CSS Print Method, and works great! Thanks

    I look on the support forum to find this feature. If anyone doesn’t know how to activate, it is under customize, and general option, change inline embedding to external file, and regenerate CSS file.

    Reply
  9. Its a bit confusing if you used gp premium from the start 😛

    I just wondered what happened to gp2.
    Until i used my brain.

    Any outlook for gp3 and (probably) the corresponding gp premium? Also a timeline (i know – thats a “ready when ready” question – but worth a try)

    Reply

Leave a Comment