Ajax Bug report for 3.72

Hello @sygnoossupport,

we just noted a reproducible Ajax bug in version 3.72. We guess it should have got something to do with your newest Ajax modifications.

The bug occurs when you access a popup website without being logged in into WordPress. We only tried it with being logged in as WordPress admin on the other hand – just for you to know.

So if you access a popup website and you are not logged in as an admin you get the following console error log in Firefox (Chrome is equivalent):

XHR POST https://[DOMAIN.TLD]/wp-admin/admin-ajax.php [HTTP/2 400 Bad Request 574ms]

Request
action=sgpb_send_to_open_counter&nonce=2e661123a9&params%5BpopupsIdCollection%5D%5B1669%5D=1

Response
0

send https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:4:26428
ajax https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:4:22034
n[b] https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:4:23029
SGPBPopup.listeners/< https://[DOMAIN.TLD]/wp-content/plugins/popup-builder/public/js/PopupBuilder.js:172:10
(Async: setInterval handler)
SGPBPopup.listeners https://[DOMAIN.TLD]/wp-content/plugins/popup-builder/public/js/PopupBuilder.js:156:13
<anonym> https://[DOMAIN.TLD]/wp-content/plugins/popup-builder/public/js/PopupBuilder.js:2844:13
(Async: setTimeout handler)
<anonym> https://[DOMAIN.TLD]/wp-content/plugins/popup-builder/public/js/PopupBuilder.js:2842:12
i https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:2:27362
fireWith https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:2:28121
ready https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:2:29914
J https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:2:30276
(Async: EventListener.handleEvent)
n.ready.promise https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:2:30469
<anonym> https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:2:30819
<anonym> https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:2:207
<anonym> https://[DOMAIN.TLD]/wp-includes/js/jquery/jquery.js:2:212

As soon as you log in and reload the page, the error is gone. When you log out and reload it, the error is back again. Also if we rollback your plugin’s version to 3.71 the error is gone – even for not logged in visitors.

Thanks for your work and fixing this,
-doffine