rudybrinkman

@karmatosed I’ve updated this posts after extensive testing and I assume this will answer your questions.

So what is so great about it? If you rate it 5 stars, I would at least hope for a list of great improvements you noticed,… Like: stuff you can do now, and that couldn’t be done before. How it improves your workflow. Many over here stumbled over several serious bugs. You didn’t?

Oh, btw.. here’s a suggestion to the developers.

1. make it part of the core app on WordPress.com first. See what happens when you bug people with this “upgrade”.

2. did it ever occur to you that WordPress is used by many companies, small businesses, private users and so on that just want a functional platform to publish their website a.k.a. content. They’re not looking for a load of (non working) fancy stuff.

And finally — why don’t you ask people who give out 5-star ratings what they think is so amazing ..? You only ask people who give ‘bad’ ratings what is wrong. But I’ve read some of the 5-star “reviews” and they are even worse than the negative feedback. They don’t tell you at all what they like so much about it. That would make me, as a programmer, very suspicious.

• This reply was modified 6 years, 7 months ago by rudybrinkman.

When the editor starts, it doesn’t look like an editor at all. You have a ‘heading’ line and .. nothing. No space to write your article (not at first). It just doesn’t look like an editor. It doesn’t even look like a page builder. It’s something in between, cluttered, messy.. not intuitive at all.

Beginners will look at it and will be even more puzzled than those who do have experience in working with WordPress. It was an editor. Keep it that way. If you don’t and make it default, people will run from WordPress. They simply won’t know what to do. I, at first, didn’t either. And I’m a very experienced user!

I think most comments here make it clear. As I said: Kill this project. Save yourself the time and effort to develop it even further more. If this will be the default editor, people will replace it with a plugin or even abandon WordPress. New users won’t even bother trying to understand how this works.. The fact alone that almost 60% of the people who reviewed it give it 1 star or less says it all I think. You’re taking the wrong turn. As an optional plugin: fine. As part of the core? Ludicrous!!

__
Oh, for the record: I’ve been working as an IT employee, including software tester and functional management, for almost 30 years. I programmed software (Pascal, Delphi) and currently work as an applications manager and own a hosting- and webdesign company with well over 1,000 clients. I’ve created well over 100 websites the past years using WordPress.

• This reply was modified 6 years, 7 months ago by rudybrinkman.
• This reply was modified 6 years, 7 months ago by rudybrinkman.
• This reply was modified 6 years, 7 months ago by rudybrinkman.

The only caching on that specific site/server is OpCache.
That might have caused it though since that’s Zend’s PHP script caching.

Thanks for responding.

Solution:

– update WooCommerce;
– renamed the directory back to it’s orignal name;
– re-activaded the plugin.

It worked with no error. Pretty weird, …

You will need to allow people to sign up and create a profile. If it also doesn’t work when you’re logged in as admin then there’s something else failing. Do use the widgets for creating profile.

You don’t think I’d be willing to install and test again on a live server with ~600 clients on it, don’t you? Come on, it’s a serious bug! As soon as I (others reported it too, here as well as on Twitter) click on the ‘media’ button, WordPress starts looping.

FYI the server setup is:
Cloudlinux
8 Gb RAM [2 Gb available per user / LVE]
Raid set with 64Mb cache disks (Seageate Constellations)

Normal server load: ~ 1.0 or less,
Server load as soon as the button was clicked: > 20.0
And it kept that high untill Apache was restarted. In the Apache server-status I could see it was the Ajax component for media files.

I assume this is enough for WordPress team. The only reason for me to register here is to tell you all about it. Do with it whatever you please.

It also happens on clean install of WordPress 4.0 with no particular plugins accept bruteprotect; installed using installatron.

What happens is that as soon as you click on the ‘media’ button, it starts looping, bogging down servers. This bug needs immediate attention since it might even crash servers within hours as soon as people start updating. I’ve told my clients not to update and don’t update my own sites.