Thread

Greetings,

I’m transferring an EE v1.6.4 site from one hosting company to another. I have versions 1.6.3 and 1.6.5 of the EE install files in my archive. What can I say, I’m a packrat. 😊 I used the existing files from the old hosting account for the EE system directory. I haven’t yet used any of the EE files from my version archive.

The control panel, and the login window, is not showing the proper theme, or any theme at all. I went in to Admin > General Configuration and made sure everything was updated to the new site. The “URL to your themes directory” seems correct for the new server. The Theme Folder Path may not be a full path on the new server. Is there another setting somewhere that I’m missing? Any ideas on what’s still wrong/missing?

I’m thinking of upgrading the site to version 1.6.5 in order to solve this. Will this update the theme directory setting properly?

Once the transfer is complete and everything is stable the plan was to upgrade to 1.7 and eventually version 2.x

Thanks,
Bob.

I’ve solved the themes problem, the server path was wrong. But there may be other issues that I’ll post back here if need be.

Thanks,
Bob.

Thanks for the update Bob. With such an old version of EE like this I think you are correct in updating to EE1.7.1 first and then upgrading to EE2.1x. No need to upgrade to versions below 1.7.1, the updater will take care of this.

I’ll leave this open for now to give you a chance to try the upgrade

John,

I was able to do the upgrade to version 1.7.0 and now Expression Engine itself seems to be working fine. The upgrade was a breeze. 😊

I’ve found a few anomalies from the move though. One was that a custom field setup as a relation seems to have lost that setting. I had to recreate the field as a relationship to the correct section/channel. The end users will have to go back in and recreate the relationships.

One error shows up on one page though:
Parse error: syntax error, unexpected T_ELSE in /www/eh15897/public_html/system_ee_ehc/core/core.functions.php(663) : eval()‘d code on line 27

Whenever a link on this page is clicked the site will throw this error, only visible when logged in as admin. Is this related to EE’s if, then, else construct?

Thanks,
Bob.

Hi, Bob.

What’s on the page that is throwing the error code wise?

Here is the block of EE code that create the html links. There is also an .htaccess file that translates URL’s.

(Rant: Lately I’ve been seeing a lot of sites using htaccess for URL management instead of using the EE template hierarchy. And those are EE sites. What a pain to use htaccess for this. Sorry, rant over.)

{if group_id=='1'|| group_id=='6'}
            {exp:weblog:entries weblog="{my_weblog}"  orderby="last_name"  status="open|For Review" dynamic="on" sort="asc"  disable="member_data|trackbacks"}
            
            {if last_name != ""}
            <li><a href="http://{eepath}change_agents/{url_title}">{first_name} {last_name}</a> <span class="pipe_gr">|</span> {chg_agent_title}</li>
            {/if}
            
            {/exp:weblog:entries} 
            {if:else}
    {exp:weblog:entries weblog="{my_weblog}"  orderby="last_name"  dynamic="on" sort="asc"  disable="member_data|trackbacks"}
            
            {if last_name != ""}
            <li><a href="http://{eepath}change_agents/{url_title}">{first_name} {last_name}</a> <span class="pipe_gr">|</span> {chg_agent_title}</li>
            {/if}
            
            {/exp:weblog:entries} 
           {/if}

Here is EE’s own code, core.functions, where the thrown error seems to come from:

if ( ! defined('EXT'))
{
    exit('Invalid file request');
}

If you take the .htaccess out of the equation, do you still get the error?

Sue,

Thanks for the idea on the htaccess file but, alas, it was not the problem. I tried turning it off for awhile and using full urls but the problem was still there.

But I did find the problem. I had to painstakingly reorganize the main index template with tabs and such to look at the structure of the code and I found that there were two if-then-else tags that weren’t closed fully. Apparently the older version of EE was less strict about the code structure and tags and the problem never showed up before.

Thanks for everyone’s help and suggestions.

- bob.

Sounds like you’re ready to go.. Don’t hesitate to post again as needed.