Plugin info

Total downloads: 1,432
Active installs: 0
Total reviews: 0
Average rating: 0
Support threads opened: 0
Support threads resolved: 0 (0%)
Available in: 1 language(s)
Contributors: 1
Last updated: 9/26/2019 (2288 days ago)
Added to WordPress: 12/7/2017 (8 years old)
Minimum WordPress version: 4.0
Tested up to WordPress version: 5.2.23
Minimum PHP version: 5.3

Maintenance & Compatibility

Maintenance score

Possibly abandoned • Last updated 2288 days ago

20/100

Is Allowed Routes abandoned?

Possibly abandoned (last update 2288 days ago).

Compatibility

Requires WordPress: 4.0
Tested up to: 5.2.23
Requires PHP: 5.3

Similar & Alternatives

Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.

Custom Page Routes
Rating 0.0/5 (0 reviews)Active installs 0
CodePeople Post Map for Google Maps
Rating 4.2/5 (31 reviews)Active installs 4,000
VenoMaps – OpenStreetMap & Privacy-Friendly Geo Maps
Rating 4.0/5 (4 reviews)Active installs 400
Xo for Angular
Rating 5.0/5 (1 reviews)Active installs 10
WP-Ultimate-Map
Rating 0.0/5 (0 reviews)Active installs 10
WordPress on Routes
Rating 0.0/5 (0 reviews)Active installs 10

Description

Define allowed routes for your website, all other routes will return a 404 error. Permalinks will be overruled.

Login, Backend routes and local files (like wp-login.php) are always available to prevent a lockout.

Also delete all your page caches after enabling to prevent unwanted routing behavior.

Use cases:

  • Absolute control over all permalinks
  • Prevent unwanted search engine indexing
  • Be sure no custom post type adds unwanted permalinks
  • No frontend needed

Important:

  • The routing overrules permalinks and works like a whitelist. Only correct entered routes will go through. You should test the routing before using on production environments
  • Be careful using several routing- or redirect plugins at the same time
  • Do not forget to delete all your page caches after enabling/disabling the routing to prevent unwanting routing behavior

Behaviour:

  • The used protocol (HTTP or HTTPS) will be ignored
  • GET params will be ignored
  • Routes are case sensitive

Syntax / Wildcards:

  • The route / allows the index page (Check the checkbox \”Allow index page\”)
  • Wildcard * allows a single term with an arbitrary value (e.g. category//page/)
  • Wildcard ** permits all possible combinations of terms (e.g. category/**) This wildcard is only allowed at the end of a route
  • Wildcards are only allowed as complete terms. Correct: /foo//bar/** Wrong: /foo/ba/test**

Installation

  1. Unzip and upload the plugin package into the plugins directory
  2. Login to the dashboard and activate the plugin
  3. Click Settings to configure the plugin

Frequently Asked Questions

No FAQ available

Review feed

No reviews available

Screenshots

  1. Example

    Example

Changelog

  • Compatibility check to WP 5; minor wording changes

  • Initial release