[NOTICE] Updating to Version 6

Heads up: Settings migration in version 5.6.03 If you’re updating from a previous version, please read this before updating. Version 5.6.03 includes a significant internal restructuring of how your settings are stored. When the plugin updates, it will automatically migrate your existing configuration to the new format — you don’t need to do anything manually, and your headers will continue working exactly as configured. As a safety measure, a backup of your original settings will be saved to your database before the migration runs. After updating, visit the Security Headers admin page and you’ll see a notice at the top prompting you to download that backup as a JSON file. Please do this and save the file somewhere safe — once downloaded it is removed from the database and cannot be recovered. A few things worth knowing: The migration is automatic and runs once on the first page load after updating Your live settings and active headers are not affected The downloaded backup is your old configuration in its original format, purely for your records If you don’t see the notice after updating, the migration either wasn’t needed or has already completed If anything looks off with your headers after updating, the Export/Import tab is the best place to start — you can verify what’s configured there. If you run into any issues feel free to post here and I’ll take a look. This topic was modified 2 months, 1 week ago by Kevin Pirnie . Hi Kevin, We’ve just deployed the latest update to the Security Header Generator plugin (released ~9 hours ago), and it is currently causing a fatal error on our site. The error is: Composer detected issues in your platform: Your Composer dependencies require a PHP version “>= 8.4.0”. You are running 8.2.30. This is being triggered from: /vendor/composer/platform_check.php on line 22 Our environment is running PHP 8.2.30 , which aligns with your stated minimum requirement of PHP 8.2 . Issue It appears that the latest release includes Composer dependencies that now require PHP 8.4 , which contradicts the documented plugin requirements. This is resulting in a hard fatal error during plugin load, taking down the site. Impact : Site becomes inaccessible due to fatal error Plugin cannot be activated on PHP 8.2 environments Immediate rollback required on our end Request : Could you please: Confirm whether PHP 8.4 is now a required dependency (intentional or not) Advise if this is a packaging/config issue (e.g. Composer platform requirement) Provide a patched release or rollback version compatible with PHP 8.2 If helpful, I can provide additional logs or assist with testing a fix. Appreciate your help on this — keen to resolve quickly. Thanks, Lance Redgrave Redfox Digital This reply was modified 2 months, 1 week ago by lanceadam . Yes, same here. My website runs on PHP 8.3x. Unfortunately, the plugin requires PHP 8.4. I’ll push an update today. The fix is rolling out. v6.0.25 Screenshot: https://prnt.sc/bnFGPl2BKYr0 This reply was modified 2 months, 1 week ago by Kevin Pirnie .