Automattic / Automattic/wp-super-cache

Handle flat permalink structure with more than 32K posts

Open
#909 2 comments 0 reactions 0 assignees View on GitHub
[Plugin] Super Cache bug
Dominant language
PHP
Stars
436
Forks
130
Avg merge
15h 11m
Merged PRs (30d)
10

Description

As mentioned in the help pages:
> ### How many pages can I cache? ###
> The only real limit are limits defined by your server. For example, EXT2 and EXT3 allow a maximum of 31,999 sub directories so if you have a flat permalink structure (like /%POSTNAME%/) and more than 32,000 posts you may run into problems. Likewise, if you run a multisite network and have more than 31,999 sites (blogs) you won't be able to cache all of them. Realistically if you had that many active sites you wouldn't be running on one server.

I see that one of my sites might reach that limit in a couple of months, and would like to ask to not be forced to change my flat permalink structure. Would it be possible to have an option for wp-super-cache to use sub folders (say /year/post-name in the cached folder) without forcing me to change my permalink structure?

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file, test, or entry point is named. Start by tracing how wp-super-cache chooses directories for cached flat permalinks, then determine where an optional nested cache path could be configured without changing the public permalink; done means supporting sites with more than 32,000 posts while preserving existing URLs and cache behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
backend, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.