Cookie Policy saving issue

Thanks for the report and for the URL, that detail actually tells us exactly what is happening.

The Cookie Policy generator saves through JavaScript: when you click Save Changes the script intercepts the form, validates it, and sends the data to the plugin via a background request, without reloading the page. The address you landed on:

/wp-admin/admin.php?company.name=&company.address=&…

is what a browser produces when it submits a plain HTML form with no JavaScript running. In other words, on your site that script is not running on the generator page, so the browser falls back to a normal form submit and you end up on a blank admin.php page with the empty fields in the URL. The Preview button does nothing for the same reason (it is also driven by that script). The form itself is fine, this is the page script not loading or being interrupted.

This is almost always one of three things, and it lines up with your note that it worked a few weeks ago:

1. A JavaScript conflict from another plugin or the theme. If any other admin script throws an error on that page, it can stop our script from initialising.
2. A caching or JS optimization/minification plugin that defers, combines, or strips admin scripts. These can break admin pages even when the front end looks fine.
3. A stale cached copy of the plugin script after an update.

Could you help us pin it down:

1. Open the browser developer console (press F12, then the Console tab), go to the Cookie Policy page, reload it, click Save Changes, and copy any red error messages you see. Those errors usually name the conflicting script directly. Paste them here.
2. Quick conflict test: temporarily switch to a default theme (Twenty Twenty-Four) and/or deactivate your other plugins, then try saving again. If it works, re-enable them one by one to find the culprit.
3. If you use any caching or JS optimization plugin, clear its cache (and your browser cache) and exclude the wp-admin area / the FAZ admin scripts from minification and combining.
4. Make sure FAZ Cookie Manager is updated to the latest version.

With the console errors we can usually identify the exact conflict quickly.

On my side, I’m also adding a safeguard so that, even if the page script is blocked for any reason, the form will no longer do a blank-page native submit, it will tell you to reload instead, so you never lose what you typed. That will ship in an upcoming release.

Thanks for your patience, and looking forward to those console messages.

Best regards