P.S.
Here is System Status from Thesis–
Thesis & Current Skin
===========================
Thesis Version: 2.7.1
Skin Name: Classic Responsive
Skin Version: 1.6.1
Skin CSS: YES → 24.1kB on 12/17/2018 at 02:30:39
Skin Custom CSS: YES → 3.44kB
Skin Custom PHP: YES → 4.4kB on 12/17/2018 at 02:30:39
Thesis Filesystem
===========================
wp-content/thesis: YES
wp-content/thesis/skins: YES
wp-content/thesis/boxes: YES
wp-content/thesis/master.php: YES → 0.2kB on 01/25/2016 at 02:41:36
Thesis Skins and Boxes
===========================
Installed Skins: Classic Responsive
Installed Boxes: Thesis Developer Tools
Active Boxes: Thesis Developer Tools
WordPress
===========================
WordPress Version: 5.0.1
Filesystem Method: direct
Using Multisite: NO
Active Plugins:
PHP
===========================
Version: 5.6.36
cURL: YES
Max Upload (according to WP): 32 MB
Memory Limit (ini): 1024M
Memory Limit (usage): 43 MB
Memory Limit (WP): 40M
Server/Database
===========================
Site URL: http://www.jamestownspeaks.org
Server Software: Apache
Options Collation: utf8mb4_unicode_ci
MySQL Version: 5.6.39-cll-lve
PHP Handler: litespeed
Browser
===========================
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:64.0) Gecko/20100101 Firefox/64.0
Have you checked to make sure that your /wp-content/uploads/ and /wp-content/themes/ directories are still in the right place on the server?
Your images are giving 404 errors:
/wp-content/uploads/2016/04/CloudBall2.jpg
/wp-content/uploads/2016/03/bear-logo.png
And your pages are trying to call /wp-content/thesis/skins/classic-r/css.css but I think it would normally be at /wp-content/themes/thesis/skins/classic-r/css.css (note that “themes” is missing from the first URL)
Thanks so much for your reply. I’ll look into what you raised. I’m scratching my ghead over what happneded and hopefully can get it fixed. I do now have access to a site backup that I think should be good. To add bad to worse, GoDaddy hosting lost my backups but they got them back today.
I’d like to close the loop on this and report it resolved. The issue was that the permissions on wp-contents had somehow changed and it was something GoDaddy had to fix. The cause is a mystery but most likely due to a failure during a migration attempt with VaultPress or a hung process during a GoDaddy file restore request.