Borge on "Errors after a manual update - won't load"

I have an old site running 3.3 and I was trying to follow the instructions to install a manual update to 3.5 because I could not do an auto-update (admin screens were blank). After a very careful manual update (all went well and made sense) I now can not load my site.

The files it says are not there, are there. Please help! Thanks, Brad

Site: myPhotoPartyArt.com

Here is the error I'm now getting in my Safari Browser:

Waing: require(/home/lwart/public_html/wp-includes/load.php): failed to open stream: No such file or directory in /home/lwart/public_html/wp-settings.php on line 21

Fatal error: require(): Failed opening required '/home/lwart/public_html/wp-includes/load.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/lwart/public_html/wp-settings.php on line 21

It seems like maybe some of the files were missed or put in the wrong place.

Is there currently a load.php file in the /wp-includes/ directory of your site?

Thanks for your reply... but yes both files exist in the proper place.

/home/lwart/public_html/wp-settings.php
and
/home/lwart/public_html/wp-includes/load.php
both exist.

I replaced both of the old files with the new 3.5 files during the update. Is there a 'pointer' I would need to update inside one of the files?

If you are sure that the files are in the right place, check the permissions on them, because soemthing on the server is blocking access to them from your script.

The file permissions should all be 644, and the directory permissions should all be 755.

https://codex.wordpress.org/Changing_File_Permissions

Thanks again for the input but I can't find any permissions that are wrong either.

I've attached a HighTail link to some screen shots showing file locations and permissions.
Let me know if I'm missing something or if you need to see any other screen shots. Thanks again, Brad

https://spaces.hightail.com/space/ZaHV4

That does appear to be correct, which doesn't make much sense when compared to the error.

I recommend asking your hosting provider about this, as they'll have the access and logs necessary to determine what's causing an existing file to not be found.

change PHP from 5.3 to 5.5 or higher