It’s just the default editor.
Can you refresh that page after clicking F12 (or whatever opens developer console in your browser) and see if there are any errors reported in ‘console’ tab?
I cant see anything specific to PW, or could be specific to PW in there. But there does seem to be some errors which could break your editor.
Do you have Autoptimize installed? Or similar optimization plugin, or do you have anything that optimizes JS and/or CSS?
This is a fairly fresh install, maybe ~9 days old. The only other plugins I have at this point are SG Optimizer(SiteGround) and Matomo Analytics. I disabled everything except the Patreon plugin and the issue stayed the same.
I don’t think the theme would have any effect here, but just for completeness: I’m running a child theme based on https://wordpress.org/themes/photofocus/
My theme changes are minimal at this point though. Just a small amount of custom CSS, a couple Google fonts, and added a custom logo on the login screen.
Not that it should make any difference, since this appears to be a backend issue, but just for good measure I tried a few other browsers as well. Same result.
Could you try changing to a default WP theme and see this will effect any change?
Switched to the Twenty Twenty One theme. Same result.
That is pretty odd. Im going to check if i can reproduce this and update this thread.
Cant reproduce this with WP 5.6.1 and PW 1.7.1
I did a fresh install on a different domain. I had no issues; everything worked fine. I’m not sure what’s going on with this particular site. It worked on my original install which was 5.6. It was only after running the upgrade to 5.6.1 that the problem appeared. I’ve tried reinstalling 5.6.1. I’ve removed the Patreon plugin completely and reinstalled. I’ll have to keep digging and see if I can figure out what’s causing it.
Here’s a quick video of exactly what I’m seeing:
There can be settings, scripts or cached code that remains from installed/uninstalled plugins or themes. They may cause such complications. Such cases are hard to track because you have to debug all the way to the origin plugin, which may have even been uninstalled.
Best choice may be to start from scratch and install all current plugins and then import content, and then move that new install to production site.
I haven’t had a chance to troubleshoot this any further yet. I just disabled the plugin for the short-term. I later discoverd two other issues when it was enabled. I could not change a featured image — it would just revert back. Also, load times on any page(even just the login screen) were taking 6-7 seconds. If I disabled the plugin then they loaded nearly instantly. I considered just doing a fresh install. Especially since the site is so new. Not much to transfer yet.
OK, I was able to recreate the issue on a new site. Here’s what I did:
I brought up a brand new, fresh WordPress site. Rebuilt my site exactly to match my current site. Same theme, same code, same plugins, same content, etc. This included the Patreon plugin with the connection configured and everything running.
At this point, everything was working perfectly. I thought the issue was resolved and was about to move it to production. The very last thing I did was to enable “Post Sync.” Then all the problems returned, same as before. The site started moving at a crawl(6-8 seconds between pages), tags getting stripped from posts, etc.
Disabling post sync at this point had no effect; it remained bugged.
Disabling post sync not addressing the situation points to the situation not being related to post sync but something else. Enabling post sync may have triggered updating of a setting somewhere.
Does your host have opcache or Redis or similar caching mechanisms?
Does the situation persist if you enable only Patreon plugin and then wait for a while (an hour maybe) and re-test?
- The topic ‘Stripping tags from Custom HTML blocks’ is closed to new replies.