Displaying 1 To 11 Of 11 Comments Buy My WordCamp Chicago Ticket Sorry to hear that you won’t be able to go. I was looking forward to chatting you up in person again. Are you going to OpenCa.mp? » Posted By Chris Jean On May 26, 2010 @ 12:37 PM WPTavern Was Trackbacked To Death I’m glad that you got the problem resolved. It’s definitely a crappy deal. This too makes me wonder if there could be a good solution for such a problem. Maybe a plugin could look for a massive influx of trackbacks and temporarily do the redirect trick to prevent site overload. I’ll mentally kick around the idea and see if I can come up with anything. The sad reality is that a solution today could easily be bypassed next week. » Posted By Chris Jean On March 10, 2010 @ 3:25 PM Special Backup Buddy Coupon For Tavern Readers @ kcristiano I’ve passed this on to Cory. Hopefully we’ll get it figured out soon. @ Fredelig Have you posted this on the support forum for BackupBuddy yet? Dustin and I are working on a new version which should address some of the issues people are experiencing on different server setups. Hopefully this update will fix your issue as well. » Posted By Chris Jean On March 8, 2010 @ 3:17 PM Should Themes Have Plugin Functionality Built-In? I was chatting with Jeff about this on Twitter, but I thought I’d add my thoughts here. As you become more familiar with the way WordPress works, you discover that there is very little real difference between plugins and themes. A plugin can easily take control over the rendering process, thus the plugin becomes a “theme”. Similarly, a theme can easily provide plugin-like functionality (and many do). So, the definition of what is a “plugin” or “theme” feature is very blurry. As a coder for iThemes, I try my best to not add features to a theme that is already very well supported by plugins. The reasoning for this is multi-fold: It reduces the complexity of the theme, thus reducing bugs and support needs. There’s no reason to rip off a plugin author’s work just to add a new bullet point to a theme’s feature list. It allows me to focus on creating new features rather than rebuilding features that have already been done and done well. » Posted By Chris Jean On February 9, 2010 @ 5:19 PM Review Of iThemes Builder Theme @ Elaine We just released a beta version of the Builder Style Manager plugin last week. It’s still a very early draft of the concept, but already many people are using it to modify their site’s style. You can see more details here: Builder Style Manager Beta Released » Posted By Chris Jean On February 8, 2010 @ 2:45 PM @ Nice I’m glad you’re excited about Builder. Know that the current version does not include a style editor of any kind, so as far as style goes, it’s similar to Flexx. As noted in my original comment, we are working on a back-end style editor and hope to have one done within a couple weeks or so (if everything goes according to plan), but it doesn’t exist currently. As for the YAML CSS flexible width, I haven’t looked at it, but I don’t think it would work since the width customization is offered in the back-end editor and is not modifiable via CSS (in order to prevent breaking the layout widths chosen on the back-end). I’ve kicked around the idea of being able to support fluid widths for a while, but it’s still just a very conceptual idea, and I don’t know if or when it would be implemented. » Posted By Chris Jean On January 15, 2010 @ 2:57 PM Thanks for the review Jeff. The response we’ve gotten since release has been great. Every day we get new ideas to expand Builder to even greater functionality and usability. The biggest request we have currently is a style editor. Today’s big release was to get the code base flexible enough to support the new features we plan to implement ASAP, the style editor included. We have six new child themes lined up for release over the next few days. There is a new feature that will be released either tomorrow or next week that many people have been asking for (it isn’t the style editor, but I think people will be excited about it). We’re getting ready to launch a wiki-based documentation site specifically for Builder. So the next week should be very exciting, and we plan to keep this pace of frequent feature releases going. For those that may not have heard about Builder before, the idea is to make it as easy as possible for the end user to take control of their site’s layout (without needing to code) while at the same time giving developers a wealth of expansion options to be able to create new styles/features and rapidly launch sites. » Posted By Chris Jean On January 7, 2010 @ 11:43 PM HookPress – Seems Like A Great Idea The concept sounds great, but the more I think of it, the less I find any actual use. Relying on the HTTP system for actions and filters also has some problems for security and stability of the website. My biggest problem may be that I just don’t have enough knowledge with the entire webhooks concept since I, a person who thinks that WordPress is great as a web application development framework, am having a hard time coming up with a valid use. » Posted By Chris Jean On August 31, 2009 @ 4:14 PM iThemes Responds To Speculation – All Is Well Thanks for commenting on this Jeff. I’ve been so focused on getting projects rolled out the past few weeks that I’ve turned off all distractions, including Tweetdeck. So I was very surprised and dismayed when Cory shared with me that rumors about the company were floating around. We’ve got some cool stuff coming up, and we can’t wait to share it with our customers. Now I need to bury myself in the work again so that I can get it ready. :) » Posted By Chris Jean On August 26, 2009 @ 11:55 AM @Ben Cook – IMHO, I would rather see frequent releases as soon as security exploits are found rather than only major releases or even infrequent releases when batches of problems have been fixed. I think the problem is that people are used to a different type of update schedule. One where known problems exist for weeks, months, or years even, and the developer does little or nothing to fix the problem. I don’t know why someone would see frequent security patches and think “scary” or “unstable”. They should think that when they see a lack of frequent security patches. I certainly don’t want the perception of security and stability from Joe Webmaster determining the release cycle of WordPress. It is important to remember that there isn’t such a thing as code without bugs. No amount of pouring over the code will catch everything. Even code launched into space on probes and satellites is often immediately found to have bugs. Thus, the best course of action is to be swift with patch releases when problems are found. Of course, it would be great if the software easily handled upgrades in order to make this update process relatively-simple and fast. Fortunately enough, that’s been taken care of as well. Note that I’m not claiming that the level of testing is sufficient. I’m merely stating that the fact that we are up to 2.8.4 doesn’t mean that the level of testing is not sufficient. » Posted By Chris Jean On August 12, 2009 @ 11:17 PM @Spamboy – You assume that everyone knew. When you read the code, everything looks good. Even when this problem was discussed on the Hackers list, some people didn’t see the problem when shown the code and the way to exploit the problem. Thus, no one noticed it, and it wasn’t readily recognizable by doing a basic review of the code. However, this is something that is so readily exploitable that people were already doing it to numerous sites, this one included. It would have been extremely careless of the WordPress devs to not issue an immediate fix. » Posted By Chris Jean On August 12, 2009 @ 7:40 AMComments Posted By Chris Jean
«« Back To Stats Page