P
by Rolf Kristensen
1 (0 reviews)
Permalink Validator
Validates the URL used and if not matching the official permalink then it issues a HTTP 301 or HTTP 404 message.
Tested up to WP 2.6 (Current: 6.9)
v0.8
Current Version v0.8
Updated 16 years ago
Last Update on 17 Aug, 2009
Synced 16 hours ago
Last Synced on
Rank
#29,843
—
No change
Active Installs
10+
—
No change
KW Avg Position
82
—
No change
Downloads
10.8K
+2 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 20
10+
20+
3,393
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 2 more installs to reach 20+
Rank Changes
Current
#29,843
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 1 of 1| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| iis | 82 | — | Tag | 16 hours ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.8
- Last Updated
- Aug 17, 2009
- Requires WP
- 2.0.0+
- Tested Up To
- 2.6
- PHP Version
- N/A
- Author
- Rolf Kristensen
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
WP Adminify – White Label WordPress, Admin Menu Editor, Login Customizer
7K+ installs
#2,738
Master Addons For Elementor - White Label, Free Widgets, Hover Effects, Conditions, & Animations
40K+ installs
#930
The SEO Framework – Fast, Automated, Effortless.
200K+ installs
#273
Smash Balloon Social Post Feed – Simple Social Feeds for WordPress
200K+ installs
#276
VK All in One Expansion Unit
100K+ installs
#300
Frequently Asked Questions
Common questions about Permalink Validator
Permalink Validator extends the validation so besides checking the format,
then it also checks that the url is referring to something valid. The validation
of the url doesn't generate any extra overhead in database queries (unless the url requires redirection).
Why does it redirect continously when activating the plugin ?
The plugin makes a redirect when the url used to reach the page doesn't match the expected permalink url.
Some times this leads to an endless loop, which Firefox shows as:
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
* This problem can sometimes be caused by disabling or refusing to accept cookies.
This can be caused by a conflict in the htaccess / isapi_rewrite redirection rules and the given permalink structure:
If enforcing trailing back-slash and the permalink structure doesn't include it.
If this is not the case then you are very welcome to post a topic with your problem as feedback to this plugin.
Please include your permalink-structure and Wordpress version in your description of the problem.
How to exclude pages from being permalink validated ?
The Permalink Validator will pretty much validate any URL you throw at it,
but sometimes there are URL's that should not be validated.
Edit the plugin-code and replace this line:
$excludes = array();
With an array of the URL's to ignore:
$excludes = array("/forum");
Plugins that requires an URL excluded:
Subscribe to Comments - Exclude "/?wp-subscription-manager"
wp-forum - Exclude "/forum"
then it also checks that the url is referring to something valid. The validation
of the url doesn't generate any extra overhead in database queries (unless the url requires redirection).
Why does it redirect continously when activating the plugin ?
The plugin makes a redirect when the url used to reach the page doesn't match the expected permalink url.
Some times this leads to an endless loop, which Firefox shows as:
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
* This problem can sometimes be caused by disabling or refusing to accept cookies.
This can be caused by a conflict in the htaccess / isapi_rewrite redirection rules and the given permalink structure:
If enforcing trailing back-slash and the permalink structure doesn't include it.
If this is not the case then you are very welcome to post a topic with your problem as feedback to this plugin.
Please include your permalink-structure and Wordpress version in your description of the problem.
How to exclude pages from being permalink validated ?
The Permalink Validator will pretty much validate any URL you throw at it,
but sometimes there are URL's that should not be validated.
Edit the plugin-code and replace this line:
$excludes = array();
With an array of the URL's to ignore:
$excludes = array("/forum");
Plugins that requires an URL excluded:
Subscribe to Comments - Exclude "/?wp-subscription-manager"
wp-forum - Exclude "/forum"
Disallow: */feed
Disallow: */atom
Disallow: */rss2
Disallow: */rss
Disallow: */trackback
Disallow: /*/feed
Disallow: /*/atom
Disallow: /*/rss2
Disallow: /*/rss
Disallow: /*/trackback
How to make proper permalink URL's in IIS ?
Wordpress supports by default Apache htaccess and its mod_rewrite rules.
When using Wordpress on IIS then these will not work and one is limited
to this type of permalink:
http://example.com/index.php/post/hello-world/
To remove the index.php, then one can either use the custom 404 redirects
or isapi_rewrite.
If using isapi_rewrite and changing from using index.php to not using index.php,
then one can use the following httpd.ini (Assumes Wordpress is installed in the root):
[ISAPI_Rewrite]
# Rules to ensure that normal content gets through
RewriteRule /software-files/(.*) /software-files/$1 [L]
RewriteRule /images/(.*) /images/$1 [L]
RewriteRule /favicon.ico /favicon.ico [L]
RewriteRule /robots.txt /robots.txt [L]
# For file-based wordpress content (i.e. theme), admin, etc.
RewriteRule /wp-(.*) /wp-$1 [L]
# Rule to perform 301 redirect to ensure trailing back-slash on post and pages
RewriteCond Host: (.*)
RewriteRule ([^.?]+[^.?/]) http://$1$2/ [I,R]
# Rule to perform 301 redirect (Remove index.php if specified)
RewriteRule /index.php/(.*) /$1 [I,RP]
# For normal wordpress content, via index.php
RewriteRule ^/$ /index.php [L]
RewriteRule /(.*) /index.php/$1 [L]
Disallow: */atom
Disallow: */rss2
Disallow: */rss
Disallow: */trackback
Disallow: /*/feed
Disallow: /*/atom
Disallow: /*/rss2
Disallow: /*/rss
Disallow: /*/trackback
How to make proper permalink URL's in IIS ?
Wordpress supports by default Apache htaccess and its mod_rewrite rules.
When using Wordpress on IIS then these will not work and one is limited
to this type of permalink:
http://example.com/index.php/post/hello-world/
To remove the index.php, then one can either use the custom 404 redirects
or isapi_rewrite.
If using isapi_rewrite and changing from using index.php to not using index.php,
then one can use the following httpd.ini (Assumes Wordpress is installed in the root):
[ISAPI_Rewrite]
# Rules to ensure that normal content gets through
RewriteRule /software-files/(.*) /software-files/$1 [L]
RewriteRule /images/(.*) /images/$1 [L]
RewriteRule /favicon.ico /favicon.ico [L]
RewriteRule /robots.txt /robots.txt [L]
# For file-based wordpress content (i.e. theme), admin, etc.
RewriteRule /wp-(.*) /wp-$1 [L]
# Rule to perform 301 redirect to ensure trailing back-slash on post and pages
RewriteCond Host: (.*)
RewriteRule ([^.?]+[^.?/]) http://$1$2/ [I,R]
# Rule to perform 301 redirect (Remove index.php if specified)
RewriteRule /index.php/(.*) /$1 [I,RP]
# For normal wordpress content, via index.php
RewriteRule ^/$ /index.php [L]
RewriteRule /(.*) /index.php/$1 [L]
http://example.com/
And this url on IIS:
http://example.com/index.php
It can also not see the difference between this url:
http://example.com/
And this url on IIS:
http://example.com/////
This is because REQUEST_URI is not supported properly on IIS, and this
plugin can only simulate REQUEST_URI to a certain limit. Therefore
it is impossible to know whether index.php or extra slashes was specified or not.
The solution is to use a rewrite engine like ISAPI_rewrite
or IIS mod-rewrite as they can provide a proper REQUEST_URI.
Why does a non existing page give HTTP error 200 on IIS ?
Microsoft IIS fails to reply with error code 404 in the HTTP header,
when trying to access an non existing Wordpress page. This usually happens
when using a custom 404 page on IIS.
It seems that when using PHP on IIS, then it is not possible to reply
with a proper HTTP header. Apparently the only way to return a proper
404 on IIS is to use ASP.
Will Google tracking code work with this plugin ?
Google tracking code adds a question-mark (?) option to the URL, which the
Permalink Validator will strip because it is not part of the permalink URL.
Instead of using a question-mark (?), then one could use a hash (#) value,
and then modify the Google tracking code to extract the hash value
instead of the question-mark value.
And this url on IIS:
http://example.com/index.php
It can also not see the difference between this url:
http://example.com/
And this url on IIS:
http://example.com/////
This is because REQUEST_URI is not supported properly on IIS, and this
plugin can only simulate REQUEST_URI to a certain limit. Therefore
it is impossible to know whether index.php or extra slashes was specified or not.
The solution is to use a rewrite engine like ISAPI_rewrite
or IIS mod-rewrite as they can provide a proper REQUEST_URI.
Why does a non existing page give HTTP error 200 on IIS ?
Microsoft IIS fails to reply with error code 404 in the HTTP header,
when trying to access an non existing Wordpress page. This usually happens
when using a custom 404 page on IIS.
It seems that when using PHP on IIS, then it is not possible to reply
with a proper HTTP header. Apparently the only way to return a proper
404 on IIS is to use ASP.
Will Google tracking code work with this plugin ?
Google tracking code adds a question-mark (?) option to the URL, which the
Permalink Validator will strip because it is not part of the permalink URL.
Instead of using a question-mark (?), then one could use a hash (#) value,
and then modify the Google tracking code to extract the hash value
instead of the question-mark value.