Displaying 1 To 21 Of 21 Comments Review Of WhiteHousePro3 By PageLines It’s also worth mentioning that there is a free version of this theme available at the WordPress theme repository but the pro version does not have the breadth of features as the free version. Another thing the Pro version has the free version does not is a wide range of page templates. I think that should read: It’s also worth mentioning that there is a free version of this theme available at the WordPress theme repository but the free version does not have the breadth of features as the pro version. Another thing the Pro version has that the free version does not is a wide range of page templates. » Posted By Ryan McCue On June 2, 2010 @ 7:32 AM WordPress RSS Parser SimplePie Ceases Development If I can make it to one, yes. :P » Posted By Ryan McCue On September 29, 2009 @ 12:16 AM Worth mentioning, I’m planning on maintaining a bugfix fork of SP as one of the (ex?) developers. » Posted By Ryan McCue On September 28, 2009 @ 10:38 PM The Lowdown On WPCoop With Jayson Cote Just FYI, you should remove the _mcePaste div completely, not just hide it. Also, if you want to hide it, just put display: none;, so it doesn’t mess up my feed reader. :) » Posted By Ryan McCue On September 24, 2009 @ 10:01 PM Top 5 WordPress Security Tips You Most Likely Don’t Follow @Josh -That’s because code is filtered out by kses by default (I think). There are plugins to change this, I do believe. » Posted By Ryan McCue On September 7, 2009 @ 3:03 AM #1 and #3 are simply security via obscurity, which is no security at all. #1 can easily be worked around if you remove or change the default username. A much better idea is to only use the admin account for actual administrating, and use a different account for everything else. Grant it the permission to do everything but change settings (Editor, I think). #2 is somewhat valid however, because if for some reason PHP was temporarily disabled, wp-config.php could be read if in your web-accessible directory. Otherwise, it’s also security through obscurity. » Posted By Ryan McCue On August 10, 2009 @ 2:31 AM It was the issue that 2.8.1 addressed, not 2.8.2. :D » Posted By Ryan McCue On August 4, 2009 @ 8:09 AM Do I Need To Upgrade WordPress.com? Erm, it would be nice if you answered it to let those who Google that know. :) » Posted By Ryan McCue On July 27, 2009 @ 7:26 AM Listener Poll: Do You Think bbPress Will Evolve Into A WordPress Plugin? @Jeffro – The difference is that WordPress and WP MU are both almost the same. They’re both blogging software. bbPress, however, is forum software. Personally, I like having it separate. One must remember though, bbPress was designed for the WP support forums. It’s not designed to be everything to everyone, and it’s not designed to be a simple, plug-in solution. » Posted By Ryan McCue On July 19, 2009 @ 2:32 AM They’re two different types of software, aimed towards two different types of people. » Posted By Ryan McCue On July 18, 2009 @ 3:56 AM TalkPress bbPress Domain Dilemma This is completely irrelevant. Sure, non-internet-savvy people may just go to bbpress.com, but as you mentioned, anyone who has the faintest knowledge of the ‘net will google it at least. If you simply type “bbpress.com” into a browser in hopes of finding it, then you’re almost definitely not going to own a server to run bbPress on anyway. If bbPress was aimed at beginners, I’d agree, but it’s not; it’s aimed at site administrators. » Posted By Ryan McCue On May 28, 2009 @ 7:09 AM Matt Takes Notice Of Gorilla Project I’ll pass on to Jeremie and Chris about this (I’m working on the backend with Chris). » Posted By Ryan McCue On April 28, 2009 @ 3:37 AM It is Lyceum, as Lyceum’s database structure is normalised, while WordPress MU’s is sharded. » Posted By Ryan McCue On April 7, 2009 @ 12:13 AM Since When Has Matt Been Right Anyway Hehehe, sucker. :D » Posted By Ryan McCue On March 31, 2009 @ 2:26 AM Core Plugins? Never Gonna Happen! Pretty much everyone on the list (myself included) disagrees with what Mike is proposing. I very much doubt myself that any new core plugins will be made and included with WP. Automattic has many useful plugins themselves, but they are not included with core, because they aren’t of use to a significant majority of users. Features should never be moved from the core into “core plugins”, but rather into normal plugins hosted on the WordPress.org Plugin Repository. @Chip Bennett – You’re mistaken in saying that Hello Dolly is a waste of resources and that it is installed by default. If you’re concerned about a 2.17kb file, then you really need a better host. Additionally, it acts as an example file to developers on how to develop plugins. » Posted By Ryan McCue On February 5, 2009 @ 1:50 AM What WordPress Needs From Its New Community Leader @Jeffro – You? Leader? When did this happen? :P Great writing though, and couldn’t agree more with the content too. » Posted By Ryan McCue On January 27, 2009 @ 4:57 AM WordPress Needs To Revise Post Revisions @Jeffro – Controlling post revisions isn’t something most people will want. Remember that while you may not be a programmer, you are still a power user of WordPress and most users will not care about the size. People I’ve helped in the #wordpress chatroom are grateful for the fact that they can revert to a previous version and that it’s built in. But, I will have to agree to disagree on this one. :) @Andrew – If your host has arbitrary limits on database size, you should be looking for a new host. Most hosts limit the number of databases you get, but never the size of the databases themselves. » Posted By Ryan McCue On January 23, 2009 @ 7:29 PM @Jeffro – It’s a single line to copy and paste. Nothing can go wrong. Most users that will want to disable this will be the ones who know about their database. Most users set their database up and forget about it, without caring how big it gets. Only those who have some knowledge of WordPress will care about it at all. On the other hand, look at it from an interface perspective: more options in the UI creates more clutter. Having an option for every single thing in the options would expand them greatly, at little to no benefit. There are tonnes of hidden options available at the moment which most users don’t know about, because they don’t need them. In case you’re wondering about whether clutter in the options matters, take a look at this wonderful essay by Joel Spolsky. » Posted By Ryan McCue On January 23, 2009 @ 7:08 PM @Andrew – The thing is, you can disable it. I’ve just confirmed by looking at the source code that you can add @Jeffro – I checked the source code of WP and inserting that define should disable them completely. Make sure that it’s before wp-settings is included. If you’re still having problems, hit me up via IM or IRC and I’ll check it out. (Also, CommentLuv should remember me unticking it. It’s a pain to have to untick it every time.) » Posted By Ryan McCue On January 23, 2009 @ 6:59 PM @Jeffro – You’re writing Trac in uppercase, as if it is an acronym. It should be called “Trac”, with a single upper case “T” to begin the word (it is a proper noun), followed by lowercase letters. It is not “TRAC”. With regards to that actual ticket, it was closed because it was possible to add a define to wp-config.php, not to remove the option entirely. » Posted By Ryan McCue On January 23, 2009 @ 6:53 PM Trac is not an acronym :) Also, link to the Trac bug. There should be comments on why it was marked as “won’t fix”, which I’m sure are valid. » Posted By Ryan McCue On January 23, 2009 @ 6:39 PMComments Posted By Ryan McCue
define('WP_POST_REVISIONS', false); and it will disable them entirely.
«« Back To Stats Page