Hi —
I am having the same issue with your plugin. I am using version 1.18.1. My site is hosted on Flywheel. Their response to this issue is the following:
Unfortunately creating a file in /wordpress/ is not something we are able to do, it is where the core WordPress files are kept and is not writable even to us.
All user files reside in /www/.
It looks like the plugin is incorrectly calling where it believes the root folder should be rather than where it is. (This is due to our de-coupled folder structure for optimal security, more and more hosts are starting to take this approach so will be in the plugins interest longer term to take a look at this).
To fix this:
The plugin author can update their plugin to correctly reference the root directory rather than where the core files are.
Would you be willing to update the plugin to fix the error?
Thanks,
Kari
Hi @karisharp
I’ll do my best to resolve this issue.
Hi Dimitar —
Have you had a chance to take a look at this issue yet? I would like to use your plugin, but am unable to do so with this error.
Thanks,
Kari
+1 for this issue. I talked to my account manager and tech support for my premium hosting. They said that, because the file structure of WordPress installations isn’t the same on every host for security or other reasons, that the location of user.ini specified by the plugin seems to look in a place where the user.ini file is for a basic WordPress file structure. Not sure if that helps or not to help solve the issue. Looking forward to a fix!
Lastly, great plugin and thank you for providing it for free. I can’t imagine the time it takes to go through each support request, especially with entitled, angry people. WordPress should have the option for authors to include a donate button on support requests if they wanted to.
– Cheers
I am also experiencing this issue on version 1.18.1.
Hosting sites on Flywheel. This was their response:
“It looks like the plugin is still working despite that Warning message in the plugin settings area. The .user.ini file would typically be found in the site root but it looks like the plugin developers are using ABSPATH to try to find the root when on our Cloud platform, where we secure the WordPress core, that constant points to /wordpress/ instead.
All that said, we still recommend that plugin for easy access to add headers to WordPress sites, and it is still functional, but we recommend reaching out to the developers to fix the warning noise there.”
The issue only appears for the sites using Flywheel’s Google Cloud hosting.
For sites hosted on Flywheel’s legacy hosting I don’t get that error and the sites (using the exact same HTTP Headers settings) score better for security than they do on the Google Cloud hosting.
Hi everyone,
Since the latest version v1.18.2 you can configure the path to .user.ini file.
To do this simply go to the Advanced menu.
Hope this solves the above issue.
P.S. Sorry for the delayed response.
