Live data from Hacker News

Things I’d want to see improved in WordPress core

masterwp.com

21–30 of 63 posts

Re: Things I’d want to see improved in WordPress core

#21
post #2

The thing I want to see, above all else (and it is coming, but slowly and without any kind of apparent over-arching strategy - which it badly needs) is designer / developer control. Gutenberg gives remarkable agency to editors, which from one angle is great - lovely to be able to add a column, shift a block upwards, pad that image over to the right without any technical skills. On the other... I don't know a web desi…

> I don't know a web designer in the world who wants to give their editors complete control.

I'm thinking this might be aimed squarely at scenarios where the editor, designer and admin are all the same person.

Re: Things I’d want to see improved in WordPress core

#22

The biggest mess IMO is the media library. Unsustainable, chaotic, impossible to keep in order if you happen to publish more than just a few images. It’s not a library. It’s a file dump. If you want to reuse an asset on a non-trivial site, it’s easier to reupload the file rather than to find it in a flat list of thousands of thumbnails. Folders, please. And the four hopeless fields to provide an image with textual me…

Folders are something that's been needed in WordPress for 10+ years and hasn't gained any traction. It's to the point where it's beyond terrible and is a large reason I don't use WP anymore.

Re: Things I’d want to see improved in WordPress core

#23
post #10

Port it to a modern language so PHP can finally die, add support for PostgreSQL and MS SQL

not a fan of php either but I wouldn't go that far. I'd love to see it reimplemented with modern conventions over Laravel. As much as i dislike php in general, I have to admit the laravel guys have done some amazing stuff.

Re: Things I’d want to see improved in WordPress core

#24
post #2

The thing I want to see, above all else (and it is coming, but slowly and without any kind of apparent over-arching strategy - which it badly needs) is designer / developer control. Gutenberg gives remarkable agency to editors, which from one angle is great - lovely to be able to add a column, shift a block upwards, pad that image over to the right without any technical skills. On the other... I don't know a web desi…

> I know many WordPress designers who have upped and left to look at other platforms because they need client constraint, not "ultimate freedom".

This is a reason why some build custom themes and blocks

Re: Things I’d want to see improved in WordPress core

#25
post #2

The thing I want to see, above all else (and it is coming, but slowly and without any kind of apparent over-arching strategy - which it badly needs) is designer / developer control. Gutenberg gives remarkable agency to editors, which from one angle is great - lovely to be able to add a column, shift a block upwards, pad that image over to the right without any technical skills. On the other... I don't know a web desi…

> I know many WordPress designers who have upped and left to look at other platforms because they need client constraint, not "ultimate freedom". This is a reason why some build custom themes and blocks

That's what we do. But (at least until now, it's slowly changing...) you could still take a beautifully designed theme and butcher it by doing some of the things I describe above.

Re: Things I’d want to see improved in WordPress core

#26
post #21
post #2

The thing I want to see, above all else (and it is coming, but slowly and without any kind of apparent over-arching strategy - which it badly needs) is designer / developer control. Gutenberg gives remarkable agency to editors, which from one angle is great - lovely to be able to add a column, shift a block upwards, pad that image over to the right without any technical skills. On the other... I don't know a web desi…

> I don't know a web designer in the world who wants to give their editors complete control. I'm thinking this might be aimed squarely at scenarios where the editor, designer and admin are all the same person.

Some truth in that, for sure. I think they're clearly aiming at the Squarespace / Wix market which is probably the scenario you describe.

Re: Things I’d want to see improved in WordPress core

#27

Earlier quoted context omitted.

was it due to the core or a plugin?

very vanilla wordpress, it was a basic blog site. I think the only plugins I used were google analytics and some basic theme. I would keep it updated whenever I remember but maybe it wasn't often enough. Not exactly sure what the vector was and from whatever quality of analysis I did, the system didn't appear damaged beyond the changes made to the wordpress folder and luckily, the damage didn't seem to escape the www…

