Skip to content
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

Pro Auto-Cache Engine not scheduled after upgrading from Quick Cache Lite #291

Closed
raamdev opened this issue Aug 29, 2014 · 5 comments
Closed
Assignees
Labels
Milestone

Comments

@raamdev
Copy link
Contributor

@raamdev raamdev commented Aug 29, 2014

When you upgrade to Quick Cache Pro from Quick Cache Lite and then enable the Pro-only Auto-Cache Engine feature, doing so may not trigger the cron job to be scheduled, thereby preventing the Auto-Cache Engine from running at all.

@jaswsinc writes...

The lite version sets the crons_setup option too, but it doesn't come with the auto-cache engine, so when they install the pro version, the routine that sets up the CRON jobs in pro (which does include the auto-cache engine) may never run. See: http://bit.ly/XZvEkK

Clicking the "Restore" button in Quick Cache when starting with the pro version would be a short-term solution.

I have verified that clicking the "Restore" button does fix the problem. See next comment.

If Quick Cache Options have been customized, you can backup your options first (Dashboard → Quick Cache → Plugin Options → Import/Export Options), then press the "Restore" button at the top of the options page, then Import your backed up options configuration.

@raamdev raamdev added bug labels Aug 29, 2014
@raamdev raamdev added this to the Next Release milestone Aug 29, 2014
@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Aug 30, 2014

I have verified that clicking the "Restore" button does fix the problem.

Further analysis has led me to discover that the cron job appears to get deleted after running the first time, so this "Restore" workaround will only get the Auto-Cache Engine to run one time, not at 15-minute intervals as it should.


I will prioritize this bug for the next development cycle so that we can get a fix out as soon as possible.

@ronnieg303
Copy link

@ronnieg303 ronnieg303 commented Sep 1, 2014

I am a new QC Pro user and just encountered this.
My temporary solution, which seems to work:

  • Set QC Plugin Deletion Safeguards to completely erase on uninstall.
  • Manually record any special options as required. Most installations should be pretty vanilla.
  • De-activate and uninstall QC Pro from WP Dashboard/Plugins.
  • Make sure the free version is also completely deleted if not already done.
  • Re-install QC Pro.
  • Re-configure all QC Pro options and save.

Auto-cache engine should start and run every 15 minutes. Monitor cache contents to confirm.

@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Sep 2, 2014

@ronnieg303 Thanks so much for posting your temporary solution! I'm sure others who come here will find that helpful. :)

@jaswrks jaswrks self-assigned this Sep 4, 2014
jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Sep 4, 2014
@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Sep 5, 2014

This has been fixed via Pull Request wpsharks/comet-cache-pro#76 and this fix will go out with the next release.

@raamdev raamdev closed this Sep 5, 2014
@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Sep 5, 2014

Next release changelog:

  • Bug Fix (Pro): Fixes an Auto-Cache Engine scheduling issue that may, in some scenarios, prevent it from running as expected. See #291.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants