[wp-hackers] Two new, long-overdue plugins to make your wordpress life a little easier...
Dagan.Henderson at epyllion.com
Mon Oct 31 14:20:40 UTC 2011
Wow, this debate is still raging, huh?
I've seen a handful of graceful, automatable suggestions for creating dev-staging-production solutions, and still "team-enterprise" is pushing for inclusion in core. What, exactly, is wrong with a plugin? It's precise definition (a set of software components that adds specific capabilities to a larger software application) is a perfect fit for this case.
Consider the enterprise must-have plugins that already exists:
-Domain Mapping (http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/)
-Bad Behavior (http://wordpress.org/extend/plugins/bad-behavior/)
-WordPress SEO (http://wordpress.org/extend/plugins/wordpress-seo/)
IMHO, it makes far more sense to develop use-case-specific plugins than to offer a few "common" choices in core. Since there are at least a few pro-root-relative hackers in the conversation right now, why don't you folks band together to help support and extend Marcus' plugin?
From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Robert Lusby
Sent: Monday, October 31, 2011 3:15 AM
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] Two new, long-overdue plugins to make your wordpress life a little easier...
On 31/10/2011 09:46, Mike Little wrote:
> WordPress is a user's tool first and foremost. I agree with that and
> it should not change. Mike
Bold statement Mike.
On 28/10/2011 19:46, Otto wrote:
> No, but that's not the same thing at all. A dev/staging/production
> environment is something used by a company to create a continual
> development process. It's not the same as a demo or test site that you
> would be showing clients. You're mixing ideas here.
So Otto - you cleary have no concept of heavy enterprise development.
Here's the process:
- Account owner / client asks for new section of website, or changes to current website
- DEV team (either in-house, or often in Enterprise, outsourced to a development agency) make said changes.
- Account owner / client will then need to review the change and approve it ready to go live (this person is very often non-technical, and in an Enterprise environment, so you can't start asking HOST file changes or DNS changes)
- DEV team then make said change live
- Account owner then approves change is live.
- Job is closed.
Sometimes we need to do this with time-delays etc ... when launching a specific product for a client, with new features etc ...
Can the list confirm two things then please?
1) WordPress is not looking to improve on Enterprise support as it's too small a use case? If so we'll start looking at more "grown-up" platforms for our clients.
2) If WordPress is so concerned about the DB content being "excatly"
what you entered, why is there a filter that changes my Wordpress to WordPress (even in URLs that can be case-sensitive)?
wp-hackers mailing list
wp-hackers at lists.automattic.com
More information about the wp-hackers