Problem porting CI 1.7.2 to 2.0.0

[eluser]Zeff[/eluser]
Hi all,

I followed the User Guide ('Upgrading from 1.7.2 to 2.0.0') to upgrade an existing site. Now I have a weird problem: although all menu links are correctly generated, they all give a 404 error. Only the default controller can be displayed, calling http://www.mysite.domain.com/
Just calling http://www.mysite.domain.com/index.php or http://www.mysite.domain.com/index.php/a.../mymethod/ gives me a 404 error...
I don't use mod_rewrite in an .htaccess and important config params are set to:

Code:

$config['index_page'] = 'index.php';
$config['uri_protocol']    = 'REQUEST_URI';

Help! What did I do wrong?

Many thanks in advance!

Zeff

[eluser]crnalajna[/eluser]
Try to get latest CI from Bitbucket.
http://bitbucket.org/ellislab/codeigniter-reactor

[eluser]Dahak-II[/eluser]
This is quite similar to the problem that I am having (forum article).

CI2.0 runs fine in my Windows/Apache dev environment, but fails in my Linux/Apache production environment.

I don't generate 404s, though, I simply get the index function of my default controller, no matter what URI I pass to it.

I'll have to pull down the newer Reactor files to see if they help.

[eluser]Zeff[/eluser]
Hey guys,

Thanks for the response. It is indeed a LAMP configuration that gives problems.
Crnalajna, I will check out your suggestion and post my findings.

Best regards,

Zeff

[eluser]Dahak-II[/eluser]
I just grabbed the current image of the Reactor files.

I can't say that I'm particularly wild about how these in-process snapshots are being made available, but that's just my opinion.

As far as solving my own routing problem, no joy.

I ran through each of the five uri_protocol options, as well.

Looks like CI2.0 is a wash-out in my LAMP environment.

[eluser]Zeff[/eluser]
I replaced the system folder with the last version from Reactor, without success...

[eluser]Dahak-II[/eluser]
Last night I started tracing my way through the Router and URI libraries on my remote server.

In my case, I've established that the LAMP setup is actually reading the URI when the uri_protocol setting is QUERY_STRING.

$this->uri->uri_string and $this->uri->segments seems to hold what they should.

I called it a night after that.

I'll continue tracing the data until I find where it seems to be getting lost.

I'll keep you up-to-date on what I find.

[eluser]Zeff[/eluser]
Thanks, I'll keep you too informed if I find a workaround or solution.

[eluser]Fierymind[/eluser]
upgrade to CI 2 was VERY rough road, I got similar issue and I fixed it using

$config['uri_protocol'] = "ORIG_PATH_INFO";

on the main config file

[eluser]Zeff[/eluser]
Thanks Fierymind, but I alraedy tried them all without success...