yogurt4
Forum Replies Created
-
Did it here.
app/plugins/PrivacyManager/API.php(388)
public function setComplianceStatus(string $idSite, string $complianceType, bool $enforce, string $passwordConfirmation = null) : boolLeft out this one (may be more as I get code coverage):
app/core/Settings/Interfaces/PolicyComparisonInterface.php(25)
public static function getPolicyValuesAgainstProvided($settingValue, int $idSite = null);It can be found at https://test.agenos.hu/ for the time being.
Hi,
Indeed, disabling CSP fixed the error.
Suggestions: 1. Please place a warning on the plugin UI about this, 2. handle the error in the JS code and pop up an alert with this.
I click Continue almost immediately, and wp-admin remains open (and logged in).
Hi,
It’s WP 6.8.3 + PHP 8.4 (using the official WP Docker image) and cookie-law-info.3.3.7.
The plugin was updated from 3.3.5 to 3.3.6 (when it came out) then to version 3.3.7 now.
The DB driver is PG4WP (with PostgreSQL 17.6) but the statement is logged before it’s translated to PG flavour.Duplicate of the issue PHP 8.2 – “Deprecated: Creation of dynamic property”, that was closed unresolved.
The solution would be trivial: Declare these properties at the start of the class, e.g.,
final class JJ_404_to_301{
private $admin;
private $actions;
…I’ve made a small patch file for myself that is applied to the plugin when building the container. Or you may overwrite the file with your fixed one.