Brandon Williams said
Hmm. Well there’s a problem. What am I to do if I’ve paid for this forum, but cannot use it?
That’s not actually the case is it? Simple:Press is completely free – there is no cost to use it. There are additional paid-for and optional plugins and theme options. And you have paid to have our full support on Simple:Press issues. This is what we are doing here.
Doesn’t seem to be fair to have to pay a developer to fix this.
A developer (or perhaps developers) somewhere along the line have written stuff that you are using that is not working. The ideal solution, of course, is to go back to them and request they correct their errors – whatever they are. If the site itself was constructed by a single developer then that is the person to talk to.
These issues are not Simple:Press related. Simple:Press is a casualty of what, I suspect, might just be careless code or, perhaps a plugin that is genuinely broken in some way. You do have 18 plugins awaiting an update I see.
I definitely appreciate you taking a look, but is it possible to have the other two check it out too and correspond with me if you all have questions on a certain issue?
I don’t know where to start, and I wouldn’t really know what to tell a developer either as to how to fix this…
If you had to tell a developer anything it would be to look at the errors. @mr-papa – despite your obvious reluctance to take his word for it – has already highlighted what be thinks is the first problem to resolve (the malformed ‘defer’ attribute). He has also made the suggestion that you deactivate all of the caching plugins – especially the one that is adding the defer to scripts (that will probably be the one trying to load cached javascript files).
Earlier, I believe it was suggested you swap themes for a few minutes to see if that sorts things out as themes, sadly, often cause conflicts with plugins. But the one above is a more likely candidate.
I will add that it is worth updating your 18 plugins awaiting action as any one of those might be needing an update due to code issues.
As a second from last resort, and if it was me, I would:
- put the site into maintenance mode for half an hour
- swap to using the default WP theme
- deactivate ALL plugins one at a time
- between each deactivation clear the browser cache and try the SP update.
- when things work as they should then you know you have found a problem plugin and can take the necessary action.
- put the site back together. This whole process can be done in minutes.
I would also add that all the caching plugins in the world will not help performance if large numbers of errors are being discovered during page construction and messages sent out to the console. And this is indeed what is happening on your site at the moment.
