Hi paul, I just upgraded to 4.1.3 and im using the auto rewrite in seo and it is not rewriting correctly. Below is what i get after the rewrite and then i get a 500 internal error for my site. How can this "äüößèÃ" be excluded when the rewrite script rewrite ?
It's hard to imagine a server that gives 500 errors when it encounters German. I'd expect the problem is with some other part. I've heard some people need to remove
Options +FollowSymlinks
And the next most likely lines to try removing are RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^(.+[^/])$ $1/ [R]
When you test removing those does the 500 error go away?
Hey Paul, It didnt work for me and i tried both recommendation. It is really not a big deal for me at least i have the option to do it manually. I wish i can help you more in that regards but i dont know why this is occurring for my site. I may upgrade my other wsnlink site and see if it occurs as well later in the week. Im also planing on setting up another fresh install as well so ill let you know if that makes a difference. The fresh install may be a while though.
Off topic question: If my main wsnlink directory is in the public_html directory do I just enter 'public_html' with no back space in the FTP Directory info section ?
Comments on auto rewrite not writing right
Forum Regular
Usergroup: Customer
Joined: Nov 01, 2004
Total Topics: 56
Total Comments: 121
Hi paul,
I just upgraded to 4.1.3 and im using the auto rewrite in seo and it is not rewriting correctly. Below is what i get after the rewrite and then i get a 500 internal error for my site. How can this "äüößèÃ" be excluded when the rewrite script rewrite ?
Options +FollowSymlinks
RewriteEngine on
RewriteBase /
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+[^/])$ $1/ [R]
RewriteRule ^admin/?$ admin/index.php
RewriteRule ^members/([0-9]+)\.html?$ memberlist.php?rewritten=1&page=$1
RewriteRule ^members/([-_/\+A-Za-z0-9äüößèà ]+)-([0-9]+)-trader\.html?$ trader.php?rewritten=1&id=$2
RewriteRule ^members/([-_/\+A-Za-z0-9äüößèà ]+)-([0-9]+)\.html?$ memberlist.php?rewritten=1&action=profile&id=$2
RewriteRule ^members/?$ memberlist.php?rewritten=1
RewriteRule ^help/?$ help.php?rewritten=1
RewriteRule ^help/([-_/\+A-Za-z0-9äüößèà ]+)/?$ help.php?rewritten=1&action=showcat&name=$1
RewriteRule ^help/([-_/\+A-Za-z0-9äüößèà ]+)/{HELPITEMTITLE}-([0-9]+)\.html?$ help.php?rewritten=1&action=showitem&id=$3
RewriteRule ^thread/([0-9]+)/$ comments.php?rewritten=1&id=$1&page=$2
RewriteRule ^thread/([0-9]+)/$ comments.php?rewritten=1&id=$1
RewriteRule ^test/details/([0-9]+)$ link.php?rewritten=1&action=detail&id=$1
RewriteRule ^lists/?$ albums.php?rewritten=1
RewriteRule ^lists/[-_/\+A-Za-z0-9äüößèà ]+-([0-9]+)/?$ albums.php?rewritten=1&catname=$1
RewriteRule ^lists/[-_/\+A-Za-z0-9äüößèà ]+-([0-9]+)/([0-9]+)\.html?$ albums.php?rewritten=1&catname=$1&page=$2
RewriteRule ^test/([0-9]+)/?$ link.php?rewritten=1&id=$1RewriteRule ^([0-9]+)/?$ index.php?rewritten=1&action=displaycat&catid=$1
RewriteRule ^([0-9]+)/([0-9]+)/?$ index.php?rewritten=1&action=displaycat&catid=$1&page=$2
RewriteRule ^([0-9]+)/sp([0-9]+).htm$ index.php?rewritten=1&action=displaycat&catname=$1&subpage=$2
RewriteRule ^([0-9]+)?$ index.php?rewritten=1&action=displaycat&catname=$1
RewriteRule ^([0-9]+)?$ index.php?rewritten=1&action=displaycat&catname=$1&page=$2
RewriteRule ^tags/([a-zA-Z0-9äüößèà ])/?$ search.php?rewritten=1&filled=1&action=filter&whichtype=links&tagscondition=like&tagssearch=|$1|
thanks,
fuee
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
It's hard to imagine a server that gives 500 errors when it encounters German. I'd expect the problem is with some other part. I've heard some people need to remove
Options +FollowSymlinks
And the next most likely lines to try removing are
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+[^/])$ $1/ [R]
When you test removing those does the 500 error go away?
Forum Regular
Usergroup: Customer
Joined: Nov 01, 2004
Total Topics: 56
Total Comments: 121
Hey Paul,
It didnt work for me and i tried both recommendation. It is really not a big deal for me at least i have the option to do it manually. I wish i can help you more in that regards but i dont know why this is occurring for my site. I may upgrade my other wsnlink site and see if it occurs as well later in the week. Im also planing on setting up another fresh install as well so ill let you know if that makes a difference. The fresh install may be a while though.
Off topic question:
If my main wsnlink directory is in the public_html directory do I just enter 'public_html' with no back space in the FTP Directory info section ?
Thanks,
Fuee
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
If it's the public_html subdirectory of where FTP lands you then yes, just type public_html.
I'll remove the accents since I don't think accented rewriting works well anyhow.