abletec

Penster4, changing the theme is a *temporary* measure to see if the problems resolve. If so, then you know the problem is your theme.

Sometimes the code in child themes becomes out-of-date & causes errors, or contains errors in & of itself.

The objective here is to try to figure out why you’re having the problem. Clearly, if you change the theme to its parent, or as I stated, better yet, to a default theme, & the problem goes away, then you know where the difficulty lies & can start working from there. It’s merely a temporary attempt to track down in which component of the WordPress installation the problem lies.

Hello, penster4, & welcome. These things can be tough to troubleshoot, but here are some equaly random thoughts from a likely much slower mind.

* You’re using a child theme. Please switch to the parent–or better yet–a default WordPress theme (these begin w/the word ‘twenty’), & see if the problem resolves. If it does, then you know your problem is w/your theme.
* Your Instagram feed appears not to be working, & the message is that your access token is invalid. If you’re using a plugin for this, often they have a page where you can go to get an access token.

Thank you *so* much for giving us your site url. It was incredibly helpful & saved some time, ie, it’s the first question we’d have asked, & then both of us would have to wait around until that was answered.

michaelnjc, from the sounds of it, you’re entering the wrong credentials. Unfortunately, these things are not standard amongst hosting providers. Some, like me, use the same ssh credentials as the client’s CPanel. Others have totally different rules. Some also use different ports instead of the standard port 22.

Some links that may prove helpful are:
https://my.bluehost.com/hosting/help/180 &
https://my.bluehost.com/cgi/help/301

Other than that, I don’t really know what to say. Perhaps posting a job on:
http://jobs.wordpress.net
might also be helpful.

Hello, michaelnjc, & welcome. The problem is that the scripts are likely timing out. If Bluehost permits shell access, then WP-CLI is the perfect tool for this. Otherwise, you may have to break your imports down into smaller pieces.

Hi, pamjasperx, & welcome. Do you happen to know whether your hosting control panel has an applet where you can view your site’s error logs? Also, have you checked your upload_max_filesize & your post_max_size & compared it w/the size of files you uploaded?

I feel terrible for asking now, but, having said that, the lines I point out look as though they may be contributory. This is 1 of the standard procedures in these sorts of circumstances.

Hi again, johannaa. Please go to ‘Settings > General’ of your site & ensure that the url structure is in fact https://www.supportuw.org.

If that does not help or is already in place, can we please see your .htaccess file? Please enclose it in , ie,

line 1
line 2
line 3

I know your IT department says it’s fine, & it likely is, but I guess I’m from Missouri even though I’m not.

It appears you’re hosting w/Network Solutions, unless my not yet having had coffee this morning is seriously impairing my investigative prowess. If I am indeed correct here, do you have facilities such as a control panel wherein you can see error logs?

Actually, I think I was doing pretty well figuring it all out. I just didn’t want to miss something if I could help it, Michael.

I figured the stray quote was likely a pasting error, but you know what you do when you assume. So I thought I’d point it out just in case it was relevant.

I think the forbidden error is pretty telling, & I suspect perhaps some changes made to your hosting provider’s mod_security rules may be the culprit. Again, I’ll ask if WordPress is set to close tags automatically, because if so, then closing them manually may (or may not) create problems. But I think your next call is to the hosting provider, asking them to check on whether mod_security is firing on some rules.

If the hosting provider doesn’t/can’t help, I’ll be glad to offer you a staging area on my server in order to clone the site & see if you’re receiving similar results, if that’s of interest. If no problems occur, then we pretty much know it’s a hosting issue. You’ve actually kind of done that already on your local box, but it might be something to consider nonetheless.

You’ve done a really great job troubleshooting this, Sir, & I do hope that once this is all said & done, you’ll think about joining the volunteers here to lend a hand to those who need it. We could always use more help. & you’ve already got a friend on here so it’s not like you won’t know anyone, which can always be a bit intimidating :).