4 ms·
WP could make a test suite mandatory and run tests on their hardware under their supported configurations; if it doesn't work on sqlite, it is not accepted in t
by Cthulhu_ 4y ago
WP could make a test suite mandatory and run tests on their hardware under their supported configurations; if it doesn't work on sqlite, it is not accepted in the plugin index.
Likewise, security checks.
- dawnerd 4y agoThey really need to force all plugins to pass the VIP phpcs rules (would need to be modified a bit). It wouldn’t be perfect but I bet it would greatly increase security. I’d also like to see them switch to git for the plugin repos.
- desas 4y ago> I’d also like to see them switch to git for the plugin repos. Could you explain this idea some more? It doesn't seem related to your first suggestion. Some people just use the svn plugin repos as a release system, the actual development being done in git. There are even github actions to automate it.
- Ayesh 4y agoAnd the plugin authors would simply self-host them. Some of the top plugins available (and are linted) on WordPress.org tend to be stubs containing a lite version plus an ad, and those plugins will have less friction if they entirely self host on their own servers.
- mgkimsal 4y agoToo many people doing that will mean that what you're looking for just won't be in the main (GPL?) plugin area. My own experience years ago was that for many folks, if it wasn't in there, it didn't exist. Downloading and FTPing 'out of store' plugins just wasn't something that folks wanted to get in to. Those projects may have been a minority of the overall username, but it wasn't an insignificant number of projects I knew about. Perhaps that attitude has changed in the last several years?
- deleted 4y ago[deleted]
- jillesvangurp 4y agoWould not be a bad idea. With Github actions, doing CI builds for plugins and wordpress should be fairly easy to do with either dockerized mariadb or sqllite. Set up a little matrix build. And for good measure, maybe support nginx and posgresql as well out of the box. Nothing to incentivize plugin developers as having a few red warnings next to their name in the plugin registry. I setup builds for most of my oss projects. It's not that hard. Of course at the scale the wordpress community operates, this would require some non trivial amount of resources.
- technion 4y agoNote that Wordpress don't use Github, or Git for that matter. https://core.trac.wordpress.org/browser/trunk https://core.trac.wordpress.org/browser/trunk
- unity1001 4y agoYour very comment would be enough to turn off 60,000+ plugin developers and 50% of the web who uses WordPress. Nobody likes anything being forced on them there. Less, non-prominent OSS projects trying to force their way in through such arrogance.
- axelthegerman 4y agoOr you could do nothing and let Wordpress rot until nobody uses it anymore. Problem solved, nothing to do for 60,000+ plugin developers.
- unity1001 4y agoWordPress will surely rot if a rather-weakly adopted database engine is not forced upon its entire ecosystem. You can be sure that the flower shop owner somewhere in Idaho, who uses WooCommerce for his flower business and the random anime blogger somewhere in Tokyo, who uses WordPress for blogging, will be hampered by that.
- kzemek 4y ago
- unity1001 4y agoYeah. You can be sure that 60,000+ plugin authors and 50% of the web that use WordPress and those plugins will just allow that.
- Gordonjcp 4y agoFuck 'em. The world doesn't need 60,000+ badly-written buggy insecure WordPress plugins. Adapt or die, and in WordPress's case, preferably the latter.
- unity1001 4y ago
- apocalyptic0n3 4y ago> The world doesn't need 60,000+ badly-written buggy insecure WordPress plugins. The world might not, but site operators think they do. It's the biggest appeal of the platform and why agencies have such a tough job doing non-Wordpress work. For better or worse, the simply stupid number of Wordpress plugins out there drive roughly half of all websites on the web today.
- Gordonjcp 4y agoYou're right, and "think" is doing a lot of work there. Everyone wants their very own special magic guestbook plugin or some damn thing, and they're often very much a "my first PHP module" thing. So it's hardly surprising that they're not the best code or written with particularly safe practices in mind. Guddling about on some old disks a few months ago I found some of the very first PHP3 code I ever wrote, and it's one big SQL injection from start to finish. The 90s were a simpler time... Roughly half the 404s on the forum I run are some attempt to access WordPress admin pages, which I guess must tell us something.
- unity1001 4y ago> The world might not, but site operators think they do Well. Considering how WP is basically ~50% of all websites on the planet, that would indeed classify its 'the world' who thinks that they need those 'badly-written' (whatever that means), buggy (is there non-buggy code anywhere), insecure (any software that gets used by 50% of the Internet without security issues?) WordPress plugins. ... Really, his/her perspective just feels like a junior dev's perspective. Or the perspective of a senior dev who never had to take at least a position like a tech lead. And god forbid any kind of actual interaction with the end users in a given ecosystem.