Displaying 1 To 14 Of 14 Comments Should Automatic Upgrades Be Opt-In? There’s a lot to reply to here, so I’ll try to keep it as short as possible. To clearly state my position, I’m in favor of opt out. My reasoning is that the majority of installs should auto-upgrade, and also the sites that should NOT auto-upgrade are also the sites that tend to have a person running or developing them that is capable of adding something to wp-config to opt-out. Having said that, I think there’s excessive concern in some of the comments here. People seem to think this might happen soon. Otto said it perfectly: We’re a loooong way away from this being possible When it DOES happen we’ll do it right. However, it’s going to take time to figure out what “right” is. I see this as another “the media area needs updating” kind of issue. We know it needs to be done, but it needs to be done right and that means we need to take time to plan. I’m also a little confused as to why Matt got a personal call out here. As far as I can tell he’s not trying to force you to do anything. This kind of thing has been discussed by the developers on and off for quite some time. At some point when a good solution is envisioned a couple of developers will try to code it up. Then several more will tweak it until it seems functional. It will end up in core and several more developers will test it, break it, fix it, etc. Whenever this eventually happens there will be quite a few people that were part of it. Matt won’t have “forced” this feature in, he won’t have “forced” you to use it (there’s certainly going to be a way to opt-out), and honestly he doesn’t even “force” you to use WordPress! In the end, if you don’t want automatic upgrades then opt out. Those that need them most are the people that don’t know it, so for them it should be turned on by default. » Posted By Aaron D. Campbell On September 10, 2011 @ 4:18 PM WPWeekly Episode 94 – Commercial Themes Had to take the time to come and comment on this episode. It was really great hearing what these guys were doing in the premium theme market. Thanks for sharing. I’ll be honest though, I was surprised to not hear any promos codes thrown around! ;) » Posted By Aaron D. Campbell On April 6, 2010 @ 3:45 PM WPWeekly Episode 68 – Hey, I Didn’t Change My Password! I’m pretty sure his name is John Godley not John Gridley. » Posted By Aaron D. Campbell On August 18, 2009 @ 10:05 AM WPWeekly Episode 67 – Everywhere You Look There’s A WordPress Book They have servers with both Layered Tech and Peer 1, but I don’t know if WordPress.com serves from any of the Peer1 servers. Also, Barry (their systems guy) used to work for Rackspace, which means he’s now had experience with all the top names in high-end hosting. » Posted By Aaron D. Campbell On August 13, 2009 @ 5:18 PM Listener Poll: What Day Of The Week Should I Record WordPress Weekly? I’m with Spamboy. I voted Thursday, but in reality I’m just saying “Any day but Friday”. The problem is that 8pm Eastern is 5pm Pacific…I would listen live, but really who wants to be doing ANYTHING at 5pm Friday? » Posted By Aaron D. Campbell On August 3, 2009 @ 3:54 PM Listener Poll: What’s the most important selling point for you when it comes to purchasing a theme? First, while you can’t see the PHP, you can see all the (X)HTML and CSS which can give you a pretty good idea for how well coded the theme is. Additionally, some places let you download and use the theme, only paying for support (such as Theme Hybrid). Lastly, you can tell based on reputation or other projects. For example, I know that Studio Press has quality code in their themes because programmers that I know have said so. Additionally, I know that Joost has been inside their themes to work on the code and I know he produces solid code (because I’ve seen it elsewhere such as his plugins). » Posted By Aaron D. Campbell On July 29, 2009 @ 11:19 AM Code Quality -> Support (and how reliable the company is, part of which is History/Longevity) -> Design -> Price -> License (all are at least GPL, which is good enough for me) » Posted By Aaron D. Campbell On July 26, 2009 @ 11:00 PM WPWeekly Episode 63 – Interview With Randy Hoyt And Scott Clark Regarding the Minimum Comment Length plugin by Joost, you can see on WordPress extend that it was last updated 7 months ago, before you had yours developed, and you can see on the plugins trac that it was first checked in 12 months ago in July 2008. » Posted By Aaron D. Campbell On July 13, 2009 @ 11:28 AM Listener Poll: Is WordPress A Community Run Project? I think you said it perfectly when you said that “it’s development is largely community driven.” It’s not community “run” but it is community “driven”. If the project were community run, you’d quickly face the “too many chiefs not enough Indians” dilemma, which causes the project to grind to a halt. If 1,000 people think they all have equal say on a matter, you unfortunately don’t end up with 600 wanting option A and 400 wanting option B. Instead you end up with options A, B, C, D, E, F, G, H, I, and J each with roughly 100 supporters. How do you handle that? Which option do you go with? The unfortunate answer is that usually none of them get done, even if 9 of the 10 options are horrible. » Posted By Aaron D. Campbell On July 11, 2009 @ 10:37 AM Listener Poll: Should there be a page on the plugin repository for Commercial GPL plugins? I know I was quite wordy in my last reply, so I’ll try to keep this one short: Whether it is needed or not, it’s only fair that plugin developers be treated equally I guess a good question would be: What’s the harm of creating a commercial plug-in page on wordpress.org? I agree. » Posted By Aaron D. Campbell On July 6, 2009 @ 3:19 PM Just to try to clear some things up: If you have the choice of developing a plugin and giving it away and putting it in a commercial repository who, in their right minds, would do the former? They are not talking about offering a commercial “repository” …just links to people that offer commercial support for their theme (and hopefully plugins eventually). I’d still give my plugins away because that lets them be in the wordpress.org repository (allowing for one click updates, update notices, etc). People selling their plugins cannot have them in the WordPress.org repository whether they’re GPL or not, because Matt has stated that he does not foresee there being any method to sell plugins or themes on WordPress.org in the future. The commercial theme repository was (I assume) created as the WordPress theme industry was deemed to be unacceptably biased towards non-GPL themes. However this does not seem to be the case with plugins. I don’t know of any popular non-GPL plugins but until recently I could rattle off the names of a whole stack of non-GPL themes, most of which were far better than their GPL counterparts. So no, I don’t see much point in a commercial GPL plugin repository. Again, this isn’t another repository. However, putting that slight difference aside, there are plenty of plugin developers that are wanting to start charging for support. I myself am one of them, and so it Joost (http://yoast.com/on-the-gpl-themes-plugins-free/). Joost has popular plugins like Sociable, Breadcrumbs, and Google Analytics for WordPress. I have things like Twitter Widget Pro. Neither of us wants to charge for our plugins, but we want to charge for support. The problem is that once a plugin gets popular, you start to get TONS of requests to work on it. People actually think they are entitled to have you fix a glitch or add a feature. The problem is, that takes a lot of time and nets you $0. If I were to fix every issue and add every feature that came as a request, my family would starve because I couldn’t do anything else. If I can charge something for support, I can better justify spending more time on them. I actually have plugins that I don’t want to release because I know that as soon as I do I’ll be getting a flood of support demands. Now, having said all that, I can do all that with the current plugins repository and without a commercial plugins page. However, it seems to me that plugin developers who offer commercial support for their plugins should get the same treatment as theme designers that offer commercial support for their themes. You can read more detail on my position at http://wpinformer.com/gpl-themes-love-plugins-suffer/ » Posted By Aaron D. Campbell On July 6, 2009 @ 1:15 PM @JLeuze - » Posted By Aaron D. Campbell On July 6, 2009 @ 5:14 PM I have this site white listed as well i Ad Block Plus. However, it looks like you DO allow flash ads as long as they are the right size for your ad spaces. I only say that because I’m interested in putting an ad up so I looked at your pricing and it says I can upload a gif, jpg, jpeg, png, or swf. I actually have a guy making a 125×125 swf to advertise http://xavisys.com right now. » Posted By Aaron D. Campbell On July 6, 2009 @ 4:37 PM WPInformer Launches – More WordPress Stuff Thanks for the writeup Jeffro. There will definitely be more to come on WordPress Informer, including a planned review of WordPress Weekly. For now your users may also be interested in the new How to Make Your Own WordPress Widget article which walks the user through creating an upcoming posts widget. The plugin itself was also released and can be found on my WordPress.org profile page. » Posted By Aaron D. Campbell On April 29, 2009 @ 11:26 AMComments Posted By Aaron D. Campbell
I thoroughly agree. I wouldn’t have chose flash if I thought it would be annoying to users. I just wanted to make sure they really were allowed before I paid to have one made (although I guess it’s already too late for that…it’s not made yet, but I already got him started on it so I’ll have to pay either way).
«« Back To Stats Page