Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Drop reliance on proprietary webserver code for clean URLs
Hey TXP chums,
Please kick me off here if this is not the right place to post this…
If I could help with this I would, but I’m too much of a thickie1.
I would like to vote(?) for a future version of TXP to no longer require webserver rules to in order to provide it’s clean URL scheme.
Apache and it’s .htaccess rule set are fine and work for me, but I believe they are partially or poorly supported by some other webservers.
I am not expecting that this can be done nor am I assuming or presuming anything — I cheerfully accept that TXP priorities likely do not stretch to such work, but I thought it would be good to make the request even if it never has a chance of being followed.
Thanks to all TXP devs for this quite superb superCMS, and whether this suggestion ever gets looked at or not, I will remain a cheery user of this excellent software.
Cheers, -Alan
1 Not clever
At LAST I’ve cheerfully donated to the core devs at #TXP. I only wish I were able to give more. Thanks to the devs and ALL fellow TXPers. -A
Offline
Re: Drop reliance on proprietary webserver code for clean URLs
alanfluff wrote:
Apache and it’s .htaccess rule set are fine and work for me, but I believe they are partially or poorly supported by some other webservers.
Heh, Apache and modrewrite isn’t required, PHP is. Server and requests redirecting method can be whatever as long as it works with PHP.
I am not expecting that this can be done nor am I assuming or presuming anything
All requests must be passed to index.php. TXP, as a PHP snippet, can not do it. Webserver must in a way or another redirect the requests to index.php. The .htaccess bundled with installation does that.
If server can’t rewrite/redirect/handle the requests, in a way or another, then nothing can be done. Then the user just must use messy urls which allow the request to go directly to index.php.
Offline
Re: Drop reliance on proprietary webserver code for clean URLs
Tks Jukka.
This came up for me a second time as a second client wanted to have a site with a hoster running Zeus and they wanted to charge $450 for trying to get their server to do what the default .htaccess does, and it’s open ended, they could take longer/charge more (nice eh? ;)
So not knowing, I just thought I’d ask the Q.
Thanks lots for explaining to me — time to look at moving them to another host I suppose. Cheers, -Alan
At LAST I’ve cheerfully donated to the core devs at #TXP. I only wish I were able to give more. Thanks to the devs and ALL fellow TXPers. -A
Offline
Re: Drop reliance on proprietary webserver code for clean URLs
Offline
Re: Drop reliance on proprietary webserver code for clean URLs
Thanks, yes, I’ve commented on that blog and am waiting a reply — he says in an addendum that there’s a problem if the TXP is in a sub dir (mine won’t be), so I imply from that that it will solve the problem — trouble is I know the client will have a short fuse (they’re one of those ;) and I am just concerned, in my ignorance, that some plugin I might use etc might trip up the rules and it might 99% work but fail in some weird way.
Hopefully he’ll reply and say the rules are AOK for TXP installs in the root and hopefully if the core TXP works, then no edge-cases that might break the Zeus rules will exist and all will be hunky dory.
THANKs for finding this for me tho! You’re very nice :D
Cheers, -Alan
At LAST I’ve cheerfully donated to the core devs at #TXP. I only wish I were able to give more. Thanks to the devs and ALL fellow TXPers. -A
Offline
Offline