Earlier quoted context omitted.
That’s awesome, now can you find one that points to all the plugins that cause these security exploits? Because none of those are from the default WordPress install with the Standard plugins (ACF Pro, CPT UI, etc).
THIS. Impressive how experienced developers and professionals fall for this fallacy all the time because, wait, they don't actually KNOW A THING about wordpress.
The complicated futility of WordPress
171–180 of 241 posts
Re: The complicated futility of WordPress
#172I’ve easily built hundreds of WP sites and Gutenberg makes me sad. Anyone raving about the block editor has clearly never used one of WP’s paid page builder plugins like Beaver Builder and Elementor, they’re in a whole different league. You of course can continue using these plugins, but the absolute chasm in quality separating these plugins and Gutenberg highlights Automattic doesn’t have the technical or design kno…
Re: The complicated futility of WordPress
#173WordPress keeps getting better and 5.9 was a big leap forward. The OP should try using a vanilla WP install, use or build a (child) theme that supports blocks, add WP Super Cache to get static site level performance and stop worrying about complex layers of third-party cruft. If you're worried about 'marketing interns' messing with the site, don't give them 'Administrator' roles!
Re: The complicated futility of WordPress
#174Earlier quoted context omitted.
> The issue is that if you’re developing like this on WP you don’t gain much from it except the ability to use a select few plugins and an admin UI. At this point why not use a solid PHP framework like Laravel? Agreed, if you have a dedicated engineering team, but most non-tech companies that need basic websites don't...so in that context, Wordpress's admin UI is a big gain. It's familiar to users and provides media…
I can tell you that new users like Gutenberg. It is us, the old shortcode style users, that have/had a problem with it. It took me some time to switch to it but I must say that I like it now. Things like copy/paste from Google docs with keeping all of relevant the styles and links works. And I guess that a bunch of users is doing that - using WP as a platform for distribution of content.
Having a classic editor plugin has nothing to do with characterizing people as crufty throwbacks who can't learn new things. Many people are in the business of their business and don't care to learn the next new-greatest-software every few months.
Re: The complicated futility of WordPress
#175It works, and I appreciate that it’s free but I’ve always hated working with it.
If someone made a node based equivalent (so I can at least use a modern templating language) that supported comments I would be all over it.
The commenting system is the only real reason I stay. There’s nothing else I can find that doesn’t necessitate stitching multiple services together just to get commenting that I can find.
And as for being able to spin up a local dev version for casual edits — horrid DX! I wonder whether a big reason social media has stolen our online interactions over the years is because there are few (no?) blogging platforms that support comments?!
Re: The complicated futility of WordPress
#176Earlier quoted context omitted.
I don't agree. I'm exactly in the position of the author with my clients. The real problem is with the Wordpress makes your client think it can outsmart you. I don't care about billing random hours to fix a footer. If anything, I program all my sites so that global options like these are ALWAYS easily editable by the customer. That's not my business model. It's just frustrating when the user wipes an entire section,…
> It's just frustrating when the user wipes an entire section, because they decided that "oh, I can change that font here". My clients fuck up their WordPress websites all the time. Revisions and incremental backups solve that issue. Nothing we can do to stop an adventurous website owner on a Friday night after 2 glasses of wine. Thankfully most of my clients stick to what they do best: run their business and leave t…
Re: The complicated futility of WordPress
#177Earlier quoted context omitted.
I love WordPress. It is kind of a universal tool: you can make simple web sites, you can use it to build complex systems. It is always better if you have developers that know what they are doing. WP development is not installing dozens od plugins to achieve some effect on your web. I guess that WP wants to become "one to rule them all". This means that they strive for even bigger adoption rate among users. FSE is the…
The issue is that if you’re developing like this on WP you don’t gain much from it except the ability to use a select few plugins and an admin UI. At this point why not use a solid PHP framework like Laravel?
The designer can, within the structure and strictures of Wordpress, build a site with all the whizzy things the client wants, and they can charge $X for it. A developer can do all of that as well, but they will probably need a designer as well (see above parenthetical), and it will cost $X * 2.
The counter to that is, "well, just build a good templating system and tweak that for other clients, and you're good." Which is true, and that's why there are lone PHP developers out there who make a decent living with a stable of clients.
One of the worst aspects of Wordpress is dealing with the infuriating and opaque reasons why a particular site is slow. A relatively simple site can be maddeningly slow for any number of reasons, and finding them is like searching for a contact lens in a full bathtub.
Re: The complicated futility of WordPress
#178I've been working with WordPress for a long time and have run a blogging network built on Wordpress since 2005-ish. Over the last few years, it's felt like I've been swimming upstream fighting against WordPress as they have tried to morph into a general website publishing tool (in order to compete with Wix, SquareSpace, etc) rather than their initial blogging roots. Security has never been a WordPress strong point an…
I love WordPress. It is kind of a universal tool: you can make simple web sites, you can use it to build complex systems. It is always better if you have developers that know what they are doing. WP development is not installing dozens od plugins to achieve some effect on your web. I guess that WP wants to become "one to rule them all". This means that they strive for even bigger adoption rate among users. FSE is the…
Here's a question: suppose that you want to use WordPress as a starting point for a CRUD app with some basic permission controls, the ability to dynamically add content and maybe even write your own search logic which respects those permissions.
Example:
1. Upon opening your site, you'll be presented with a list of Foos
2. Each Foo will have a description, a configurable amount of maximum Bars, and a summary of how many Bar instances have already been added, as well a location on a map below the list (a pin, think Leaflet.js)
3. Upon logging in to the site, you'll be able to open each Foo and see all of the Bars under it
4. In this list you can click on a Bar to open its view, which shows all of the data added it: typical stuff like text, numbers, dates, times etc.
5. With the appropriate permissions, you can either edit the Foos/Bars that you have access to, or edit all of them as an admin. As a user, you can only view them.
(just an example that i made up, vaguely like a CRUD that i created in PHP with one of the regular web development frameworks)How would you go about that? Are there any resources that you would recommend?
For example, if one were to use Slim, they'd look at their documentation: https://www.slimframework.com/docs/v3/
Similarly, Laravel has pretty decent documentation for developers: https://laravel.com/docs/8.x
Whereas with WordPress, i don't think that there is such an informative, guided resource for implementing things like that: https://wordpress.org/support/
A lot of it seems to focus on how to maintain installs of WordPress or how to work with its built in concepts (like pages/posts/etc.), but there's nothing along the lines: "Here's how you're supported to mess around with its internals in an idiomatic way and introduce custom views, validations, persist the data in the DB and add whatever you need to cover what constitutes a business process". Maybe i haven't dug inside of it enough.
Are you just supposed to hack things together with a custom theme or custom widgets, custom post types and storing most of the information into custom fields that are attached to the post? Why does the documentation have such a lack of PHP in it, then? Is there a separate set of developer docs somewhere?
Actually, i wonder if there's some super lightweight boilerplate theme, that attempts to do almost no styling and has very basic layouts, to be used as a boilerplace, e.g. what the likes of Skeleton are for CSS: http://getskeleton.com/
Re: The complicated futility of WordPress
#179However so much of what this author says resonates more than I care to admit. I have a good relationship with WP but I worry about the future.
Re: The complicated futility of WordPress
#180I hope more people stop building bespoke websites and start building tools for regular people to just make things. It's 2021. It should not be this hard for a regular person to update a website. If you can make a powerpoint presentation with MS PowerPoint, why can't you make a website that way?