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.

500 error after moving site to different provider

May 21, 2009 1:44pm

Subscribe [3]
  • #1 / May 21, 2009 1:44pm

    roman-vc

    46 posts

    Hi,
    i just moved my webspace to a different provider. Moved everything to the new webspace, changed the paths and stuff. The only pages that are accessible at the moment are the frontpage and the control panel - the cp is missing the style sheet. All other pages give me a 500 error unless i add a “?” to the url.
    This works: http://www.berlinista.com/?en/contact
    This results in a 500 error: http://www.berlinista.com/en/contact
    I tried nearly everything including the force query trick, which didn’t change a thing.
    Any ideas? Please help.
    Roman

  • #2 / May 21, 2009 1:53pm

    Sue Crocker

    26054 posts

    But this one is OK..

    http://www.berlinista.com/en/blog

    and the other link is working just fine now… ?

  • #3 / May 21, 2009 2:46pm

    roman-vc

    46 posts

    Hi,
    strange… It ain’t workin’ for us. Maybe because we’re on Macs? See the attached file. The red text says: “The script: http://www.berlinista.com/en/blog couldn’t be executed without faults.
    Roman

    UPDATE: Actually not that strange. The domain got switched to the new location around 10 hours ago. Maybe your servers aren’t yet updated. whois.net for example still shows the old provider as host.

  • #4 / May 21, 2009 3:18pm

    Ingmar

    29245 posts

    I suggest you do not remove index.php from your URL just yet. If you try with a question mark, this works fine:

    <a href="http://www.berlinista.com/index.php?/en/contact">http://www.berlinista.com/index.php?/en/contact</a>

    Consequently, forcing query strings should be all that’s necessary. Try to disable all .htaccess based rewriting during debugging, please. Also, what version and build are you on?

  • #5 / May 21, 2009 6:21pm

    roman-vc

    46 posts

    Hi, index.php was removed at the very beginning of the site and after more than 7.000 articles we won’t go back. Forcing query strings doesn’t work - already tried that one. We are running version 1.65.
    Thanks’ a lot.
    Roman

  • #6 / May 21, 2009 6:34pm

    Ingmar

    29245 posts

    Hi, index.php was removed at the very beginning of the site and after more than 7.000 articles we won’t go back.

    It will work either way, and I am only trying to rule out one possible source of errors which, unfortunately, happens a lot with url rewriting.

    Forcing query strings doesn’t work - already tried that one.

    Since adding a question mark to your URL (and really, that’s all this option does) makes it work, I don’t think why it shouldn’t. Unless, of course, your rewrite rules are somehow changing it. As you can see, this clearly works:

    http://www.berlinista.com/?/en/culture

  • #7 / May 22, 2009 11:55am

    roman-vc

    46 posts

    Ok,
    if i remove the rewrite part from the htaccess file i get a 404 error instead of the 500 one. Force URL query doesn’t change a thing. You see no change at all.
    Whatever setting of the above i choose, the cp still has no styling - as you can see in the attached image.
    Roman

  • #8 / May 22, 2009 12:02pm

    Ingmar

    29245 posts

    if i remove the rewrite part from the htaccess file i get a 404 error instead of the 500 one. Force URL query doesn’t change a thing.

    This URL still works fine: http://www.berlinista.com/?/en/culture (with the question mark), so I really don’t know why forcing query strings shouldn’t work for you. How are you creating your links, internally? Can you show us some code?

    Whatever setting of the above i choose, the cp still has no styling - as you can see in the attached image.

    There’s a KB article on unstyled CPs, have you gone through that?

  • #9 / May 22, 2009 12:24pm

    roman-vc

    46 posts

    Hi, one problem solved - the KB article helped for the CP part.
    I don’t know how ee creates it’s links. What part of the code you wanna see? Tons of files…
    Roman

  • #10 / May 22, 2009 12:27pm

    Ingmar

    29245 posts

    Well, your menu, for example, but really any piece where you link from one part of the site to another. Do your hardcode your links, or do you let EE create them for you, using one of the existing path variables? Because only in case of the latter will “force query strings” actually do anything for you.

  • #11 / May 22, 2009 12:33pm

    roman-vc

    46 posts

    Ok, the following is a part of the code of the nav bar.

    {if segment_1 == "de"}
            <!-- #nav: Hauptnavigation -->
            <div id="nav"> <a href="/de%22id=%22navigation" class="first">Home</a></li>
                        <li {if '{embed:loc}' == 'musik'}id="current"{/if}><a href="/de/musik">Musik</a></li>
                        <li {if '{embed:loc}' == 'kunst'}id="current"{/if}><a href="/de/kunst">Kunst</a></li>
                        <li {if '{embed:loc}' == 'mode'}id="current"{/if}><a href="/de/mode">Mode</a></li>
                        <li {if '{embed:loc}' == 'digitalesleben'}id="current"{/if}><a href="/de/digitalesleben">Kultur</a></li>
  • #12 / May 22, 2009 12:52pm

    Ingmar

    29245 posts

    OK, let’s take a look at a small sample here:

    <li {if '{embed:loc}' == 'musik'}id="current"{/if}><a href="/de/musik">Musik</a></li>
    <li {if '{embed:loc}' == 'kunst'}id="current"{/if}><a href="/de/kunst">Kunst</a></li>

    You are creating your links manually. Which means that “forcing query strings” won’t do anything for you. Try putting that question mark in there manually, like so:

    <li {if '{embed:loc}' == 'musik'}id="current"{/if}><a href="/?/de/musik">Musik</a></li>
    <li {if '{embed:loc}' == 'kunst'}id="current"{/if}><a href="/?/de/kunst">Kunst</a></li>

    You really should be using some of EE’s dynamic path variables, though, makes things much easier.

  • #13 / May 22, 2009 1:15pm

    roman-vc

    46 posts

    Ok,
    I removed the following piece of code from the htaccess file:

    "##Begin Strip index.php
    RewriteEngine On
    RewriteCond $1 !^(css|themes|images|rv69be|slideshow|ssp_director|storage|mint|yaml|players|js|index\.php|robots\.txt|kortornado1joe3me\.php|kolibri15tornado\.php|hahu-huha\.php|sitemapold\.php|modlogan|canvas\.html|rpc_relay\.html).*
    RewriteRule ^([^/]+.*)$ index.php/$1 [NC,L]"

    Though it doesn’t bring the “index.php” back to the url if i remove the part from the htaccess that takes it away, adding a question mark every now and then doesn’t look to me like a proper solution to our problems.
    Do you have any other ideas about what might be wrong?
    Roman
    UPDATE: Don’t you think that the problems are somehow connected to the new server? Maybe there is a thing that they have to activate in order to get the site working properly again?

  • #14 / May 22, 2009 2:00pm

    Lisa Wess

    20502 posts

    Hi, roman-vc; to summarize, the site does work if you include index.php? in the URLs, correct?

    That means that you must use the question mark; yes, this is server related.  See this kb entry - it includes an explanation.

    As for your links, you’re hard-coding the links rather than letting EE build them.  For instance you have this:

    <li {if '{embed:loc}' == 'musik'}id="current"{/if}><a href="/de/musik">Musik</a></li>

    Instead try:

    li {if '{embed:loc}' == 'musik'}id="current"{/if}><a href="http://{path=de/musik}">Musik</a></li>

    which EE will then create the full link, and respect the “force query strings” option for you.  You can read in the docs about the Path Global Variable.  This will also include index.php as in the Name of your site’s index page in Admin -> System Preferences -> General Config.

    On a side-note and unrelated, you do not want to quote and brace your conditional, ie:

    '{embed:loc}'

    should be”

    embed:loc

    when inside a conditional.  You can read more about that in Troubleshooting Conditionals, especially the security part of the explanation therein.

  • #15 / May 22, 2009 3:16pm

    roman-vc

    46 posts

    Hi Lisa,
    just rang up the provider and they told me that the reason is the number of mod rewrites that we have. They limit it to 20 and we have “several thousand” rewrite requests which result in a 500 error.
    Our site includes about 110 templates which i didn’t build. For that reason i don’t have no clue where to change everything the way you describe. Guess i have to look for another provider in a hurry.
    Roman

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

ExpressionEngine News!

#eecms, #events, #releases