phpBB SEO Lite 1.1.1
Bug Fix & Maintenance Release
phpBB SEO Framework Lite 1.1.1 resolves critical canonical URL resolution, pagination offset, and direct post deep-linking issues.
Fixed
- Canonical Pagination & Entity Encoding:
- Resolved an issue where entity-encoded ampersands (single
&start=or double&start=) and zero-initialized global request states shadowed the query parameter, causing native paginated URLs (e.g.viewtopic.php?t=X&start=Y) to lose their offset and redirect to page 1. - Implemented recursive entity-decoding for request query strings prior to parameter extraction.
- Resolved an issue where entity-encoded ampersands (single
- Direct Post Resolution & Deep Linking:
- Resolved direct post requests (
viewtopic.php?p=POST_ID) to the specific paginated canonical URL (e.g./topic/slug-ID/page/X/#pPOST_ID) based on the post's actual position (prev_posts) within the topic and board visibility rules, ensuring the#p...DOM anchor is directly reachable. - Prevented generation of invalid phantom canonical URLs (such as
-0/) when an unresolvable post ID is requested, correctly failing closed to 404.
- Resolved direct post requests (
- Routing Parameter Sanitization:
- Stripped single- and deeply-encoded routing parameter leftovers (e.g.
?amp%3Bamp%3Bstart=20) from redirect target URLs, avoiding stray or malformed query strings.
- Stripped single- and deeply-encoded routing parameter leftovers (e.g.
- Precedence Conflict Resolution:
- Prioritized the verified post position over any conflicting or stale explicit
startparameter whenever a resolvable post ID is present, ensuring visitors land on the page containing the post. - Hardened query exclusion regex with
preg_quoteconsistency acrossRedirectResolverandPublicResourceUrlResolver.
- Prioritized the verified post position over any conflicting or stale explicit
Improved
- Clean preservation of non-routing tracking query parameters (
utm_*,gclid, etc.) preceding fragment anchors in canonical redirect targets.