Another 404 issue - apologies
I'm using Joomla 5 on a Windows server 2022 and IIS10, but Sendy doesn't work correctly when moving to a different page. If I manually add .php to the end of the page URL it displays correctly.
The .htaccess file is present in the sendy folder and I've followed the instructions to add RewriteBase /sendy after RewriteEngine On but it has no effect.
Is anyone else using sendy on a Joomla site and knows of a fix to this issue?
This discussion has been closed.
Comments
Hi,
The cause is that IIS ignores
.htaccessfiles, so theRewriteBase /sendyedit does nothing..htaccessis an Apache feature. Sendy's clean URLs (like/sendy/subscribersinstead of/sendy/subscribers.php) depend on those rewrite rules, which is why adding.phpby hand works.On IIS you need the same rules in a
web.configfile, using the URL Rewrite module.sendyfolder, and open URL Rewrite..htaccessfile and click Import. IIS converts the Apache rules toweb.configformat automatically. Click Apply./sendy/web.config:<?xml version="1.0" encoding="UTF-8"?> <configuration> <system.webServer> <rewrite> <rules> <rule name="Sendy add php" stopProcessing="true"> <match url="^(.*)$" /> <conditions> <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" /> <add input="{REQUEST_FILENAME}.php" matchType="IsFile" /> </conditions> <action type="Rewrite" url="{R:1}.php" /> </rule> </rules> </rewrite> </system.webServer> </configuration>Sendy's
.htaccessalso has rules for tracking and subscribe links (/l/,/t/,/w/,/subscribe/,/unsubscribe/). Those need translating as well, which is why the Import Rules route is safer than the hand-written version.One more thing to check. Joomla's own
web.config(or root rewrite rules) can catch requests before Sendy sees them. If the 404 persists, make sure Sendy is in its own subfolder with its ownweb.config, and that the Joomla rules exclude the/sendypath. The usual way is a condition like{REQUEST_URI}doesn't match^/sendy.