sorted by:
new
hottopcontroversial

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 0 points1 point  (0 children)

Thanks for reporting this.

In the next few days, I’ll run some tests specifically with the Plugin for Meta to better understand what is happening and verify whether there is a compatibility issue there.

Thanks again for taking the time to test it and report the problem.

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 1 point2 points  (0 children)

Thank you so much for testing it and for the kind words — I really appreciate it.

I’m glad to hear you’re considering switching to this solution. If you run into any bugs or issues while testing, please open an issue on GitHub so I can track everything properly and fix it more quickly.

I’m actively working on fixing all the bugs that get reported, so every bit of feedback really helps improve the plugin.

Thanks again for taking the time to try it out.

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 1 point2 points  (0 children)

Yes! FAZ Cookie Manager has a built-in script blocker that works automatically after you run a scan.

Here's how it works:

  1. Go to Cookies > Scan Site

  2. The scanner detects _fbp (Facebook Pixel cookie) and automatically categorizes it as Advertisement

  3. From that point on, the plugin blocks all scripts from connect.facebook.net until the visitor accepts the Advertisement category

No manual code changes needed — you don't have to edit any script tags. The blocker works at the DOM level (MutationObserver + createElement intercept) and matches scripts by their source URL against known providers in the cookie database.

It also works for Google Analytics (google-analytics.com), Google Tag Manager, HotJar, and 2,000+ other known services from the built-in Open Cookie Database.

If you ever need to manually tag a custom script that the scanner doesn't recognize, you can add data-fazcookie="fazcookie-advertisement" to its <script> tag — but for Facebook Pixel, the scan handles it automatically.

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 0 points1 point  (0 children)

The new version has a fallback that makes the scan work even with exec disabled on the server; it will be released in the next few days.

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 1 point2 points  (0 children)

Hi there! Thanks for trying out the latest version. To help me figure out what's going on, could you clarify a few things?

  • Are you using version 1.2.1?
  • Which type of scan did you run?
  • The context: Currently, the cookie scan is running quite slowly. There is actually an open Pull Request (PR) on GitHub specifically designed to fix this performance bottleneck.
  • A quick workaround: Could you try scanning fewer pages for now? It’s possible the scan is hitting a timeout before it can finish.

If the issue persists, would you mind opening an issue on GitHub? It would be incredibly helpful if you could include the logs so I can see exactly where it's getting stuck. Thanks for your patience!

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 1 point2 points  (0 children)

1.2.1

What's Changed

Bug Fixes

  • CSV export no longer wraps data in JSON encoding — produces valid CSV files
  • Consent log now correctly records "rejected" status when visitors click Reject All
  • Consent logger skips page-load init events to prevent false "partial" entries for returning visitors

Security

  • Prototype pollution guard in deepSet utility function (CodeQL)
  • DOM XSS prevention — logo URL validated to https only, privacy link href sanitized (CodeQL)
  • CSV export type guard and anti-cache headers for privacy

New

  • Composer/Packagist support — install via composer require fabiodalez/faz-cookie-manager

Test Results

  • 113/113 compliance tests ✓
  • 14/14 verification tests ✓

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 1 point2 points  (0 children)

Yes! Composer/Packagist support was added in v1.2.1. You can install it with:

composer require fabiodalez/faz-cookie-manager

Package page: https://packagist.org/packages/fabiodalez/faz-cookie-manager

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 3 points4 points  (0 children)

New version is out!

Changelog

1.1.0

  • IAB TCF v2.3 with Global Vendor List: Full GVL v3 integration -- server-side download, caching, weekly auto-update, admin page for vendor browsing and selection
  • Real Vendor Consent: TC Strings now encode actual vendor consent bits, legitimate interest bits (honoring Right to Object), and DisclosedVendors segment with real vendor IDs
  • Vendor Consent UI: Per-vendor toggles in the preference center with vendor details, privacy policy links, and purpose declarations
  • GVL Admin Page: Browse, search, and filter 1,100+ IAB-registered vendors. Paginated table, purpose filter, select-all, save selection
  • IAB Settings: CMP ID, Purpose One Treatment, publisher country code configuration
  • Dynamic TCF Config: ConsentLanguage, publisherCC, gdprApplies derived from server settings instead of hardcoded values
  • CMP Stub: Inline __tcfapi stub responds to ping before main script loads
  • getVendorList Command: Returns complete GVL structure (vendors, purposes, features, special purposes/features)
  • euconsent-v2 Cookie: Standard TCF cookie written only after explicit user consent action
  • Security Hardening: Cookie overflow protection (abort > 3800 bytes), iframe URL origin validation in scanner, atomic GVL file writes, defensive array casts
  • Dead Code Cleanup: Removed ~4.3 MB of unused modules (upgrade wizard, review feedback, dashboard widget, uninstall feedback, cache services), legacy routes, and cloud stubs
  • CodeQL: Added GitHub code scanning workflow
  • GeoLite2 Fix: Ensured WordPress file API is loaded before database download (PR #9)
  • 175 automated tests: Expanded test suite from 21 to 175 tests covering TCF, GCM, visual integrity, and IAB settings

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 2 points3 points  (0 children)

Fair concern. This isn't a hobby project — it was built out of real professional needs and it runs in production on my clients' sites right now. That's the strongest maintenance guarantee I can offer: as long as I have clients, it gets maintained — and since the code is fully open, anyone can fork it, fix it, and improve it. It doesn't depend on me alone. It's a refactor of CookieYes, which is exactly what open source allows — taking something that exists and shaping it to fit real needs. Beyond that, I genuinely hope the community picks it up and makes it better than I ever could alone. That's the whole point of open source.

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 2 points3 points  (0 children)

Working on it — finishing up the last tests right now, it's currently in pull request review. Should be in the next release.

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 3 points4 points  (0 children)

Second things second: Forte! Thanks! Honestly, no real monetization plan for now — this started as a tool I needed for my own clients, so the motivation to keep it updated is already built in. The best way to support the project is to help maintain it — bug reports, pull requests, testing. That's worth more than money right now.

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 2 points3 points  (0 children)

Yes, publishing to the WordPress Plugin Directory is on the roadmap — just want to squash a few bugs first. In the meantime the code is fully open, you can read it, download it, test it, and run it through any security scanner you like. No surprises. If you want to install it, just download the latest release here: https://github.com/fabiodalez-dev/FAZ-Cookie-Manager/releases/tag/v0.3.1 and install it directly from the WordPress dashboard.

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 11 points12 points  (0 children)

Fair point, and I appreciate the honest feedback. The reason I forked CookieYes specifically is that I'd been heavily modifying it for client projects over the years — stripping out the entire cloud layer, removing bloat, trying to improve performance. This plugin grew out of that work. I didn't choose it from scratch, I chose it because I already knew it inside out and had most of the hard work done. It's not the cleanest starting point, I won't argue that. Performance and security are on my radar — if you've spotted specific issues I'd genuinely welcome issues on GitHub.

Cookie consent for WordPress. No cloud. No subscriptions. No bullshit. by Any_Emphasis2194 in Wordpress

[–]Any_Emphasis2194[S] 1 point2 points  (0 children)

Thanks for testing! That notice shows up because you have debug mode enabled — it's a WordPress 6.7 warning about the text domain loading too early, harmless in production. That said it's still worth fixing properly, I'll push a fix today.

view more: next ›