PermaLinks conflict

Wed, 11 Feb 2026 15:41:51 -0800

Thanks Jeff!

PermaLinks conflict

Wed, 11 Feb 2026 13:03:36 -0800

It doesn't need to be quite so specific, this will do it nicely:

RewriteEngine On

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !/$
RewriteRule ^(.*)$ /$1/ [R=301,L]

PermaLinks conflict

Wed, 11 Feb 2026 12:58:12 -0800

So, to enforce the slash at the end of domain urls, in .htaccess you have something like this at the top (or above any kind of cms rules...like with WP)?


RewriteEngine On
RewriteBase /
# Exclude actual files from the rule
RewriteCond %{REQUEST_FILENAME} !-f
# Redirect to trailing slash if not ending with one
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.*)$ https://yourdomain.com/$1/ [L,R=301]

PermaLinks conflict

Tue, 10 Feb 2026 14:30:15 -0800

Same here, Jeff. I got tired of Google fighting me with canonical issues so everything gets a slash at the end

PermaLinks conflict

Tue, 10 Feb 2026 14:27:45 -0800

personally I set my htaccess rules to enforce the trailing slash, much cleaner in the long run as that is what the permalinks expects, still solves the seo noise

PermaLinks conflict

Sun, 08 Feb 2026 03:08:16 -0800

hello thanks for your feedback, i have a rule in my .hta access to remove slash from end of any URL to avoid duplicate issues for SEO but it seems it had broken the rewrite rules

i tried alot of things , but in the end i defined the admin folder as perma link and it worked, the password is working as well


    RewriteEngine On

    ##########################################
    # CANONICAL DOMAIN (www → non-www)
    ##########################################
    RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
    RewriteRule ^ https://%1%{REQUEST_URI} [R=301,L]

    ##########################################
    # REMOVE TRAILING SLASH (FILES & DIRS SAFE)
    ##########################################
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} .+/$
    RewriteRule ^(.+)/$ /$1 [R=301,L]

    ##########################################
    # FRONT CONTROLLER DISPATCH
    ##########################################
    RewriteRule ^permalinks_dispatcher\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /permalinks_dispatcher.php [L]

PermaLinks conflict

Tue, 03 Feb 2026 18:24:31 -0800

Hi moh3,

So in .htaccess we have something like this that checks to the see if the URL or permalink exists as a file or directory. If it doesn't it passes the request to the dispatcher:

### Pass URL to permalinks dispatcher (do this last after any other redirects)
RewriteRule ^permalinks_dispatcher\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /cmsb/plugins/permalinks/permalinks_dispatcher.php [L]

But if you're password protecting your admin folder with .htaccess and .htpasswd, that can interfere with the directory detection and redirect.

You can try adding a condition to skip your admin folder when processing permalinks. Something like this:

### Pass URL to permalinks dispatcher (do this last after any other redirects)
RewriteRule ^permalinks_dispatcher\.php$ - [L]
RewriteCond %{REQUEST_URI} !^/cmsb/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /cmsb/plugins/permalinks/permalinks_dispatcher.php [L]

Let me know if that works for you!

PermaLinks conflict

Tue, 03 Feb 2026 08:43:15 -0800

Hello i'am using perma links and the admin folder is rewritten with the dispatcher ,any idea what the issue is? i'm moved the dispatcher to the roor directory as im protecting the admin folder with password