Alfio Piccione

Hi @omarfpg

I did what you suggested, installed Jetpack, disconnected the account and reconnected.

I also tried to deactivate SG Speed ??Optimizer, but nothing changed.
I contact you via woocommerce support, for now I have no other ideas ??

Thanks!

Hi @carolm29
I deleted the plugin, reinstalled it but unfortunately it doesn’t change anything.

Thanks for your support but I don’t know what to do anymore…
it’s all very strange

Hi @doublezed2
other info, I activated the test mode for a moment and the problem remains
https://postimg.cc/672rxvJh

Hi @doublezed2

mmm strange this morning the error wasn’t present, now instead it is..
https://snipboard.io/lWpEuq.jpg

Hi @carolm29,

This morning before trying to switch to test mode on the live site, I checked the checkout and inexplicably now I do not see the error … can you confirm it for me too ?

very strange… at this point I wonder what caused the error the past few days?

Thanks!

Hi @carolm29

Yes, I tell you that all the plugins are the same and they are all the same version, as mentioned the only difference is the safe mode of WooPayments.

for more details I will provide you with the staging status report
https://gist.github.com/Picaland/3bdf53deef829d1ea43542c1a835df70

Hi @rajeshml

Yes thanks for your intervention, I am also a wordpress developer and I know the conflict tests.

but apart from that, I created a staging https://staging4.woopop.it/ from the live site, where the only difference is the safe mode of WCpayments

here I do not find errors.

Curious as what….

Hi @omarfpg

By disabling the WooCommerce Stripe Gateway plugin from anonymous and not logged in I get the error in the console.. how can we solve it? I also tried to disable the cache plugin but the error remains.

Hi @omarfpg
I deactivated the WooCommerce Stripe Gateway plugin which was active but not used as a payment gateway. I currently only use WooPayments, so do you still encounter the same problem?

Hi @omarfpg

The Siteground Speed ??Optimizer caching plugin doesn’t have many configurations, I excluded the recommended WC pages from the cache and the /checkout/ page is definitely excluded

I still can’t find the errors in the console whether logged in or not

but I can’t do anything other than disable the minidication and combination of js. could that be the problem?

Grazie, segno come risolta la richiesta di supporto.

@matteomangia2
Grazie!! ??

@johnatan72 Grazie Mille!

@johnatan72 no la funzione non dovrebbe creare problemi.
Ma come detto via mail. ho controllato un’ordine è sembra tutto corretto.

E stato fatto anche un test per controllare il blocco del checkout nel caso in cui il campo codice fiscale sia vuoto.
Anche in questo caso non ho riscontrato problemi.

@johnatan72

nel checkout c’è un campo CF che non è quello di WooPOP.
vedi allegato (campo segnato in rosso)

A parte questo mi sembra tutto corretto.
Siete sicuri che il campo valorizzato sia quello giusto e che questo campo non crei conflitti ?

Per capire maggiormente servirebbe avere accesso al sito e fare dei test.
può inviarmi i dati di accesso tramite mail: support[@]woopop.it

Grazie!

• This reply was modified 1 year, 2 months ago by Alfio Piccione.