Blog Sections Open

Why Friendly Pagination Rewrites Can Break TinyMCE and Other Manager Paths

How a seemingly successful rewrite from <code>?page=2</code> to <code>/page2/</code> can accidentally block manager tools and media dialogs.

Changing pagination URLs from query-based to path-based forms can look successful until an unrelated manager tool suddenly starts returning Forbidden. The reason is simple: a broad rewrite rule often catches more URLs than intended.

The Risk

If the rule that transforms pagination is not scoped tightly enough, it can alter or block requests used by TinyMCE dialogs, media browsers, or other manager-side endpoints.

Whenever you rewrite pagination aggressively, re-test manager tools and media upload flows, not just the public listing. A rewrite rule that works for the frontend but breaks content editing is still wrong.

Newer post

Fixing Intermittent CKFinder “Unknown Protocol” Errors

Why CKFinder can intermittently try to open a <code>kcact:</code> protocol URL and how to track down the manager-side integration bug.

Older post

Responding to a jQuery ScrollTo Malware Infection

Why a compromised third-party script can infect multiple sites at once and what to audit after discovering malicious code inside jQuery.ScrollTo.