Since update can no longer edit pages using Classic Editor
-
I’m helping someone who has a WordPress.com build with Visual Composer installed, latest versions. They’re unable to edit a couple posts with either Visual Composer or the Classic Editor, and many posts are no longer editable using the Classic Editor – the TinyMCE editor just doesn’t appear. I’ve followed the usual process of disabling all plugins and only when I disable Visual Composer can I edit these posts with the Classic Editor again.
There’s no code or markup in these posts that strikes me as problematic – in fact I can edit a page in PHPMyAdmin, removing all markup, and still can’t edit the post until Visual Composer is disabled.
This wasn’t a problem on 18 October and we’ve not touched the site since, except WordPress and the Visual Composer have both been updated since.
I intend to recommend removing the Visual Composer plugin but before I suggest the nuclear option, is there anything I could try to resolve this?
-
@rohanvc I’ve deleted your offer to login to your user’s site. While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
- Ask the user to install the Health Check plugin and get the data that way.
- Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
- Ask the user to create and post a link to their
phpinfo();output. - Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
- Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
- Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
You’ve been placed on “modwatch” until we’re convinced such postings have stopped. Your account has *not* been banned, we just want to check things for a while before they’re public. If you wish to take issue with this, contact moderators via the #forums channel on slack (https://make.www.ads-software.com/slack)
- The topic ‘Since update can no longer edit pages using Classic Editor’ is closed to new replies.
