[Resolved] GP 1.3.42 & GP Premium 1.2.93

[Tom]

GP 1.3.42 and GP Premium 1.2.93 have been released.

These are pretty big updates that coordinate pretty heavily with each other, so it’s a good idea to update both (although it won’t break anything if you don’t).

You can see what changed in each version here:
https://generatepress.com/gp-1-3-42/
https://generatepress.com/gp-premium-1-2-93/

[Darron]

many thanks for the updates tom – hope al is well

[Tom]

Thanks, you too!

[BarnaB]

Thank you! 🙂

[Tom]

Known issues so far:

GP Premium 1.2.93 – if you’re using a contained navigation, floating to the left or right, with the sticky effect/transition set to “None”, you’ll run into this issue: https://generatepress.com/forums/topic/gp-update-today-broke-my-sticky-menu

Pretty specific options are needed to run into it, but it’s been fixed in the next version I’ll be releasing tomorrow. For now, just set your navigation to Full Width.

GP 1.3.42 – if you’re using an older version of GP Premium (pre-1.2.93), and you only have 1 of Typography/Spacing activated, defaults.css will load and cause some CSS priority issues. Best thing you can do here is update GP Premium or activate both Typography and Spacing. This fix will also be released in an update tomorrow.

[sjoerd89]

Got myself this message when trying to update premium:
An error occurred while updating GP Premium: Download failed. cURL error 51: SSL: certificate subject name 'docs.generatepress.com' does not match target host name 'generatepress.com'

Any ideas?

[Tom]

Looks like Yoast gets the same question: https://kb.yoast.com/kb/update-errors-with-certificate-subject-name/

[sjoerd89]

Thanks i will check this out with my hosting provider.

[Robin]

Same problem here :/
Don’t know how to fix it.

[sjoerd89]

Robin it is a hosting problem, contact your hosting provider and tell them to update both your SSL library and CURL. They should do this for free and tell you what will happen.

[Tom]

Your server running these old libraries is actually a security issue, so it’s good to get them to upgrade anyways 🙂

[sergeysl]

Hi Tom!
Headers of comments are not translated from English. After replacing the code between <h3 class = “comment-header”> and <h3> in comments.php to a similar code of the previous version, translation works fine ❓

[Tom]

Ah, I try my best never to change translated strings, but in this case I had to update the comments header to conform to new WordPress.org standards.

The translation will need to be updated on WP.org: https://translate.wordpress.org/projects/wp-themes/generatepress

[sergeysl]

OK. Thanks for the explanation!

[Tom]

No problem! If you update the translation just let me know and I’ll try to ping the translation editor/request you become one so you can approve it for your language 🙂

[Author]

Posts