ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Help with "URL Segment Support"

July 12, 2007 7:26pm

Subscribe [2]
  • #1 / Jul 12, 2007 7:26pm

    muddygrey

    9 posts

    I hope this is the right place to post this.  I’m about to install ExpressionEngine and downloaded and ran the Server Compatibility Wizard.  Everything is coming up supported except for “URL Segment Support”.  On my development server I’ve installed Apache 2.2.4 on a Windows XP box. 

    Could someone please tell me how I can enable this?  The ExpressionEngine documentation mentioned that if hosted on an Apache server then “it needs to be configured with AllowOverride=on” and that this can be set with an .htaccess file.  I’ve tried Google to find instructions on how to do this with no luck.

    Any help you can give me will be appreciated.

    Thanks.

  • #2 / Jul 12, 2007 8:05pm

    Sue Crocker

    26054 posts

    Hi, skoppy. Welcome to ExpressionEngine!

    Link

    Query for AllowOverride=on and you’ll find the post I listed above.

    Does that help at all?

  • #3 / Jul 12, 2007 11:29pm

    muddygrey

    9 posts

    Hey Sue thanks for the reply.  I checked out that post you linked to and tried to follow what it laid out.  Perhaps I don’t know how to properly write a .htaccess file.  The only line I put in the file was “AcceptPathInfo On”, without the quotes of course.  After that I re-ran the server compatibility wizard and URL Segment Support still came back unsupported. 

    In addition Ability to send Pings and Trackbacks and Built in Spellchecker suddenly came back unsupported.

    Was I supposed to add more to the .htaccess file?

    Thanks.

  • #4 / Jul 12, 2007 11:31pm

    muddygrey

    9 posts

    Also, might you know of any good beginner’s tutorials for writing .htaccess files?

    Thanks again.

  • #5 / Jul 12, 2007 11:43pm

    Sue Crocker

    26054 posts

    skoppy, at this point you’d need to contact your host. You may not have a choice, and would need to use index.php? instead of index.php.

    Output and debugging preferences

    See the text on force query string.

  • #6 / Jul 13, 2007 12:08am

    muddygrey

    9 posts

    Once again thank you for the quick reply.  I would contact my host but unfortunately at this point that would be me.  Thankfully I’m just setting up a development server now so I still have time to figure this out.  From the link you posted it seems like the fact that my development box is just a Windows XP workstation might be to blame.  So this problem may very well work itself out by the time we go live on a Unix box.

    I’m going to try and search the web a bit to see if I can find a way to resolve it and please if you think of anything else that might help be sure to post it.

    Once again thank you for your assistance with this.  I’m rather new to ExpressionEngine and setting up my own web server so your help has been appreciated.

  • #7 / Jul 13, 2007 12:35am

    muddygrey

    9 posts

    Sorry one more quick related question and then I’ll get out of your hair.  I installed EE Core on another machine I have at home to do some testing on.  It too is a Windows XP machine and once again the server compatibility wizard said that “URL Segment Support” was not supported.  But when I view the site the URLs seem remarkably free of query strings.

    Example:
    http://localhost/eecore/index.php/C5/

    Could it be that for some reason the wizard.php script is encounter some sort of false error and “URL Segment Support” is supported?

  • #8 / Jul 15, 2007 10:13am

    Robin Sowell

    13255 posts

    Hm- only difference I see- a live site will use the $_SERVER[‘QUERY_STRING’] if it’s available by default.  While the wizard just checks the path_info.  So if you had something going on that would allow it to know the query_string without using one?  Er- but I’m not up on windows servers. 

    You could try putting this in a test template- turn php parsing ‘on’ and view the rendered output:

    <?php
    $path_info = (isset($_SERVER['PATH_INFO'])) ? $_SERVER['PATH_INFO'] : @getenv('PATH_INFO');
    $query_str = (isset($_SERVER['QUERY_STRING'])) ? $_SERVER['QUERY_STRING'] : @getenv('QUERY_STRING');
    
    echo 'Path info: '.$path_info;
    echo '
    Qstring info: '.$query_str;
    ?>

    The path_info bit it pretty much what the wizard is using to test if path_info is supported.  Putting it in a template and checking it with/without the ? in there will give us a better hint as to what’s where.  Make sense?

  • #9 / Jul 16, 2007 1:18pm

    muddygrey

    9 posts

    Robin,

    I put the code you supplied in the master site default page.  When I clicked on the “Blogging” category link in the First Entry that is posted when you install EE this is what was output:

    Path info: /category/Blogging/
    Qstring info:

    Which would indicate that path_info is supported right?

    It’s really a windows server.  It is a Dell workstation with Windows XP installed but I am using Apache as the web server.  I’m not sure if that would influence this somehow.  This is only the development server so this isn’t as big a concern on this server.  I was just hoping to figure this out for when we do the install for the live server with will be Unix based.

    And thank you for your post.  Being new to all of this it is something that I would never have thought to do my self.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases