christian70

Already done last week. Five stars.

You are totally right. I did ignore those settings at bottom of Sandbox account. Everything now works as well as expected.

You saved my life. Thank you indeed.

I updated from 6.1.2 version…

I had to re-install the plugin but I can confirm that the newest version has fixed the issue.

Thanks.

I’ve just updated to the latest version and I get error in setting page but I can’t open the page now because of a new js error:

ReferenceError: uoActive is not defined
    at wn.eval (eval at Ya (vue.min.js:6:91725), <anonymous>:3:12174)
    at e._render (vue.min.js:6:35481)
    at wn.r (vue.min.js:6:68170)
    at fn.get (vue.min.js:6:26768)
    at fn.run (vue.min.js:6:27652)
    at un (vue.min.js:6:25760)
    at Array.<anonymous> (vue.min.js:6:12466)
    at qe (vue.min.js:6:11867)

Same issue here, six sites with same error in IG feed. Is there any fixing update planned very soon?

Thanks.

I’ve just checked it, it works like a charm. Fantastic plugin, so much easier and more customizable than the rest.

Best regards.

Ok I’ve got it. I was using previous 1.31 version and after update it was not allowed to switch back to the HPOS option on because there were orders synchronization pending…

Thanks for your support.

Thank you for your reply.

I know that scheduled posts cannot be read and their urls give 404 error. So I found this workaround: a function to give them a published status instead of future one. In this way you can display future posts (posts with future date) and automatically add them to the sitemap.

• This reply was modified 1 year, 4 months ago by christian70.

Hello,

I don’t insert Paypal buttons directly, in Woocommerce based e-commerce sites I usually use a free plugin that implements Paypal payment in the checkout. So I can wrap that code with your default if-statement before Paypal is added, consistently with cookies choice.

Hello,

thank you for your reply.

That’s a very good question: in my opinion Paypal should be blocked until an explicit consent is given, because it uses cookies no matter if you decide to pay with it or not (you may want to complete the checkout by using other payment methods. Or you could change your mind and buy no items at all). These cookies become mandatory once you click on the Paypal button and decide to purchase by Paypal.

If the plugin do not block Paypal automatically, it should be done manually working on the code that loads the Paypal buttons.

• This reply was modified 1 year, 4 months ago by christian70.

I’d better say: “… when Wordfence is active”, because it doesn’t matter if Woocommerce option is enabled or not.

Thanks for your support, though.

Thank you for your quick and exhaustive reply.

In my opinion it’d be nice to be able to use the shortcode also along with the unique slug/name of the feed, not only with the id number, because it may happen to erase the feed and than to re-create it again, or to test it locally or move it to another site and its number may change.

Best regards.

I know, you are completely right. I’m using theme.json file just in order to define some rules for blocks editing (hiding what I do not need for example). It may also be empty but the error remains.

Given that the error doesn’t seem to cause any functional issue, the only solution to fix for now is deleting the file and using filters to apply similar rules.

WPML assistance is a bit complicated and they are suggesting weird solutions that do not fit in my case. I will see.

Thank you for your help, anyway.

Ok I’ve checked that the problem is the theme.json file. There is a sort of incompatibility between WPML and all themes using a theme.json file.

Thanks a lot.
I will try.