Jason

Any updates, Afterpay?

PageSpeed Insights is flagging us for slow TBT due to your Javascript.

Third-Party

Transfer Size

Main-Thread Blocking Time

squarecdn.com

201?KiB

1,241?ms

/square-marketplace-js/chunk-analytics-vendors.js

(js.squarecdn.com)

55?KiB

763?ms

/square-marketplace.js

(js.squarecdn.com)

130?KiB

215?ms

/square-marketplace-js/chunk-placement.js

(js.squarecdn.com)

13?KiB

155?ms

/square-marketplace-js/chunk-analytics.js

(js.squarecdn.com)

3?KiB

107?ms

It would be great if you’d consider extending this plugin to remove any registered image sizes.

My issue does not need a screenshot. I am literally asking you how to replicate your demo.

Que?

I am talking about a second problem in the Braintree plugin. I provided a reference to the file which is broken, it’s a file from your plugin. Nothing to do with GoDaddy.

Thanks guys, would it also be possible to fix the issue with vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/assets/css/frontend/sv-wc-payment-gateway-payment-form.min.css referencing the non existent file sv-wc-payment-gateway-payment-form.min.css.map ? Causes unnecessary 404’s which impacts some firewalls.

Thanks,
Jason

You reckon we’ll see a fix for this, or specific details allowing a user generated patch?

This plugin has served us well.

You need to enable advanced fraud tool, and the error will only occur on a product page when you have paypal “buy now on product pages” disabled.

I modify line 134 of the plugin shown in my code excerpt above to remove the dependency.

Hi Zubair,

See https://i.imgur.com/05nksdU.png

Thanks,

Jason

Hey Peter,

Thanks for the detailed reply!

The tool used is the mariadb performance_schema, running on a live site for a few days. You’re right that it appears to be aliasing columns as fields, as the Query Monitor plugin shows that the Wordfence plugin is responsible for all the ‘SHOW FULL COLUMNS’ on wp_wfblocks7.

As it’s the biggest time sink according to the data, any improvements would be great to see! It must also be reproduceable as our site is not that special.

Cheers,
Jason

You guys need to make this plugin PHP 8.2+ compatible.

Hi Saif,

It is not simply a deprecation notice on a developers console. On a high traffic site, this issue causes massive amounts of logs – there are 10+ deprecation messages from this plugin on every page load. Multiply that by the number of visits per day and you have a recipe for catastrophe.

It also has severe performance implications when the PHP engine has to log these messages.

Can you please make sure this backlog item has sufficient severity to indicate the significance of the problem as simply “ignoring it” is not an option.

Thanks,

Jason

To avoid wasting my time, can you answer when you will test your plugin against PHP 8.2 as I asked in my first post?

Thank you!

I believe the issues come with PHP 8.2.

I too am having compatibility issues with PHP 8.x.