Web Hosting Co Can't Locate My Web Site

Hello I need some help, please. Apparently my hosting company cannot locate my web file. I logged into my Concrete5 page and found a page full of errors. With this one being on the bottom. Strict Standards: Non-static method Loader::db() should not be called statically, assuming $this from incompatible context in /hermes/bosnaweb23a/b1540/ipg.foxvalleyprtcom/site/updates/concrete5.4.2.2/concrete/startup/shutdown.php on line 3

My website was built years ago and to the best of my knowledge hasn't been updated in Concrete5 for at least 4 years? The guy who built my website is no longer available.

Julie Felten

View Replies:
hutman replied on at Permalink Reply
Sent PM.
pixelmargin replied on at Permalink Reply
Sorry this was replied to wrong thread as i was on phone.
pixelmargin replied on at Permalink Reply
Hey Friend

Its caused by Server Upgrade. Solutions are

1. Either modify all the old php functions
2. Get the site copy locally and upgrade it into latest c5 version.

I can help you out quickly. Please add me on skype id : tinkutr and lets have a quick call.

You may also reach me over phone : +91 8281828551
JacFelten replied on at Permalink Reply
Now I can't even log into Concrete5, my dashboard. Is this problem related or is Concrete5 down now too?
JacFelten replied on at Permalink Reply
This is the error message I receive when trying to access my login page for Concrete5. Did the latest upgrade change the login link as well? Seems like perhaps I have two separate issues?

The requested URL /site/index.php/login was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

My login link to Concrete5:http://foxvalleyparsons.com/site/index.php/login...

I was able to pull this up earlier, however it was full of errors (listed above). But now I can't even pull it up. Is Concrete5 linked to my web host provider?
webigear replied on at Permalink Reply
May be you are using wrong link. I can see it here but with the errors.http://foxvalleyparsons.com/index.php/login...
C5devScott replied on at Permalink Reply
Hello Julie,

I will be more than happy to assist you for this small job.

Please check my message in your Private message box and kindly add me on Skype: cis.scott so we can discuss further.

Also you can email me your requirements at [email protected]

Thanks and regards,
Scott W.
TMDesigns replied on at Permalink Reply
I have had this problem before with a few clients, if you want me to take a looking please get in contact
mhawke replied on at Permalink Reply
As others have mentioned, your host has upgraded (for good reasons) the default version of PHP that runs on your server and now it's causing problems for older sites like yours. For a quick, temporary solution, you could either log into your host's Control Panel and find where you can change the version of PHP that your site is running or contact your host (iPage?) and ask them to change the version. Moving it back to a version prior to 5.4 should give you access to your site BUT this is temporary. Your site needs to be upgraded (possibly stepping through several versions) until it gets up to the most recent version of
manup replied on at Permalink Reply
I am suggesting to place the following code at the start of index.php

and config/site.php

update/add the following lines
define('BASE_URL', 'http://foxvalleyparsons.com');
jasteele12 replied on at Permalink Reply
Unfortunately error_reporting() is set later in dispatcher.php - so modifying index.php won't help. (very old) was before PHP version 5.4 when E_STRICT was included in E_ALL and therefore wasn't masked at that time.

Since Google is indexing /site/ I wouldn't make those modifications in config/site.php until 301 permanent redirects were added to .htaccess for each of the URLs in /sitemap.xml

The only real quick fix is to try disabling E_STRICT in php.ini or downgrading the PHP version from the hosting provider. Temporarily, since it will need to be higher later in the update process (not to mention security and speed improvements).

Also, as @mhawke mentioned above, there is a very definite need to update concrete5 versions in a specific order (with backups along the way). There are quite a few things that can go wrong getting from all the way to