I don’t know if this is the best place for this post but…

I’m having two issues related to removing the index.php from the urls in my app ...
I have followed the instructions from the user guide almost exactly. in fact my .htaccess is simply..

The first issue only shows on the root page of my site… ( http://semantalyzr.com/ )

If I have

 
I get these notices/errors only on my root page semantalyzr.com/ (actually this is now happening for me whether I have this empty or “index.php”) (EDIT: This was fixed by making my .htaccess empty)

A PHP Error was encountered

Severity: Notice

Message: Undefined offset: 0

Filename: libraries/Router.php

Line Number: 197
A PHP Error was encountered

Severity: Notice

Message: Undefined offset: 0

Filename: libraries/Router.php

Line Number: 203
A PHP Error was encountered

Severity: Notice

Message: Undefined offset: 0

Filename: libraries/Router.php

Line Number: 206

The second issues is with the .htaccess file itself I believe…

for a certain type of page on that site you will get a 404 error if you leave out the index.php, (ex. http://semantalyzr.com/page/analysis/http://www.time.com/time/nation/article/0,8599,1858933,00.html?xid=rss-topstories )

I believe this is completely due to the urlencoding in the url conflicting somehow with the .htaccess rewrite rules because if I add the index.php to the url it works fine…

(ex. http://semantalyzr.com/index.php/page/analysis/http://www.time.com/time/nation/article/0,8599,1858933,00.html?xid=rss-topstories )

Currently I have index.php enabled because everything seems to work fine this way… but I would like to remove it ASAP.

Thanks in advance!

Try

Its simple and fits my needs. Lets start there.

CI Lee. Really!? Try? Yes. Try this. Cut. Paste. Try. That’s what programming is now. Cut. Paste. Cross. Fin. Gers. Tr. Y.

Thanks for the replies!

I pretty much fixed the first problem, and I have somewhat of a work around for the second problem.

I won’t bother with all the details but basically the root of the problems was in the .htaccess file.

I removed the “negative” approach “!^(index\.php|public|robots\.txt)” and did something different and it works now.

Thanks for the feedback!

Perhaps someone should update the User Guide? I ran into the exact same problem using the provided .htaccess code from the guide.

It would be nice to see what were the changes that you made to the .htacces file I’m trying to change this in one of my app. I have search the forum but did to find a clear answer and I can see that a lot of people had issues with this.

alejandra -

Sorry! Here’s the .htaccess I used:

Thanks to CI Lee above for this!

Mark Drzycimski - 04 December 2008 05:54 PM

alejandra -

Sorry! Here’s the .htaccess I used:

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /index.php/$1 [L]

Thanks to CI Lee above for this!

I place this in a .htacces file and it did not work then I try

and my home page lost all the images and css file.

I’m trying this for the first what can I do, it seems like there is no clear way to do this.

I started having this same problem after switching from PHP4 to PHP5.

The problem with the above .htaccess “solution” is that it loosens the security of the site.  The original .htaccess (and the one that I use):

has the advantage of preventing access to other files that are not listed in the RewriteCond rule.  And I like that extra security.  The .htaccess solution:

works to remove the “Undefined offset” warnings, but it also allows unrestricted access to other files that you might not want to allow.  So be really sure you understand what you are doing in .htaccess before you just blindly implement a recommended “solution”.

I decided to focus on the original cause of the error messages, rather than messing with .htaccess changes.

The “Undefined offset: 0” errors in the Router.php file are not really “errors”.  They are “Notices”.  When you access an undefined offset, PHP will return a null value, but will flag this with a “notice error”.  If your PHP.INI file is set up to report all “errors”, then you will get these messages.  However, in your PHP.INI file, you can set:

error_reporting =  E_ALL & ~E_NOTICE

and this will suppress the display of “notice errors”.  However, in the PHP5 CGI version, there is a bug that will still display errors on your web page, even if the “display_errors=Off” (see http://bugs.php.net/bug.php?id=44729).  So even changing the error_reporting option wasn’t working for me on my server.

So some people will see these Notice messages, while others might not, depending upon their error_reporting settings for PHP.

I finally decided to fix the code in the Router.php file for good.  It really isn’t hard, and the Code Igniter developers should really add this fix to the next release:

Edit your Router.php file, and then find the “_validate_request” function (line 196 for me).  At the beginning of this function, add this:

I have seen some other solutions to this that do not work properly.  This is a very simple solution…if the array is empty, we just set the $segment[0] value to a null string.  This is what PHP is going to use anyway (after issuing the Notice error), so this just avoids the error/warning in the first place.  Simple and easy.

This fixed my site on PHP5, so hopefully this will help others.