peg

@clorith

The other users are not reacting to your review, they are reacting to me, which is hijacking this review and isn’t acceptable at all.

Please do not feel personally attacked. Nobody is hijacking this review. I only add my opinion to a shared perception of wrong behavior which the title of this review clearly states.

I’m sorry you find out support lacking, it’s worth noting that we’re an open source project, not a company product, and as such we do not need to live up to those notions of “the customer is always right” (which is where I see you heading with your statement, if it’s not, I apologize).

Well, you are right and let me tell you, why:
WP might be an open-source project, but it is indeed a product. We might not pay you with money, but we pay you with market share, marketing, image creation which ultimately supports a product: WordPress and a company: Automattic.
WP is a product because it has users. Users, who depend and rely on the fact that this product works as described, especially because this product is not an end product.

Let me give you an analogy:
I am a producer of cars.
You (I mean: developers and decision makers of WP) are the producer of car engines.
No matter how I pay you for your service or product, I decided for your engines to be built into my cars.
Suddenly, you deliver engines that are completely different from the ones I used to build my cars with, which I have neither ordered nor agreed to. And clearly, my cars don’t work anymore. Other car parts depending on the engine structure don’t work anymore. And I – I have to stop production.
So, what does any sane end producer do?
Well, first, perhaps, we would try to talk to you, asking for a “why”.
— Getting crazy or no real answers like “this is the future”.
Then we would try to find out the cause for this “happening”.
— Our research reveals that you are about to also build the car trunk and the windshield wipers into the car engine …

Now, at that point we are beyond the possibilities of working with your new engine. We have to find other suppliers who can provide us with what we need for our cars: an engine.

Are we angry: yes
Will we support and recommend you: no
Would we ever trust you again: no

Merry christmas!

@clorith:

It’s also a well known fact that happy users do not go looking for places to tell everyone they are happy, while disgruntled ones will look for a place to vent and throw blame

This is too easy!
I’d recommend you guys do some more research on terms like “complaint management” and “customer feedback”. Looks like we all cannot expect that you decision makers do understand even the simplest of rules of user feedback:
As long as customers / users complain they are still in the game. They try to reach you in order to see if there is anything like a compromise possible. But, and this is the dangerous part, if they are quiet, they have already left the sinking ship – without telling you.

Design by committee (which is what votes are), are not a good approach to any solution, we won’t be doing any vote.

Why looking for a solution if there is no problem, right?
Why asking people to vote, if everyone already knows the outcome, right?
Why giving users of of an open-source platform a voice, right?

I am so shocked by you mini elite WordPress bunch of not-to-user-listeners wrong-decision-makers, I can’t even put it into words.

Good that you can remove an additional editor plugin and the rest of the world has to add one to their site in order to not being forced to use this editor …

Hi Tammie,

what I was seeing wasn’t the “white screen of death”, it was actually a blank admin page. I did some further testing and the reason I am seeing this is simply because I deactivated the default endpoints from the REST API. So it is not a bug with the plugin. It’s an issue with my security measures.

Nevertheless, I can only hope, that you guys take all of the bad and honest reviews seriously and rethink your decision on building this editor into core.

Hi again.
By further testing I have now found the reason of the above behaviour. Besides the Page Builder issue I found some more css problems and also that error messages (woocommerce and contact form) did not display.
So I started to remove each setting in the plugin one by one and once I set “Remove Pingback” option to “no” all was back to normal.
I thought that this option would only remove the header tag but it seems it does a bit more…

I have made a support request pointing to this thread.
https://support.hogash.com/support/topic/conflict-of-page-builder-with-latest-update-of-wp-hide-security-enhancer/

Hopefully they can help.

Hmm, what can we do? I am not on facebook. But if you are, you might get in touch with them there: https://www.facebook.com/hogash.themeforest

It is the built-in page builder of the kallyas theme:
https://themeforest.net/item/kallyas-responsive-multipurpose-wordpress-theme/4091658

Hey. Thanks for your quick support! The error message is gone.
My pagebuilder unfortunately is still compromised. The elements are not loading and the html looks strange. Could you let me know what might be causing this?
I can confirm that it has to do with the recent update because when I revert back to version 1.3.6 all works normal.
Thank you.

Yes. We could solve the issue.
For anyone reading this, please disregard my statement. It must have been a problem with email delivery. UM do answer their tickets.

Hi Calum,
Thanks for your reply. I have just sent the email with the text “For the attention of Calum”.
Thanks.