Unable to bring Oscommece site back online after restore @ a new hosting

[premme]

Hi,

 

Due to problems with my provider i whas forced to move my website to another provider.

Now i created a new DB with an other name, restored all tables

uploaded all files from the website to the new hosting and changed the configuration files.

 

Once the DB link worked, i got a blank page on my website, nothing comes up.

 

I've changed the config files in \admin\inludes and in \includes

 

What i'm i missing here

 

The site = www.PrecoShop.be

 

Thx,

 

Kris

 

[burt]

It is impossible for us to say.

 

You need to check your error_log to see what it says, which you can then tell us.

Then we can give you advice.

 

Error_log is in your hosting control panel.  If you cannot find it, ask your host.

[premme]

Hi,

 

This is the error i'm getting, but it thus not make sens to me.

 

FastCGI: server "/var/run/php-fpm/php54/php-cgi" stderr: PHP message: PHP Parse error: syntax error, unexpected '(', expecting identifier (T_STRING) or variable (T_VARIABLE) or '{' or '$' in /sites/precoshop.be/www/includes/classes/shopping_cart.php on line 35

[oscMarket]

Try to upload your backed up files again, in this specific case the : includes/classes/shopping_cart.php

 

See if you get a "new" error or keeping the same error.

 

Does your admin login work?

[premme]

got an other error now...

something to do with the path??

 

required 'includes/languages/.php' (include_path='.:/usr/local/php54/share/pear') in /sites/precoshop.be/www

[premme]

This is when i try to access the Admin panel

 

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at [email protected] to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

[MrPhil]

If reuploading shopping_cart.php fixed that error, it means you had a bad backup and/or restore. There may be other problems awaiting you.

 

The languages/.php error means that your new host is at a higher PHP version than your old host, and it has exposed a bug in application_top.php found in older versions of osC. Are you still back on osC 2.2-something? Anyway, either consider upgrading to 2.3.4 (a step at a time) if you are currently on 2.3 or higher, or installing 2.3.4 and migrating your data if you are on an older (2.2) version. Unless your shop is very highly customized, you will find it a losing battle to try to keep patching osC 2.2 to keep up with PHP version changes.

 

The Admin Internal Server Error can be caused by many things, but usually it means your .htaccess or php.ini file contains an illegal command for your server and PHP versions. It may be as simple as a php_flag or php_value command having to be moved over to php.ini, or it could be something complicated.

[premme]

Hi,

 

My backup is fine because i still have access to the enitial site and just restore it completely.

The website poped up once or twice but dissepeared on refresh again :-(

 

My newer provide thus indeed have a more recent PHP version running.

and i have 2.3.1 running on OSC.

 

I will try to upgrade to v2.3.4 then

 

For the Admin, could i try withouth the .htaccess for testing?

 

Thx,

 

Kris

[premme]

Some other question,

how can i check my current version when the site is not working?

[MrPhil]

The current version of osC is listed in application_top.php.

 

You can try renaming .htaccess to something else, to see if that's the 500 error cause. Don't plan on running long-term that way, though. Did you implement "password protected directory" on Admin on the old system? If so, it's quite possible that you will need to remove it and redo it for the new system, as the commands needed, etc., may be different. At a minimum, check that the files involved have been updated to correct names and paths.

 

If you find it's the .htaccess that's causing the problem, list it here (after obscuring anything sensitive, such as account names). It's probably a simple fix, such as your new host does not allow the Options command. Also check the php.ini file, if any.

[premme]

Seems that i have v2.3.1

i'm busy upgrading to v2.3.2 but i'm unable to find the new files.

where can i find those?

[premme]

Done, i've used them from the latest release...

 

Do i need to go true all the updates one by one or is there a way to upgrade from 2.3.2 to 2.3.4?

 

Is it easy to move all my data like users/order and items to a new version if i start from scratch?

[Hotclutch]

There's a new version announced to be released soon FYI. Search the forum for "bootstrap".

[premme]

looks good but i still whant to get my current site back online asap...

could i just fix the bug by upgrading some files now?

[Hotclutch]

I can't say what's wrong with your existing store, but it's not that difficult to make the change to bootstrap version, provided your existing version is not too heavily modified.

[MrPhil]

2.3.2 -> 2.3.3 -> 2.3.3.1 -> 2.3.3.2 -> 2.3.3.3 -> 2.3.3.4 -> 2.3.4 is one step at a time, but it will preserve your modifications and data. If you have no add-ons or other modifications, you could install 2.3.4 (and optionally, the BootStrap version on top of that) and migrate your database and other data.

[premme]

I'm afraid that is a problem... i have done many changes in the last 9 years and Always perfomed upgrades

[MrPhil]

9 years? Then you must have started at osC 2.2-something. Did you upgrade from 2.2RC2a to 2.3, or install a fresh copy? If you upgraded, you have a hybrid store that is neither fish nor fowl (we call it a Frankenstore) and will be increasingly difficult to upgrade as time goes by. At some point, you will want to make a clean break with the past and install 2.3.4 or something later. 

 

When you say you "have done many changes", are you talking about add-ons and custom modifications, or just upgrades to the next osC release? If only upgrades, you have an otherwise "stock" store and should strongly consider a jump to 2.3.4 (migrating your data). If the store has been modified a great deal, that may prove too painful, though I would still recommend installing a new 2.3.4 test store and taking the time to explore it (with your migrated data) and decide what add-ons and custom work are needed to get it to where you want it. Remember that with 2.3, a lot of "look and feel" customization migrated to CSS.

[premme]

 

 

Indeed, i wil propably start from scratch.

What table data do i need to move to have the best possible data migration?

[MrPhil]

You would make a copy of the old database, then apply SQL updates osC level-by-level, until you match the schema for 2.3.4. Don't try to pick and choose tables (you'll need them all, anyway).

[premme]

Hi,

 

In the meantime i did a complete new installation, resored my DB and did all the nessecary SQL upgrades.

But the login page thus not show up? (login.php)

 

Any sugestions?

 

Thx,

 

Kris

[MrPhil]

What do you mean by "thus not show up"? Did you request to log in and you get a blank white screen? Any errors logged by the site? Or did something else happen?