Fixes external redirects and URL-encoded path matching. Settings are now kept on deactivation. Saved rules are normalised to lowercase paths the next time you save.<\/p>","1.0.0":"
Initial release \u2014 no upgrade steps required.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3543071,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":3543071,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The PathGuard Redirects settings page showing the blocked URLs list, redirect action selector, and Exclude Admins option.","2":"The Settings action link on the WordPress Plugins list page."}},"plugin_section":[],"plugin_tags":[1912,263896,727,600,263895],"plugin_category":[54],"plugin_contributors":[254156],"plugin_business_model":[],"class_list":["post-315366","plugin","type-plugin","status-publish","hentry","plugin_tags-access-control","plugin_tags-block-pages","plugin_tags-redirect","plugin_tags-security","plugin_tags-url-blocker","plugin_category-security-and-spam-protection","plugin_contributors-emily50","plugin_committers-emily50"],"banners":{"banner":"https:\/\/ps.w.org\/pathguard-redirects\/assets\/banner-772x250.png?rev=3543071","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/pathguard-redirects\/assets\/icon-256x256.png?rev=3543071","icon_2x":"https:\/\/ps.w.org\/pathguard-redirects\/assets\/icon-256x256.png?rev=3543071","generated":false},"screenshots":[],"raw_content":"\n
PathGuard Redirects is a lightweight, developer-friendly plugin that lets site administrators block any relative URL on their WordPress site and control exactly what happens when a visitor tries to access it.<\/p>\n\n
How it works<\/strong><\/p>\n\n Add the relative paths you want to block (one per line) and choose what should happen when someone visits them:<\/p>\n\n Key features<\/strong><\/p>\n\n Security<\/strong><\/p>\n\n Enter paths relative to your site home, one per line. Example:<\/p>\n\n If you paste a full URL, it is converted to its path when you save. Paths are matched with or without a trailing slash and regardless of case.<\/p>\n\n If WordPress is installed in a subdirectory (e.g. No \u2014 by default the Exclude Admins<\/strong> option is enabled, which means logged-in users with the Yes. Enter any full URL (e.g. The plugin falls back to serving the 404 page so the blocked URL is never accidentally left accessible. The same happens if the destination is itself a blocked URL, which would otherwise cause a redirect loop; the settings page shows a warning in that case.<\/p><\/dd>\n No. The block logic runs on the No. PathGuard Redirects blocks the URL, not the content. A blocked page's content can still be reachable through the REST API (e.g. The plugin purges supported page caches when you save, so pages cached before a rule was added are not served. Caches that run outside WordPress (server-level caches such as Varnish or Nginx FastCGI cache, or a CDN) must be purged manually after changing rules.<\/p><\/dd>\n No. Settings are kept on deactivation. They are removed from the database only when you delete the plugin from the Plugins screen.<\/p><\/dd>\n No. Only the path portion of the URL is compared (e.g. \n
\n
\/secret-page\/<\/code>, \/members-only\/<\/code>).<\/li>\n\/secret-page<\/code>, \/secret-page\/<\/code> and \/Secret-Page\/<\/code> all match.<\/li>\n\/%73ecret-page\/<\/code>. Non-ASCII paths (e.g. \/caf\u00e9\/<\/code>) are supported.<\/li>\npathguard_redirects_rules_updated<\/code> action).<\/li>\n<\/ul>\n\n\n
manage_options<\/code>) before processing any form data.<\/li>\nsanitize_text_field<\/code>, esc_url_raw<\/code>, sanitize_key<\/code>).<\/li>\nesc_textarea<\/code>, esc_attr<\/code>, esc_html_e<\/code>).<\/li>\n\n
pathguard-redirects<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
What URL format should I use in the blocked URLs list?<\/h3><\/dt>\n
\/secret-page\/\n\/members-only\/\n\/private-area\/\n<\/code><\/pre>\n\nhttps:\/\/example.com\/blog\/<\/code>), enter paths relative to that directory: \/secret-page\/<\/code>, not \/blog\/secret-page\/<\/code>.<\/p><\/dd>\nWill administrators be blocked?<\/h3><\/dt>\n
manage_options<\/code> capability can always access blocked URLs. You can uncheck this option to apply blocking to administrators as well.<\/p><\/dd>\nWhat is the difference between the two redirect actions?<\/h3><\/dt>\n
\n
Can I redirect to another website?<\/h3><\/dt>\n
https:\/\/example.com\/<\/code>). You can also enter a path such as \/home\/<\/code>, which is resolved against your site home.<\/p><\/dd>\nWhat happens if I choose \"Custom URL\" but leave the destination field blank?<\/h3><\/dt>\n
Does this plugin affect REST API or admin requests?<\/h3><\/dt>\n
template_redirect<\/code> hook which only fires for standard frontend page requests. REST API, WP-CLI, and admin requests are unaffected.<\/p><\/dd>\nDoes blocking a URL make its content private?<\/h3><\/dt>\n
\/wp-json\/wp\/v2\/pages<\/code>), RSS feeds, site search, and XML sitemaps. To keep content private, set the post to Private or password-protect it.<\/p><\/dd>\nDoes it work with page caching?<\/h3><\/dt>\n
Will my settings be lost if I deactivate the plugin?<\/h3><\/dt>\n
Does the plugin block query strings?<\/h3><\/dt>\n
\/secret-page\/<\/code>). Query strings like ?preview=true<\/code> are ignored, which means \/secret-page\/?anything=value<\/code> is still blocked by the rule \/secret-page\/<\/code>.<\/p><\/dd>\n\n<\/dl>\n\n\n1.1.0<\/h4>\n\n
\n
\/%73ecret-page\/<\/code>) and non-ASCII paths (e.g. \/caf\u00e9\/<\/code>) are now matched correctly.<\/li>\n\/home\/<\/code> can now be saved.<\/li>\npathguard_redirects_rules_updated<\/code> action.<\/li>\n1.0.0<\/h4>\n\n
\n
rawurldecode()<\/code>.<\/li>\n