11–20 of 175 posts
> WordPress is a content management system, and the content is sacred. Every change you make to every page, every post, is tracked in a revision system I'm not sure I see how the absence of a revision tracking system rises to a violation of sacred principles.
You can also just turn it on by emailing support...
I mean, yeah. Isn't that what they're supposed to be doing? Because an option exists to store every revision doesn't mean you necessarily have to do it for free. It is a costly feature. They're free to chop up WordPress as much as they like and monetize features that elsewhere are default. They're not hiding it and users can choose to go elsewhere. Otherwise every WordPress host would be the same, just hosting vanill…
> while the WordPress people may not like it hmm i wonder why... https://wordpress.com/wordpress-hosting/ always great to see devs sh1t on other devs under the premise of "this isn't right!!!" when in reality it's just affecting their bottom line. money makes the world go round!
> WordPress is a content management system, and the content is sacred. Every change you make to every page, every post, is tracked in a revision system I'm not sure I see how the absence of a revision tracking system rises to a violation of sacred principles.
I mean, yeah. Isn't that what they're supposed to be doing? Because an option exists to store every revision doesn't mean you necessarily have to do it for free. It is a costly feature. They're free to chop up WordPress as much as they like and monetize features that elsewhere are default. They're not hiding it and users can choose to go elsewhere. Otherwise every WordPress host would be the same, just hosting vanill…
You can chop up WordPress, because it's open source. But you cant chop it up and keep calling it the same thing. Only the vanilla WordPress gets to be called WordPress... because the project called WordPress has decided that the release they put out is what they want to attach their name to. Someone cant come along later, make a bunch of changes, and then attach someone elses name to it.. and then go around insisting…
define('WP_POST_REVISIONS', 0);
That's it.
That being said, some commercial users of open-source software need to be better contributors to the eco-system and not just vampires.
Over the years, I've watched them through a progression of management changes move from value of service to value extraction. Chipping away at costs while holding the price constant or raising it and extracting the difference for themselves. This isn't in and of itself a "bad" thing, it is what business does, however I find the integrity around value extraction varies tremendously. From zero integrity Mackenzie type MBAs to high(er) integrity owner operators.
It is rare when a management team says, "this is enough money" and that is sad.
Earlier quoted context omitted.
You can chop up WordPress, because it's open source. But you cant chop it up and keep calling it the same thing. Only the vanilla WordPress gets to be called WordPress... because the project called WordPress has decided that the release they put out is what they want to attach their name to. Someone cant come along later, make a bunch of changes, and then attach someone elses name to it.. and then go around insisting…
WordPress makes those features disable-able themselves , nobody has "chopped up" anything here. define('WP_POST_REVISIONS', 0); That's it.
Disabling a feature isnt chopping anything up. Im specifically commenting on this statement you made.
Earlier quoted context omitted.
WordPress makes those features disable-able themselves , nobody has "chopped up" anything here. define('WP_POST_REVISIONS', 0); That's it.
They're free to chop up WordPress as much as they like Disabling a feature isnt chopping anything up. Im specifically commenting on this statement you made.
> What WP Engine gives you is not WordPress, it’s something that they’ve chopped up, hacked, butchered to look like WordPress, but actually they’re giving you a cheap knock-off and charging you more for it.