Jon Fuller

Update: looks like this should do the trick, but let me know if you notice anything wrong with it:
https://gist.github.com/Garconis/d308efccf02e7376c59eecabb922970b

It looks like this fixes the issues:

https://aioseo.com/docs/aioseo_disable_shortcode_parsing/

add_filter( 'aioseo_disable_shortcode_parsing', '__return_true' );

But can you better explain in that documentation what it really is doing? I don’t know why it’s not enabled by default, considering you’re otherwise breaking popular WP plugins and themes. At the least, this should be a checkbox somewhere in the settings, or have the plugin auto-detect if it’s breaking things and enable it automatically.

Although, it’s also worth noting that when your plugin is installed (even WITHOUT a Divi Child Theme), it causes this stylesheet to pull in:

<link rel="stylesheet" id="divi-style-pum-css" href="https://example.com/wp-content/themes/Divi/style-static.min.css?ver=4.13.1" type="text/css" media="all">

However, when your plugin is NOT installed, it doesn’t pull that file in. So something (either on your end or Divi’s end) is causing files to get pulled in with your pum in the id.

• This reply was modified 3 years ago by Jon Fuller.

Are you able to share the functions.php of your child theme? We are using this one, to pull in the child style.css and adding a datestamp to the file: https://github.com/FreshySites/Divi-child

I was talking about the one in the screenshot with the red arrow, with the ID of divi-style-pum-css

That’s somehow a result of your plugin.

Did you test with these settings: https://i.imgur.com/5Ff7Zvy.png

Looks pretty good, but input errors seem to need additional top padding that the Gravity Forms theme.css is removing: https://i.imgur.com/oeu8S8V.png

They are removing padding top when the form input uses Descriptions Above the Inputs via:

.gform_wrapper.gravity-theme .field_description_above .gfield_description

But they unfortunately are therefore also removing the top padding from the actual validation message too, since that also uses the gfield_description class.

So could probably add CSS like:

.gform_wrapper.gravity-theme .field_description_above .gfield_description.gfield_validation_message {
    padding: 12px 16px;
}

It’s still broken…

Doesn’t instill much confidence in your plugin or service, when your main plugin screen has a broken image on it for months with no fix.

I’ve purchased v3 to test it out. Unfortunately the TTFB is still high even when the page is cached by the hosting provider. With the plugin, the TTFB is between 500-600ms. Without the plugin, the TTFB is about 40-50ms. ??

Is that v3 of the paid version, or the WP free version? I see the changelog here is only up to 2.7.19.

Is there a changelog of the paid version?

Can you describe the difference between between first touch referral and last touch referral?

• This reply was modified 3 years, 1 month ago by Jon Fuller.

I assume we could still make adjustments to the existing logic that Widget Logic has implemented, by adjusting code within the site’s database, but I haven’t looked to see where the plugin stores its logic per widget yet.

But yes, I may need to go into the DB and manually remove this plugin’s code (per widget), then implement some other plugin instead. Though, when I checked a couple years ago, none were quite as useful as this one. ??

Edit: it looks like one of the plugins you linked to, is having the same issue. It only works on the “Classic” widgets. Apparently there is this plugin we can install for now, which will bring the Widgets back to the “Classic” view… which should then theoretically let us still use this Widget Logics plugin.

https://www.ads-software.com/plugins/classic-widgets/

• This reply was modified 3 years, 3 months ago by Jon Fuller.

Has anyone figured out a way to revert from the WP 5.8 Widget Blocks? Or to get Widget Logic plugin to work with the new 5.8 blocks?

I’m quite disappointed that I can’t even adjust the existing logic that this plugin has implemented.

Any update here? Would love to continue utilizing your plugin to make Gravity Forms look great with Divi, but currently, it’s still a bit wonky. ??

No worries. I look forward to it supporting the new Gravity Forms code, since I’m interested in updating them, so I don’t need to rely on Legacy anymore.