I'm gunna suggest compromised hosting. The issues I've seen (once plugins / core / php is up to date and obvious stuff sorted) has been almost entirely on shared hosts.

Re: Things I’d want to see improved in WordPress core

#28
I only used wp once but the most surprising thing for me was that default installation used 7 SQL tables and their schema uses 3 different conventions (table.ID/table.table_id and table.foo/table.table_foo). Maybe if DB themselves enforced some kind of limits like [a-z0-9_] this would never happen.

Re: Things I’d want to see improved in WordPress core

#29
Since everyone else is posting their wish-list, here's mine.

Use a database like SQLite so I can back-up a website into a ZIP without being concerned about keeping a separate MySQL database backup in sync. (I wrote about this three years ago: https://billpg.com/dear-wordpress-please-stop-using-mysql/ )

Include TOTP one-time-password login in the core. (I hate having to deal with plug-ins.)

Full backup in the core. When triggered by cron, save a complete backup to some folder. The setup, once the DB is configured, would have a option to restore from a backup, including populating the database, themes, wp-content, etc. Skip doing a backup if nothing has changed since the last one.

Make multi-site easier. There's so many steps where I have to paste stuff into config files. Instead, have all of it ready for me to create a new site and if I never stray into that section and create a new site, no problem.

Lose the URL settings and work it out from the request. If a request (after URL rewriting) comes in looking like example.com/thing/index.php?abc=xyz, then you know what the base URL is. If I install wordpress as localhost:8080 and suddenly requests start coming in as example.com:443, I really don't want a redirect back to localhost:8080.

Re: Things I’d want to see improved in WordPress core

#30
I was a WP dev for 5-7 years before moving on to bigger and better things. It's easy to hate on the platform, for both justified and unjustified reasons.

As a writer, it's good not great. As a low code dev, it's the best because you can do 99% of what you need to do with no licensing costs. As a regular beginner dev it's a great platform to learn on. As an experienced dev it's just terrible to get anything done and too many people never graduate from it for larger build outs. Here's just a random list of hot takes I have (keep in mind I have not worked on the platform since Gutenberg got introduced, though I imagine much of the backend code hasn't changed)

- It's not an application framework, so stop treating it like one. It's good at blogging and decent for laying out web pages. If you need it to do other things, use Laravel or Grav or something

- File management is completely unmaintainable for anything more than a personal site. I've worked on some larger 2000+ page sites and it's nothing short of a nightmare.

- Post/page versioning is basic. There are plugins that do a much better job at accomplishing this, but it's time that it makes it into core. I'm talking about an actual publishing workflow with visual diffs and such.

- The backend API is atrocious. Using methods like get_post or the_content are great examples of why people hate PHP. Inconsistent naming, unclear usage, no namespacing, etc etc makes it really hard to read code. I'm a .NET dev so I'm probably a bit biased but with the amount going on under the hood, a service layer is necessary.

- Being able to rapidly prototype with themes and plugins is great and part of the dev experience, but unfortunately most projects never mature past the prototyping stage.

- The community surrounding WP is great, and Wordcamps are a great experience. I've given a couple of (admittedly bad) talks at WC Milwaukee and was surprised at the range of people that attend them.

- One of the talks I hosted was about how to use Xdebug with WP. Maybe things have changed, but I threw the talk together because _maybe_ 1% of devs I ever interacted with in the WP space asked if I had stepped through my code with a debugger. var_dump is a terrible crutch that PHP devs rely on way more than they should. I know things have improved with Docker compared to the days of Vagrant, but even at the time WP devs seemed to lag behind the rest of the industry in this regard.

- Last thing, I have terrible nightmares still about the database schema. Too many plugins/themes rely on post_meta and (whether you agree with them or not) I think WP needs a proper ORM.

Quick Edit: I will praise WP's for its plugin architecture with actions/filters. I've replicated this in our own .NET-based application and really love just being able to hook into places without dealing with nasty hierarchy structures.

Post reply on HN