Denis ?oljom

Is this a new plugin installation when you have noticed this? Or have you noticed this after a plugin update?

I think this started happening after an update. We are using premium version 5.1.0

?Can you also describe a bit when this error gets generated? Are there any particular steps to reproduce this? Have you noticed the error only once, or did you notice it being generated constantly?

Not sure what triggers this because it’s a background action and we get these issues picked up in our logs.

Have you noticed any (bad) effects coming from the error on your site or plugin functionality?

I’d say filling up error logs are the bad effects.

Does your website use WordPress Cron (WP Cron) or a server-side cron alternative?

We use WP Cron.

I also got notice in our Sentry that there are N+1 queries, mainly:

UPDATE wp_2_options SET option_value = 'serialized data' WHERE option_name = 'cron'

SELECT wp_wsal_occurrences.* FROM wp_wsal_occurrences WHERE 1 AND ( ( ( site_id = '-1' ) )) ORDER BY created_on DESC LIMIT 5

and

SELECT * FROM wp_wsal_metadata WHERE occurrence_id = 375345 AND name = 'Users'

First one has some delete action from action scheduler as a preceding span, then this options update. The second one has a preceding span with this query:

SELECT option_value FROM wp_options WHERE option_name = 'wsal_adapter-connection' LIMIT 1

The last one has this query as arepeating span:

db.sql.query - REPLACE INTO wp_wsal_metadata (id, occurrence_id, name, value) VALUES (2530994, 451402, 'Users', 'a:0:{}')

https://docs.sentry.io/product/issues/issue-details/performance-issues/n-one-queries/

Can you just let your engineering team to investigate this a bit more?

Thanks!

We don’t have nginx cache, but varnish and cloudflare, but those get purged. We are also clearing transients and cache flush because of redis, just to be safe. Then the last thing that is done is permalink flush.

The strange thing is that I’ve ssh’d to the static instance we have and ran the command manually for the URL and that worked.

I’m not sure where the problem could be tbh.

Hi!

Any movements regarding this?

iskreno nisam nikad cuo za taj dodatak.

Mislim, to samo znaci da plugini nisu testirani jedni s drugime i da mozda jedan od ta dva plugina nece funkcionirati skupa

Mozete probat aktivirati i vidjeti imate li neke errore. Ako sve radi, samo ignorirajte. Ako ne ?????♂?

Jedino da se napravi custom integracija za taj odre?eni plugin, a to bi iziskivalo neko vrijeme da se napravi (vrijeme = novac ofc).

Jedino da probate deaktivirati te pluginove i vidjeti hoce li se pojaviti error.

Nisam nikad imao ovaj problem, moram probati reproducirati lokalno.

Imate li neke pluginove koji bi mogli utjecati na ponasanje plugina?

Hmmm, ovaj problem ukazuje na neki problem sa cron eventom (pozadinski proces).

Bas sam htio napisati jeste li probali promijeniti valutu, spremiti pa vratiti natrag i spremiti. Jer obicno je to razlog zasto ne radi.

Mozete li upaliti debug i poslati debug log (bez vaseg osobnog tokena koji se nalazi u responseu)?

Nisam jos provjerio, ali cu pogledati i testirat pa mogu updateati kod na pluginu. Hvala!

Da, trebao bi biti novi order pogotovo jer se okine na hook koji sluzi da se okine kad se prebaci status u completed. Morat cu istraziti to malo da vidim da li mi se desava slicno.

Koji je $orderStatus?

Ok, znaci da plugin ok registrira hookove. Iduci korak je da se error log stavi u jedan od dva callbacka – u vasem slucaju unutar sendApiRequestOnOrderCompleted metode.

On bi se trebao okinuti kada se status narudzbe promijeni u completed.

Register bi se trebao okinuti na pocetku requesta. Znaci bilo koji reload fronta, admina i slicno bi ga trebao okinuti.

Kada stavite error_log(print_r('REGISTERED!', true)); unutar register metode u MakeApiRequest klasi, i pogledate logove, da li vidite taj string? Jer ako da, onda se registriraju ti hookovi i sve radi, ako ne, onda je negdje problem nastao.