Menu Content

Support

> Forums, FAQs & Paid Support
Welcome, Guest
Username Password: Remember me

Profile for kirk837

  • OFFLINE
  • Time Zone: GMT +0:00
  • Local Time: 13:16
  • Posts: 3
  • Profile Views: 1811
  • Location: Unknown
  • Gender: Unknown
  • Birthdate: Unknown

Signature

Posts

Posts

emo
The correction discussed in this topic (Static content homepage, posted by Nate West back in April) and placed in the official source code, does fix the 403's, but it leaves the com_frontpage as the \"homepage\" that responds to \"thisurl/\" and \"thisurl/index.php\". The problem is that con_frontpage is hardcoded as the homepage; this can be fixed by the following code change, just above the change just discussed:

 
$query = \"SELECT `id`,`link` FROM #__menu WHERE `menutype` = 'mainmenu' AND published` > 0 AND `ordering` = 1;
//`link` LIKE '%com_frontpage%' LIMIT 1\";
 



I believe this takes care of the difficulty and makes JoomSEF consistent with the Joomla! homepage rule: The first item on the main menu is the home page.
Static content homep ...
Category: JoomSEF 3
emo
The correction just discussed does fix the 403's, but it leaves the com_frontpage as the \"homepage\" that responds to \"thisurl/\" and \"thisurl/index.php\". You have con_frontpage hardcoded as the homepage; this can be fixed by the following code change, just above the change just discussed:

 
$query = \"SELECT `id`,`link` FROM #__menu WHERE `menutype` = 'mainmenu' AND `published` > 0 AND `ordering` = 1;
//`link` LIKE '%com_frontpage%' LIMIT 1\";
 


I believe this takes care of the difficulty and makes JoomSEF consistent with the Joomla! homepage rule -- the first item on the main menu is the home page.

Kim Kirkpatrick
Re:Static content ho ...
Category: JoomSEF 3
emo
This question appears in various forms a number of times in this forum (search \"trailing slash\"). It hasn't been answered satisfactorily, nor even acknowledged by ARTIO.

I believe it arises only when JoomSEF's \"file suffix\" setting has been made blank. In this case, it is fixed by setting file suffix to / (slash). Then all urls will have a slash at the end and none will be filenames.

Then we have the problem of missing trailing slashes -- if someone types in a url without a trailing slash, we want the page to come up, not a 404. Let's modify .htaccess:

Options +FollowSymLinks
DirectoryIndex index.php
RewriteEngine On
RewriteBase /Joomla

RewriteCond %{REQUEST_URI} !(\.|/$)
RewriteRule (.+) /Joomla/$1/ [R=301,L]

RewriteCond %{REQUEST_URI} ^(/component/option,com) [NC,OR]
RewriteCond %{REQUEST_URI} (/|\.htm|\.php|\.html|/[^.]*)$ [NC]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule (.*) index.php


This is the .htaccess that JoomSEF generated at installation, with RewriteBase modified for the subfolder my site is in (\"/Joomla\"). I've added the two lines isolated in the middle; they force a trailing slash on any url that doesn't contain a dot (ie, a filename) and doesn't end in a slash. After that the JoomSEF rewrites are handled. (I hope a rewriterule expert will polish this up. It works for me.)

So the question remains: What is \&quot;tolerant to trailing slashes\&quot; supposed to do?<br><br>Post edited by: kirk837, at: 2007/09/10 03:35
Be tolerant to trail ...
Category: JoomSEF 3
More
User Login Empty