The module stopped working

[d3fes]

Description

It could happen, because I upgraded the plugin version from 4.0.5 to 4.0.6, but the issue is that now I cant use it because I get the error "The JSON response is not a valid."

WooCommerce version: 10.1.2
WordPress version: 6.8.2

Screenshots

Additional information

No response

[picocodes]

Hi @d3fes, which screen is this?

[d3fes]

@picocodes that's the error I get on all the pages

[picocodes]

Okay. Do you notice any errors in your PHP error logs?

…

On Fri, Sep 5, 2025, 09:12 d3fes ***@***.***> wrote: *d3fes* left a comment (hizzle-co/noptin#1062) <#1062 (comment)> @picocodes <https://github.com/picocodes> that's the error I get on all the pages — Reply to this email directly, view it on GitHub <#1062 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEYCZ4F66OKTIOESXB65OG33RESUTAVCNFSM6AAAAACFUZA7NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJXGE4DQMZZGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[d3fes]

no PHP errors related to this plugin

[d3fes]

I am not able to adjust the settings as well

I tried to re-install, but it saves the settings because of this setting I did in the past.

[picocodes]

“Not a valid JSON response” almost always means something on the site is printing output or throwing PHP notices before WordPress sends the REST response. That can happen even if the error isn’t in Noptin.

Please try the following in order:

1. Check for PHP output/errors during REST calls. In wp-config.php, set WP_DEBUG and WP_DEBUG_LOG to true and WP_DEBUG_DISPLAY to false, then reproduce the error. Review wp-content/debug.log and your server/PHP error log for any notices, warnings, or fatal errors at the same timestamp as the failed request. If you see anything, fix/disable the offending code and test again. Also, ensure display_errors is off in PHP so notices aren’t injected into JSON.

2. Inspect the actual REST response. From the browser dev tools “Network” tab, open the failing request and check the Response tab for stray whitespace/HTML before or after the JSON, and confirm the Content-Type header is application/json. If you can, share the exact response body and headers.

3. Version check. If the issue started right after updating from 4.0.5 to 4.0.6, please try rolling back to 4.0.5 to confirm whether it’s a regression on your site or an environmental change that coincided with the update. If 4.0.5 works and 4.0.6 doesn’t, let us know.