Thread

When running EE 1.x, we were able run our site without forcing query strings;  has something changed in 2.1? 

For example:

http://www.site.com/index.php/template-group/template  worked fine in 1.6.9, but no longer works in 2.1…. same server and everything. 

Thanks for any guidance. 

Confused,

- Phil

Moved to CodeShare Corner by Moderator

Phil,

what version and build of EE are you using?
What type of hosting are you using?

Have you got a specific example link to your site?

Leave the preference to force query strings off for the moment and open up your config.php file
system/expressionengine/config/config.php

Find the line

$config['uri_protocol']    = 'AUTO';

and change it to

$config['uri_protocol']    = 'PATH_INFO';

Does that make a difference?

Are you using any htaccess file?

JH,

Thanks for the help. 

Here’s the info:
Build: 20100810
.htaccess in the root directory:  Nothing there aside from some old 301 redirects.  Should there be something else? (If I need to write some mod_rewrite directives, I will, but I wanted to understand what was going on first)  I even took the .htaccess file away for a moment to see if that made any difference.

Host: They are using: GoDaddy as their host, running PHP Version 5.2.14.

Here’s a specific example:

http://www.uproducers.com/

Any of the tabs across the top link to a template group.  We didn’t need to use Force Query strings in 1.6.4.  I currently have them enabled since the site is live, but I tried turning them off and changing the following line in the system/expressionengine/config/config.php file:

$config[‘uri_protocol’] = ‘AUTO’;

and change it to

$config[‘uri_protocol’] = ‘PATH_INFO’;

Didn’t seem to make any difference. 

One final piece of info… When I enable template debugging (when force query strings is off), EE is searching for the template “index.php”—which obviously doesn’t exist, so it defaults to site/index.  Thanks again for any guidance or insight.

GoDaddy is one of those hosts where Force Query Strings still may be an issue. Many people use an .htaccess to remove index.php? out of their urls. We don’t support it directly, but I can move this over to the CodeShare Corner for additional community support if you’d like.

Thanks Sue… that’s definitely my next option.  What changed between 1.6.x and 2.1 that made this an issue?  Do you happen to know?

I have no idea what changed. I just know how to fix it. 😊 Moving over to CodeShare Corner.