pressidium

Hey, @mmtomm!

The plugin doesn’t support this natively. You’ll likely need to rely on custom JavaScript or CSS, like @kingofmycastle suggested.

Hey, @kemuricodes!

To keep things clear and easy to reference, it’s best to comment on the original thread rather than creating duplicates.

I’ll mark this as resolved, and we can continue the discussion there: https://ww.wp.xz.cn/support/topic/request-to-adjust-heading-structure-for-better-seo/

Hey, @kemuricodes!

The <h2> change was inherited from the cookie consent library we use (ref). Reverting that change would mean deviating from the library, which could slightly complicate future maintenance. We’ll have to factor that in.

That being said, you make a good point and we’ll likely adjust that in a future release.

Additionally, you can enable the “Hide from bots” option (wp-admin → Cookie Consent → General → Hide from bots), which automatically parses the user agent to detect bots/crawlers/webdrivers, and hide the cookie consent banner from them.

Hello, @tomaobretenov!

after refreshing the page, nothing was saved

This might be related to a conflict with another plugin or a possible bug in Pressidium Cookie Consent.

To rule out the possibility of a plugin conflict, could you try disabling any security plugins (which might block the REST API) and optimization plugins (that handle caching or minifying JS), and let us know whether the issue persists?

Could you also check if the WordPress REST API is disabled, either via custom code or a third-party plugin?

If it turns out to be a plugin conflict, please share the name of the conflicting plugin with us. If it’s not, we’d appreciate it if you could provide the following details to investigate further:

1. Steps to reproduce – Detailed steps to reproduce the behavior.
   • Go to ‘…’
   • Click on ‘…’
   • Scroll down to ‘…’
   • See error
2. Screenshots – If applicable, add screenshots to help explain the problem.
3. Environment – Please provide the following information:
   • Browser (e.g. Chrome, Firefox)
   • Plugin version (e.g. 1.7.1)
   • WordPress version (e.g. 6.7.1)
   • PHP version (e.g. 8.1)
4. Server logs – If applicable, include any server logs that could be related to this issue.
5. Browser console logs – If applicable, include any warnings/errors in your browser’s console. You can open the Console panel in Google Chrome, using ⌘ + ⌥ + J on macOS, or CTRL + Shift + J on Windows/Linux.

Hey, @surbma!

I expect the English language texts should be automatically added, when a new English language is added, whatever Country is selected for that language. Or at least you should add a button to auto-load default texts for English.

Thanks for your input! This has already been suggested and it’s tracked as issue #47 on the plugin’s GitHub repository.

This way, when a new language is added, it should be auto loaded with the default texts.

Another solid suggestion! I’ve opened issue #109 to explore implementing it in a future release.

Hey, @lebro!

the domain set is correct

The “Cookie Domain” setting in wp-admin → Cookie Consent → General has been configured incorrectly.

It should be formatted as:

example.com

but the link you shared follows this format instead:

www.example.com/

Could you please update the “Cookie Domain” value and let us know if that fixes the issue?

Hey, @jookk!

Right now, our plugin doesn’t include shortcodes to automatically list cookies for a dedicated Cookie Policy page. However, all cookies are displayed in the consent settings modal, accessible via the floating settings button.

To enable the floating button, navigate to wp-admin → Cookie Consent → Floating Button, and turn on the “Enabled” toggle.

I’ve also opened a feature request (GitHub #106) to consider implementing shortcodes and/or blocks in a future update of the plugin. Keep an eye on its progress.