-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-Cache Engine fails silently when allow_url_fopen=0 #644
Labels
Milestone
Comments
raamdev
added a commit
to wpsharks/comet-cache-pro
that referenced
this issue
Dec 28, 2015
raamdev
added a commit
to wpsharks/comet-cache-pro
that referenced
this issue
Dec 28, 2015
raamdev
added a commit
to wpsharks/comet-cache-pro
that referenced
this issue
Dec 29, 2015
Next Pro Release Changelog:
|
ZenCache v160103 has been released and includes changes from this GitHub Issue. See the v160103 announcement for further details. This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#644). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When
allow_url_fopen
is disabled via the PHP configuration, the Auto-Cache Engine cannot read the XML Sitemap and silently fails with a PHP Warning:Until we take a closer look at falling back on cURL for reading the XML Sitemap when
allow_url_fopen
is disabled (see #440), we should move forward with detecting whenallow_url_fopen=0
and showing a Dashboard error notice to site owners when the Auto-Cache Engine is enabled.This should work the same way as the error handling for checking the XML Sitemap itself, where the issue is checked on each
admin_init
and the error message cleared automatically when the error goes away. That way if a site owner setsallow_url_fopen=1
on their server and refreshes Dashboard, the error goes away automatically.While this isn't strictly a bug, I'm marking it as a bug because for site owners on servers where
allow_url_fopen=0
, there is no indication of any problem. Rather, the Auto-Cache Engine simply appears to not work at all.The text was updated successfully, but these errors were encountered: