frappeweb

Tako?er mogu potvrditi isti problem. Iz nekog razloga od nedavno Solo kreira 2 fiskalizirana ra?una za istu narud?bu. I uz to ne ?alje PDF s ra?unom kupcima. Puno problema.

Evo ?to se doga?a u na?em slu?aju:

1. Kupac kupi proizvod preko Woocommerce webshopa
2. Administrator webshopa promijeni status narud?be u “Completed”
3. WordPress backend kontaktira Solo preko plugina (API), u Solo ra?unu vlasnika webshopa se kreira fiskalizirani ra?un.
4. Solo Plugin dobiva odgovor od Sola i sada treba poslati e-mail kupcu s ra?unom u PDF formatu, no to se ne doga?a
5. Administrator webshopa klika “Resend” tipku u Solo pluginu jer je iz loggova jasno da kupcu nije poslan e-mail s ra?unom
6. Prilikom klika na “resend”, WordPress backend opet kontaktira Solo preko API-ja no ponovno se kreira novi fiskalizirani ra?un za istu narud?bu, pa sada postoji duplikat, te se jedan od ra?una mora stornirati

Tako?er, u zadnje vrijeme vidimo puno Error code 100 odgovora od Sola. Usluga ne mo?e obraditi vi?e od 1 requesta unutar 10 sekundi. Da li se mo?e napraviti nekakva retry funkcija koja ?e automatski poku?ati pozvati API nakon ?to inicijalni request bio neuspje?an?

Molim vidjeti screenshot loggova:

View post on imgur.com

Tri pitanja:

1. za?to Solo ili Solo plugin kreira duplicirane fiskalizirane ra?une kada se klikne tipka “Resend”
2. za?to se e-mailovi ne ?alju klijentima. Kako mo?emo to debuggat?
3. da li mo?ete napraviti nekakvu automatsku retry funkciju kada API izbaci error code 100 da ne mo?e obraditi vi?e od 1 requesta unutar 10 sekundi?

Lijep pozdrav

Po?tovani,

rije?ili smo problem. ?ini se da je sustav za object cache kojeg smo nedavno implementirali bio uzrok problema. Nakon ?to smo ga deaktivirali, SOLO plugin je bez problema uspio poslati zahtjev prema SOLO API-ju i nije bilo nikakvih errora.

?teta ?to plugin ne radi dobro sa object cacheom. To nam je u?tedjelo velik broj database queryja. Morati ?emo prona?i na?i kako da object cache ignorira odre?ene transient objekte.

Lijep pozdrav!

Happy to help. It would be great if you could leave a review if you are happy with the Powered Cache overall ??

Of course! Thank you again for your help.

Hi @m_uysl,

we use shared hosting, so your suggestion makes a lot of sense. There is probably some issue with the way how our Memcached server works. We will contact our hosting administrators and examine this issue with them.

I’m glad that we determined that Powered Cache is working properly.
Thank you very much for your time and support.

Hi @m_uysl

We only have one WP installation on this particular hosting, and our wp-config.php has no defined WP_CACHE_KEY_SALTconstants.

There is only define( 'WP_CACHE', true ); // Powered Cache constant.

When we turn off the object cache everything appears to be working normally.

Hi @m_uysl,

I waited until I got the error again, and then ran Diagnostic test just as you recommended. I found something weird.

For some reason Powered Cache is looking for .htaccess file in /public_html/wp-admin/ folder (where it doesn’t exist). Please see screenshot here.

When I purge all cache and flush Memcache via cPanel, then Powered Cache properly looks for .htaccess in /public_html folder.

When this error occurs I also get this dashboard message (see screenshot), and WP Login page CSS appears to be broken (see screenshot).

Hope this helps in debugging.