robinanonymous

@hljeffries Aw man, pure HTML outsourcing sounds like a total nightmare. I was going to provide an obvious suggestion (rebuild the site) but if it is pretty big and you have already been editing for over a year I can understand the inability to easily transition.

The only conclusion I can imagine that could potentially be causing this issue (if that is sincerely the only edit you recall making when visual began dysfunctioning) is this…

WordPress was updated not long ago and the editor is updated frequently . As you know, it is extremely rare that any modern site is built on HTML alone. So, perhaps as WordPress and the editor evolve they’re developed to co-adapt with the way most modern sites are built; a combination of HTML, CSS, JS, etc. Maybe some edit you did around that time or previously has had a dysfunctional effect on the way the scripts recognize a function via the updates.

Whether or not this is potentially the case – my only suggestion would be to call HostGator and have them backup your site to just before the dysfunction occurred. Again, apologies if you have to redo edits but you’re better off doing that if it means you can continue working again.

Meanwhile, God bless your soul on that kind of site! (I’m not religious – just feel sympathy for having to go through that back-and-forth. lol)

Wow, nice timing hljeffries! Just checked my email. (It seems I accidentally missed RebelDietitian’s post. Sorry.)

Regarding the hard coded font style that should not have been there – why was it there in the first place? I figure starting here is the most important thing to consider. This is because everything was working normally up until the point that you edited the hard code.

For example, if that hard-code was automated through a plug-in then chances are that the plug-in itself is faulty – even if it worked just fine before. If a plug-in is faulty it can do serious damage to the functionality of your back and front end. Whether or not you like it, your only option is to deactivate and delete the plug-in entirely. After deleting, if the issue still remains that means the damage has already been done so you will have to call your host and ask them to backup your site to just before you made that edit. (This is what I had to do. Annoying because I had to re-do some edits but at least everything was working again!)

Anyway, the point is where did this hard-code come from?? Let’s start with the origin of the issue.

Hello gkarmas,

Yes, I was able to fix it! I’m sorry to hear you’ve similarly tried many solutions.

As a few people have mentioned in my forum searches relating to this issue – the cause is different for everyone’s situation – so it requires patience as you try to learn what yours may be.

It turned out my issue was that I exported a blog from my client’s old website which was a) an outdated version of WordPress and b) corrupted by hackers and taken down by her old web host (2MHost – low quality providers with poor security standards and email support only).

One or both of those reasons had to be the issue because I tried everything else. Therefore, I called our current hosting provider (iPower – higher quality with better security standards and 24 hour call/email support) and requested that the website be reverted back in time just before I imported the corrupted blog.

Due to the reversion in time I lost some edits on the site that I did after the blog import but it was worth it to at least finally see the visual editor working again and just continue forward.

So, in a summation, my cause was due to imported corrupted files. It made the WordPress interface glitch.

Good luck on your search!!!