• I am wondering if the Classic Editor will continue to be supported? The new Gutenberg is too confusing for my community to use as the users are all non-savvy and prefer to just have a simple form to fill in for the headline, the main text for update and select the category. I tried the new editor and non of them were able to use it.

    If the classic editor is to go away, I will have to switch to a different CMS… unfortunately.

Viewing 7 replies - 16 through 22 (of 22 total)
  • and this is getting urgent now, as I am back in work mode and a bit behind on keeping my site updated

    @otto42 no reply ?

    Tried to see if I would have any luck by using different internet explore, so I have tried on both firefox and chrome, but on both, still giving me the 504 gateway timeout message, after clicking on the debug info tab

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    We can’t help you unless you give us information to work with. You say that the debug screen times out on you, well, then you need to fix that too. Why does it timeout? What is wrong with your server? Basically, you’re giving a list of problems, but not any indications as to any answers.

    You posted info that indicates that the REST API and the cron loopbacks are not working. So you need to fix those. Can’t tell you how, because I have no idea how. I don’t have access to your site. I can’t see what’s on it. All I can do is to provide you with advice.

    My advice would be to figure out what is so broken about your site that it can’t do loopbacks or REST calls. What’s in the .htaccess? What plugins are you running? You do need to know some level of code and how websites work to be able to fix problems like these.

    If you can’t figure it out, then I suggest hiring somebody to fix the problem for you. Or asking your hosting service.

    ok
    i’ve doen everything you ask me to do, I have a very good internet connection ( 100Mbps so I don’t know why I would be getting a time out
    Why is this happening, well, from my end, all I see is, before Guthenberg, no problem, everything works as it should, guthenberg thrust on to me ( why ) and now not working
    Maybe there is an issue with my server/ site, which is so small it did not affect anything, but with guthenberg it does
    still, logic has the finger pointing at this new guthenberg being the issue
    so why can’t things just be left alone
    4 days now where I can’t post, and you are guiding me to fix it, but we are not getting anywhere
    so yes, I am going to have to hire someone , which will cost me money, and again, all this because soneone at word press thought it would be a good idea
    so to that person, big thanks

    • This reply was modified 7 years, 7 months ago by sonnyphotos.
    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Maybe there is an issue with my server/ site, which is so small it did not affect anything, but with guthenberg it does

    That’s exactly correct. If the REST API isn’t working, then the new editor most certainly will not work either.

    The fact that your cron also isn’t working shows that the problem is something more fundamental to your server configuration. But I can’t tell you what that is without knowing more about your server, how it’s configured, what the config files have in them, etc.

    ok
    turns out I needed to update plesk on my server and get a security certificate
    still having issues with the api
    and healthcheck the debug tab is no longer timing out, but it shows nothing in that tab, just blank space

Viewing 7 replies - 16 through 22 (of 22 total)

The topic ‘WordPress classic editor’ is closed to new replies.