Problems with SEF

[Wik]

Dear Reader,

I currently was working with 404SEF, but my provider complaints that this component is stressing the server way to much. Therefore I was looking for another SEF component.

This leads me to Advanced SEF en SF404SEF, but I can not get both systems working on my website using Mambo 4.6.2 / 4.6.5 (http://sbc.vanbragt.net/mambo.

I tried SF404SEF on a other Mambo of website and there it is working fine. I also installed an new clean mambo and connected this one to the database of the sbc.vanbragt.net website and still SEF is not functioning.

The homepage is build up correctly showing SEF urls. But when clicking one of those url I got a 404 page (with SF404SEF internal while with advanced SEF a default 404). I think there is something wrong in my database, but I do not have clue what is going wrong.

Any help would be appreciated.

Kind Regards,

Wilco

[Saka]

Please check the FAQ: http://www.sakic.net/support/faq/sef_advance/#1

[Wik]

Thanks Saka for the pointer. It was already early in the morning (around 2:30u) and I was probably to tired to read well.

Now I used the .htacces file enclosed in the Advanced Sef zip and now I have the following behaviour that it Advanced Sef is picking up the page not found part. When clicked on a link on the website with SEF url enabeld will forward the user back to the homepage (default advanced sef behaviour). So it looks advanced sef is working party, but why are the links not forward to correct item?

The website is running a subdomain http:/sbc.vanbragt.net/mambo.

My .htaccess for now:
#
#  mod_rewrite in use
#

RewriteEngine On

#  Uncomment following line if you get 403 Forbidden Error

#Options +FollowSymLinks

#  Uncomment following line if your webserver's URL
#  is not directly related to physival file paths.
#  Update YourMamboDirectory (just / for root)

RewriteBase /mambo

#
#  Rules
#

#RewriteCond %{REQUEST_URI} ^(/component/option,com) [NC,OR]
RewriteCond %{REQUEST_FILENAME} !\.(jpg|jpeg|gif|png|css|js|pl|txt)$
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php

########## Begin - Rewrite rules to block out some common exploits
## If you experience problems on your site block out the operations listed below
## This attempts to block the most common type of exploit `attempts` to Joomla!
#                             
# Block out any script trying to set a mosConfig value through the URL
RewriteCond %{QUERY_STRING} mosConfig_[a-zA-Z_]{1,21}(=|\%3D) [OR]
# Block out any script trying to base64_encode crap to send via URL
RewriteCond %{QUERY_STRING} base64_encode.*\(.*\) [OR]
# Block out any script that includes a <script> tag in URL
RewriteCond %{QUERY_STRING} (\<|%3C).*script.*(\>|%3E) [NC,OR]
# Block out any script trying to set a PHP GLOBALS variable via URL
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
# Block out any script trying to modify a _REQUEST variable via URL
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2})
# Block out any script trying to execute an extern script in the URL
#[OR] RewriteCond %{QUERY_STRING} http
#[OR] RewriteCond %{QUERY_STRING} ftp
# Send all blocked request to homepage with 403 Forbidden error!
RewriteRule ^(.*)$ index.php [F,L]
#
########## End - Rewrite rules to block out some common exploits

Add-on: I asked the provider about the com_rewrite and .htaccess override features and both are enabled on the server my domain is running on.

Hopefully you can point me to the right part to get this working.

Regards,

Wilco

[Saka]

Does the built-in SEF work when SEF Advance is disabled or uninstalled?

[Wik]

Thanks again for the quick response.

Exactlty the same behaviour. When clicking a default SEF link  (from the default page) the home page is displayed again.

Probably there is something wrong in the database I assume, but I don't know what.
Hopefully you can help me with this issue.

[Saka]

Then it's nothing wrong with SEF Advance, it's either mod_rewrite or .htaccess that don't work (regardless of what your host is telling you). Read the FAQ carefully on how to test if .htaccess override is working or mod_rewrite is checked. The built-in SEF must work before you install SEF Advance and thus I can't support setting up mod_rewrite and .htaccess override on your server.

[Wik]

Thanks again for your answer.

I noticed with doing some testing that some rights were not set up correctly on another component.

Now the default SEF is functioning correctly, using the default htacces.txt supplied with the mambo release. I tried to enabling Advanced SEF again, but that behavior is not changed unfortunate. It is still referring every page to the homepage (which is specified as the 404 page), of course using the .htaccess file as supplied with the Advanced SEF package.

Is there something wrong in the .htaccess file. I still using the file as specified in the previous post.

Hopefully you can help me with this issue. I also send an e-mail to the provider again to guarantee that mod_rewrite and .htaccess override on the servers are allowed.

PS I will be on holiday from tomorrow (sunday), so I will not respond to this forum before the 18th of august.

[Saka]

Send the superadmin password and FTP info to my email and I will take a look.