Displaying 1 To 14 Of 14 Comments Andrew Nacin Intros WP_Theme Class For WP 3.4 Thanks for that, though despite the name of the class, this doesn’t really affect theme developers. get_themes() and get_theme() are both largely internal functions. Even plugins don’t use them very often. This will affect theme developers mainly by allowing us to build awesome goodies like multiple screenshots. » Posted By Andrew Nacin On February 29, 2012 @ 4:23 PM 500 Plugins To Possibly Be Purged From The Repository @Tim H. – There are a few people tasked to work on WordPress full time, but no one actually works for WordPress. (For example, I work for Audrey.) WordPress itself is built by hundreds of core contributors, many of whom do not make their living off WordPress, and the vast majority of whom do not work on WordPress core full time. What I’m getting at is, even under the widest definition — including people I interact with in the community, ranging from contributors, to forum volunteers, to users I might meet at a WordCamp — I have not heard of a Ted Clayton, I’m afraid. @SearchWPPlugins – Now, I talk a good game, but WordPress isn’t that large of an organization. Only a few people actively work on WP.org architecture. I’ve been following this thread, admittedly cringing at some statements, but making note of some ideas. We’ve toyed around with our search quite a bit over the past year — including tweaks to the underlying engine, how different fields are weighted, what fields are considered, and when to push better plugins up and old/abandoned plugins down (or off the list entirely). We have a huge list of possible improvements (small and large), and we’ve took swings at these ideas in core, too. I think sites like searchwpplugins.com is pretty cool. That kind of innovation is nice, to see what people want, or what filters could benefit users the most. I think an advanced search on WP.org would be a good addition at some point, but right now, we can probably spend more time improving individual plugin listings, plugin quality, and how we generate and display search results, and end up with more bang for the buck. At least right now. » Posted By Andrew Nacin On February 27, 2012 @ 10:29 PM Sigh. Explosive headlines aren’t typically necessary. Next time, send me an email, and I’ll give you a heads up that the core team is likely going to adjust the guidelines to allow for a wider variety of licenses; there just hasn’t been the chance to talk about it yet. (The discussion on the ticket really only started late last week, not 11 months ago, after some very valid concerns were raised by a few individuals.) I tried not to speak on their behalf on the ticket, but I don’t have much of a choice now given the spreading of FUD. » Posted By Andrew Nacin On February 23, 2012 @ 10:57 AM @Edward Caissie – Ah, yeah. It is implemented as part of the canonical API. Rewrite isn’t a good place for it, as we don’t want it to stop on existing posts or pages. Here’s the ticket. » Posted By Andrew Nacin On February 23, 2012 @ 9:04 AM This is already in WordPress 3.4. /login, /dashboard, and /admin will take you where you want to go, even if WordPress itself is installed in a subdirectory (such as wptavern.com and wptavern.com/wordpress/). » Posted By Andrew Nacin On February 22, 2012 @ 4:03 PM WordPress Ink Does Not Equal WordPress Cult @Kevinjohn Gallagher – Honest question, do you have a hobby? Are you passionate about it? Does that mean you belong to a cult? Because you’re framing people’s passions (either a hobby or work they love) in a terrible light, and I don’t think that’s fair. “the WordPress store that was built this year by WordPress Core Devs” – That is not an accurate statement, so I won’t address it beyond this. » Posted By Andrew Nacin On January 1, 2012 @ 5:35 PM Case Study On How WordPress Won The Crown @Kevinjohn Gallagher – I agree the “best in breed” comment is without merit, but most of the CMS requirements you listed here are covered by a number of high quality plugins (and that form of coverage is no different than how the Drupal or Joomla ecosystems work). 1. Document management — Check out Ben Balter’s Google Summer of Code project. It’s a fantastic piece of work. 2. Workflow management — See Edit Flow, already used in a number of newsrooms. It’s worth nothing that Document Revisions and Edit Flow interact with each other — have them both on the same site, and you can use the manage a workflow for your documents. It’s mighty clever. 6. ESI Caching / CDN ability — W3 Total Cache supports the gist here. 7. WYSIWYG editing — Despite the bad rap given to most WYSIWYG editors, MoxieCode’s TinyMCE is the best one out there. Core supports it out of the box of course, and plugins and themes are pushing its limits with the editor API and editor styles. 8. Single Sign-on — With what? There’s plugins to do this with social networks, specialized authentication systems, and the like, and building a plugin for a system that isn’t covered is easy. 9. Multi-side Admin — Ours is pretty good. Could be better. Have any ideas? 11. Access Management — Combine a plugin like Members with a plugin like Edit Flow, toss in some custom capability code, and you have yourself a pretty good base system. 13. Multi-lingual — This is definitely a sore spot. Most of the plugins that try to do this, do it really poorly. Not much different than the e-commerce offerings, currently. I certainly didn’t cover all of your points, and some of them have no corresponding WordPress solutions. Some of the plugins I mentioned are nascent. What we need is the demand to occur and the ecosystem to step it up. “If you build it, they will come” isn’t really a core philosophy. » Posted By Andrew Nacin On December 6, 2011 @ 7:16 AM Some Not Happy With Flyout Menus @Kevinjohn Gallagher – It’s a beta release. Typically, a few things are still broken in our initial betas: Internet Explorer, the blue color scheme, and right-to-left support. (PHP4 used to also be on this list.) We handle those as we go, and typically we’re supported by dedicated contributors who, for some reason, thoroughly enjoy one or more of these pain points. But again, that’s why we just call it a beta, and why there’s always a beta 2. » Posted By Andrew Nacin On October 17, 2011 @ 5:00 PM Great to hear, Jeff! » Posted By Andrew Nacin On June 8, 2011 @ 4:26 PM Narrowly Escaping WordPress 3.0.6 We’re going to avoid updating wp-content on update. The exception is if an update crosses a version that introduced a new default theme, it will be copied over. Initially, we’re not unbundling anything. (And keep in mind Akismet is already an external to plugins.svn.) The plan will be easy to implement and it’s going to be really effective. No more Akismet dances, and themes won’t get overridden in a core update. » Posted By Andrew Nacin On February 9, 2011 @ 7:46 PM The decision to forego a WordPress 3.0.6 came before the idea of hotfixing it via plugins. We’re not letting the solution change how we think about and define releases. Rather, it was very quickly decided that the bug was too much of an edge case. But, the plugin is a convenient way to offer the fix to the few who were affected. » Posted By Andrew Nacin On February 9, 2011 @ 7:23 PM Protecting WordPress Login Credentials From FireSheep @John Pratt – That’s actually not true either — One Time Login is pretty much useless against Firesheep. After that one login, you’ll have the same authentication cookies for the duration of the session. » Posted By Andrew Nacin On January 5, 2011 @ 11:08 PM Plugin Authors And The Activation Hook I provided a detailed follow-up that explains the rationale and decision-making process behind this, as there was some initial confusion. » Posted By Andrew Nacin On October 27, 2010 @ 7:13 PM @Sherry: Are you perhaps thinking of the Affero GPL? » Posted By Andrew Nacin On August 31, 2010 @ 4:20 PMComments Posted By Andrew Nacin
«« Back To Stats Page