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

Store legacy cache files in the supercache directory. #177

Merged
merged 2 commits into from Feb 9, 2017

Conversation

@donnchawp
Copy link
Contributor

@donnchawp donnchawp commented Feb 2, 2017

If we store the legacy cache files in the supercache directory it will
be much easier to maintain them as they'll be in a directory structure
that reflects the URLs served by the site, just like supercache files.
This patch checks the original blogs_cache directory first but any new
cache files will be created in the supercache directory.

If we store the legacy cache files in the supercache directory it will
be much easier to maintain them as they'll be in a directory structure
that reflects the URLs served by the site, just like supercache files.
This patch checks the original blogs_cache directory first but any new
cache files will be created in the supercache directory.
@donnchawp donnchawp self-assigned this Feb 2, 2017
With wp-cache files stored in the supercache directories we can put the
meta files in the same directory since they're separated out by URL.
@donnchawp donnchawp merged commit 3284d22 into master Feb 9, 2017
@donnchawp donnchawp deleted the legacy_files_in_supercache_dir branch May 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant