mermare

Hi Balachandar,

Thank you. I updated to v. 1.12.4 and my inline styles are back. I appreciate your follow up and quickly pushing out a fix.

Looking at the changelog for v. 1.12.3 – my guess is the issue occurred with this: “Improvement: Performance – CSS optimization up to 50%.” Can we swap out the stylesheet for the non-optimized version and see if it fixes things?

This style sheet is overwriting/overriding the inline styles. wp-content/plugins/ultimate-addons-for-gutenberg/dist/blocks.style.build.css?ver=1.12.3

• This reply was modified 5 years, 8 months ago by mermare.

For example: when I view the block as html in edit page, it has all the correct css – it’s inline css… what is preventing it from displaying properly on the front end? It seems like a bug in v. 1.12.3.

It is like the classes of nested elements in a UAFG block are no longer recognizing the styles set in the block settings. On the front end they are showing the default styles for that element. But in the settings themselves they are still set correctly. What happened?

Well, I see that I can switch to the base styling only in the settings for WPForms so that made it easier to style without using !important. I am curious of the purpose of the empty divs – are they like placeholder guides for users styling? Or something else… in any case I will mark this resolved.

?? thanks Garavo.

Thanks Garavo. Colors saving now with v 1.13.4. Possible new issue… I cannot download an export of settings and palette in Backup or JSON (I was able to download a CSS backup).

Ditto, not saving colors here with a new install of 1.13.3. WP 5.0.3 and Astra 1.6.8. I’ll uninstall for now.

Best,
Marianne

You’re welcome. Thanks for passing it on the Ultimate Addons for Gutenberg Team.

@toddcav I never got a response, so I uninstalled Gravity Forms + Stripe and went a different route. Best of luck.

Unfortunately since the old plugin is not in the WP repo, WP Rollback is not an option. I did a manual rollback with a few hiccups that I ironed out. Remember to backup the site prior to doing this.

Thanks for the explanation.

Thanks Edward. In evaluating whether to return to v 1.3.3 or continue forward with v 2+ it would be helpful to know your roadmap and an estimated timeframe for this feature and others like the ability to style specific fields of staff on the archive pages as well as on the modal pages. Are those things you can provide?

Hi Edward,

I used CSS to hide all the social media icons as a temporarary measure until you fixed it.