Hi @chad171
Thanks for response!
The part of the Hummingbird’s code that reports this error first checks if the “wphb-logs” folder exists and “is writable” within content path (which usually/by default is /wp-content/ folder, unless specifically changed).
This is a “joined” check in that sense that:
– if folder doesn’t exit, it fails
– if folder does exist but is not writable – it fails as well
But only if it fails there’s a function “mkdir()” used that’s meant to create that folder – and that is the function that returns the error.
Given the check logic and the error content, it would confirm that the folder does exist but is not writeable.
I see that you have checked permissions of content inside /wp-content/wphb-logs folder but what are permissions of that folder itself?
If it’s 755 (or “drwxr-xr-x”) already, try setting it to 775. If that doesn’t help, please
– go to the “Tools -> Site Healt” page in site’s back-end -> “Info” tab and check the exact value of WP_CONTENT_DIR under “WordPress Constants” tab; see if it is correct in comparison to the actual/real path
– then check please current setting of “open_basedir” PHP option; you can do it e.g. by putthing the .php file in a root folder of your site (just remove it after it’s checked) with a following code in it
<?php
phpinfo();
?>
and visiting it in browser
– finally, please check what user/group is webserver running with and what is a user/group that “own” the wphb-cache folder on server (in case you are unsure about it, please ask your host for help).
Update us here with these information, please.
Kind regards,
Adam
