Bug (JSON Error)
-
Hi, I am getting the following errors, nothing appears on my screens.
-
Hi @sviluppomania,
Could you enable debugging and tell me what you see there?
Kind regards,
Hessel
Deprecated: Creation of dynamic property JSON_API::$query is deprecated in /.../wp-content/plugins/json-api/singletons/api.php on line 6
Deprecated: Creation of dynamic property JSON_API::$introspector is deprecated in /.../wp-content/plugins/json-api/singletons/api.php on line 7
Deprecated: Creation of dynamic property JSON_API::$response is deprecated in /.../wp-content/plugins/json-api/singletons/api.php on line 8
Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7300
Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2189
Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7300
Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2189
Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7300
Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2189
Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /.../wp-includes/functions.php on line 7300
Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2189
Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/.../wp-includes/functions.php on line 7300
Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /.../wp-includes/functions.php on line 2189The above errors are not coming from Burst, and are just warnings, so probably not related. It may cause issues with debugging enabled though. But in that case it should be resolved by disabling debugging.
Do you have a security plugin like All In One Security enabled? We’ve had reports it blocks the request.
Can you also post the log in the browser console? You can find it by right clicking on the screen, then “inspect element”, console.
Hi @rogierlankhorst ,
The All In One Security security plugin is active on the Site.
These are the errors that appear in the Browser Console.
api-fetch.min.js?ver=4c185334c5ec26e149cc:2
GET https://www.sviluppomania.com/wp-json/burst/v1/fields/get?nonce=04964937c8&token=nbozt&_locale=user 403 (Forbidden)api-fetch.min.js?ver=4c185334c5ec26e149cc:2
POST https://www.sviluppomania.com/wp-json/burst/v1/do_action/tasks?_locale=user 403 (Forbidden)This is a known issue with the AIOS plugin. You can resolve it by disabling the 5G setting in the firewall settings of AIOS, then deactivate the plugin, then activate it again. That should resolve the issue!
But this way you can’t use the 5G setting?
@rogierlankhorst As you can see I had already disabled the 5G and 6G settings. I tried to disable and enable the Plugin again, but the statistics still don’t work.
Did you deactivate AIOS, then activate it again? because that is what is needed to clear the firewall.
The 5G setting in AIOS is deprecated, so will be removed soon anyway.
Yes, deactivated and reactivated the AIOS plugin… 5G Firewall setting deactivated.
And with AIOS deactivated, does Burst work then? just to check if there is something else in the settings.
Yes, with AIOS disabled Burst works fine.
So I found the setting that causes problems, it is this:
Is there a solution to use it and not have problems with Burst?
I was able to reproduce the issue with this setting. It shouldn’t affect it I would think, so I’ll check with their support to see why it happens.
So will there be a fix in the next update?
The topic ‘Bug (JSON Error)’ is closed to new replies.