nykzukowski

WordPress does not need “renewed” in the first place–that’s the problem. The developers insist on forcing this onto a community (apparently they are too dense to understand the concept of “community” in the first place) that has shown overwhelming opposition to it.

I guess their motto is if it ain’t broke, break it even worse and sell it as if it’s somehow better. Completely unacceptable.

Hi Con,

I got my issue resolved. It was actually due to a conflict with Awesome Support in which I negated to set the WooCommerce integration up correctly.

Sometimes things are much simpler than they appear. ??

This is so incredibly backwards. GUTENBERG should be a plugin, not requiring a plugin to REVERT to a far better system.

What is this? Is this pride? A power trip? The community is going haywire over this and you just keep on insisting that this is absolutely how it’s going to be. You aren’t listening to the community. Who in the world gave you, Tammie, the power to decide this for the entire community?

Who are the individuals responsible for doing this against the wishes of the community? I know Matias Ventura, Joen Asmussen, and you, Tammie Lister are listed as the developers. I want the names and contact information of every single person who is taking it upon themselves to implement this in the face of HUGE resistance from the entire community.

Hi Rick,

Can you provide some links to sites you’ve built, please? From what I can tell, more experienced developers have the wisdom to know that this will be a catastrophic mess if this is integrated into core.

I have noticed quite a trend of people who give this 5 stars having very, very basic sites where a drag-and-drop editor like this may be a good idea. But more experienced developers who do this professionally and who build far more complex sites with CPTs, CFs, etc. can see this coming a mile away.

Thanks.

Copetto,

Do you have any links to sites you’ve built other than your homepage? It seems very simple and a site that would fit more the goal of Gutenberg–not a complex CMS.

Thanks.

A lot of us revolt because we’ve had enough wisdom with our clients to know this is a bad idea. WordPress core devs are devs deving for devs.

Building a site for a client / end user (the final target audience of the devs that the core devs are deving for) is a lot different. My clients don’t want to drag and drop and move things around. They don’t need a page builder.

They need and want a clean, clear, concise way to edit documents in the same way they use software like MS Word / Google Docs, etc.

Gutenberg’s seeming target market is DIY business owners who are using services like Wix. They kinda want to design their site themselves, but don’t know a lot about development, computational logic, and the like. Drag and drop. Move things around. Save. BOOM.

Another target seems to be entry-level developers who are just a couple view-sources above homeboy over there crankin’ out a quick 4-pager for he and his cousin’s lawn mowing gig.

More seasoned, experienced, and wiser developers can easily see this from a 30,000ft view and how it will directly affect their clients, the final end-users behind the site’s entire purpose.

Visitors aren’t seeing this change. It’s all back-end. Integrating Gutenberg with core is a terrible idea and will prove to be disastrous if it actually gets forced in 5. KISS, and IIABDFI.

If you insist, please for the love of all things sacred in web development, keep this as an OPTIONAL, off-by-default plugin.

The resulting trainwreck for doing otherwise will be a disaster that will cause many a headache, whisky barrels of coffee to scramble together patches when TSHTF, lost profits, unpaid bills, hungry kids, breakups, and may even save a couple people from getting fired.

Please think about this and be wise in your decision to rock the boat this hard. Trying to fix what isn’t broken rarely turns out anything fractionally as good as how it was in the first place.

Issue was resolved. There was a conflict where WordPress was installed on a subdirectory of my domain and the PHP version for the main directory was 5.4, though the PHP version was 7.0 for the WordPress directory.

Now that this is back up and running, we are running further tests and will be purchasing upgrades soon. Thanks! Excellent plugin.

However, the prompting for a reason why the plugin is still off-putting. It may have not submitted due to the PHP version error. Thanks.

Update:

I am not sure what is going on, but the link to the files in the email are going to a 404 on my site and not actually downloading the file.