Displaying 1 To 24 Of 24 Comments This feature is still a work in progress. ;) » Posted By Viper007Bond On April 27, 2010 @ 8:26 PM Interview With Beau Lebens Talking BackPress BackPress is awesome. When I write a non-WordPress script, I find myself missing all of the helper functions that WordPress provides. BackPress allows you to have that framework without having to make your script entirely WordPress-powered (which is often overkill when writing a simple otherwise non-WordPress script). » Posted By Viper007Bond On April 16, 2010 @ 7:17 PM Who’s Right? Network Solutions Or Matt @Chris Olbekson – I don’t think it’s WordPress’ job to make sure your host knows what they are doing and are running a secure environment. » Posted By Viper007Bond On April 14, 2010 @ 7:15 PM Even if I chmod my wp-config.php file to 777 (basically the loosest/most insecure permissions possible), in a properly configured environment you shouldn’t be able to access the file even if we’re on the same shared webserver. » Posted By Viper007Bond On April 13, 2010 @ 10:31 PM Senior Front End WordPress Developer Wanted @Ionut Staicu – Creating a theme (which is front-end work) requires knowing PHP and the kinda stuff these big companies create are usually significantly more complicated that the kind of themes you’ll find available for download on WordPress.org. ;) » Posted By Viper007Bond On April 2, 2010 @ 5:25 PM @Saad Bassi – Better is personal opinion. Unless Jeff has memcache, xcache, etc. then WP-Super-Cache is just fine. » Posted By Viper007Bond On March 20, 2010 @ 7:47 PM WPTavern Was Trackbacked To Death @Jeffro – They’re actually fairly easy to install and come with great instructions. :) When someone hits any page on your blog right now, PHP generates the page and gets data from the database. Both of those actions use CPU power. Both caching plugins short-circuit that and instead serve a previously generated version of that page (which uses significantly less CPU). Two guests to your site will see the same content, so the plugin just generates the page for one and serves it to the second without using the CPU power needed to generate the page. New comments and such automatically invalidate the cache files, so it’s basically install and forget. » Posted By Viper007Bond On March 10, 2010 @ 3:29 PM http://wordpress.org/extend/plugins/disable-trackbacks/ Also a caching plugin would have helped GREATLY in this case. Try WP-Super-Cache or W3 Total Cache. I use both (on different blogs) and each has it’s advantages (currently I prefer W3 as I’m using memcache and WP-Super-Cache’s memcache support is still in beta). » Posted By Viper007Bond On March 10, 2010 @ 3:18 PM Donate To Plugin Developers Day – March 1st @Oliver Schlöbe – You’d hear no complaints from me. :) » Posted By Viper007Bond On February 23, 2010 @ 4:43 AM There’s already a day for this. It’s January 28th. ;) http://wordpress.org/development/2009/01/thank-a-plugin-developer-day/ » Posted By Viper007Bond On February 22, 2010 @ 7:31 PM WordPress Dev Chat For 1-07-10 If you don’t have an IRC client: http://pjirc.viper007bond.com/?chan=wordpress-dev&network=chat.freenode.net » Posted By Viper007Bond On January 7, 2010 @ 10:22 PM Canonical, Core, Something Plugins @Devin – I can’t wait. It’ll cut down on the pointless forks or authors not accepting patches, abandoned popular plugins (see Podpress), etc. » Posted By Viper007Bond On December 18, 2009 @ 5:07 PM WordPress Dev Chat For 10-22-09 Viper007Bond who is the guy behind the new oEmbed feature in WordPress 2.9 suggested that there be a way to add support for some more sites out of the box that don’t support oembed. Erm, no I didn’t. :) I was asking for a bit of a brainstorm of what the popular video sites were so that they could be supported natively by WordPress. Someone else suggested a UI (rather than the existing function call) for being able to add more whitelisted oEmbed providers so non-admins could use them. Completely separate things. » Posted By Viper007Bond On October 24, 2009 @ 4:32 PM I definitely get where sivel is coming from. I only survive because I basically ignore most of my plugins, especially the unpopular ones. Even then though… » Posted By Viper007Bond On September 29, 2009 @ 10:10 PM WordPress Dev Chat For 9-17-09 The embed code is sound, it’s just that it basically adds a feature that could potentially be used to inject bad HTML into a blog (as the embed HTML can be fetched off a remote server). Security enforcement techniques will need to be come up with to make it as secure as possible. The idea is though that you can post say a YouTube URL on it’s own line and it’ll automatically be replaced with an embed. » Posted By Viper007Bond On September 18, 2009 @ 7:13 PM Supported Legacy Branches For WordPress.org? WordPress is a community driven project. If you want a feature, write it. The same goes for this — if someone wants a legacy branch, then they should step up and volunteer to port patches to their older version of WordPress. I think it’s being selfish and asking to much to expect that the already busy core devs maintain multiple versions of WordPress. @Dougal Campbell – I don’t see the need for more people with commit access rather than having them just submit patches and poking a committer for them to commit it. » Posted By Viper007Bond On September 23, 2009 @ 5:41 PM Who’s Responsible For Keeping Your WordPress Site Up To Date? If you choose to host your own blog, then you are choosing to have to keep it up to date. If you don’t want the responsibility, then don’t host your own blog. There are plenty of alternatives. Simple as that. » Posted By Viper007Bond On September 16, 2009 @ 2:48 AM @Elpie – There shouldn’t be a reason to need to modify your core files, so what does it matter what files changed? And your comment is wrong as well. WordPress is developed using SVN, so it’s incredibly easy to track changes. For example, here is every single change between v2.8.3 and v2.8.4: http://v007.me/wp284diff » Posted By Viper007Bond On September 7, 2009 @ 12:42 AM If you aren’t capable of keeping your blog software up to date, for whatever reason, then you shouldn’t be running your own blog. Use WordPress.com instead. » Posted By Viper007Bond On September 7, 2009 @ 12:12 AM Roll Your Own URL Shortener With Pretty Link Why in the world would you pay for something like this when there’s the insanely awesome YOURLS? It’s free, written by two well known WordPress plugin developers (Ozh and GamerZ), and doesn’t even require WordPress (although of course there’s a WP plugin to auto-shorten and even auto-tweet new posts or pages). You can run it on your existing domain (in a subfolder or whatnot) or buy a cheap short domain. I’m paying $10/yr for v007.me. :) Here’s a screenshot of the WordPress plugin at work on the write screen, and also an example of the thing in work (I used a custom stub, but if left it at the currently single character default, my URLs are currently shorter than bit.ly URLs and will be for quite a few hundred or thousand posts): http://v007.me/yourlsimg » Posted By Viper007Bond On August 19, 2009 @ 6:22 PM Do You Think The Codex Is The Future Of Documentation For WordPress? Wiki’s are by far the best solution for handling documentation. The Codex just needs some work, that’s all. » Posted By Viper007Bond On August 14, 2009 @ 5:05 PM WordPress.com Testing A New Look @Edward Caissie – The one that was included in WPMU for a while was a slight modification of my plugin which is based on the old WordPress.com admin bar look (completely original code though). » Posted By Viper007Bond On August 12, 2009 @ 4:38 PM Top 5 WordPress Security Tips You Most Likely Don’t Follow @Phil – It’s just security through obscurity, i.e. not real security when you get down to it. #3 is also semi-invalid as the hacker could just use the variable to get the prefix. #1, #4, and #5 are great though. :) » Posted By Viper007Bond On August 9, 2009 @ 11:19 PM WordPress Tattoo Using The Wrong Logo? You have way too much time on your hands, Jeff. LOL » Posted By Viper007Bond On February 10, 2009 @ 4:41 AMComments Posted By Viper007Bond
«« Back To Stats Page