@uvwcreation the plugin uses standard php functions like is_writable() and file_exists() to check for these capabilities.
Possibly the path structure has changed? If the path is the same, and the css file is still there, the plugin should be able to load the css at least.
A first step to check is if the path in the html source is correct. If you search for ‘css_file’, and check if the path behind it points to the correct directory, you can check if it is correct, check if the corresponding folder contains the css file, and if the url can load in the browser, showing the contents of the css file.
If you can post your website we can take a look ourselves.
Hello,
thank you for looking into this. Currently, the page source contains the following (domain anonymized for security reasons, that is also why I cannot post the website here):
“css_file”:”https:\/\/www.mydomain.com\/wp-content\/plugins\/complianz-gdpr\/cookiebanner\/css\/defaults\/banner-{type}.css?v=34″
This does not change after saving the display settings (those seem correct and differ from the default).
By FTP, I found out that files like /wp-content/uploads/complianz/css/banner-1-optin.css and a preview version of the same exist. Both were created in september of this year (without changing anything afterwards).
By help of a minimal plugin I checked that is_writeable returns false for the folder /wp-content/uploads and /wp-content/uploads/complianz, but true for subfolders like /wp-content/uploads/2023. The function file_exists does not even return true for /wp-content/uploads/complianz.
I will inform you here if re-adding the permissions to this folder helps.
Alas, for some strange Windows reasons, it is not possible set permissions to /uploads/complianz or its content anymore. On reinstallation of the plugin, the folder cannot even be created at all.
Strange thing is, it worked before and nobody changed any settings.
I leave this thread open in case there is any idea to solve the issue.