Displaying 31 To 41 Of 41 Comments Interview With Ryan Imel Of CommentBits.com @Ryan: Love the work you’ve done with this project, and am contemplating getting the Lifetime pass, but have a question: You’ve included threaded comments, but do these packages include code to list trackbacks in a separate list from regular comments? I currently have my trackbacks listed below the actual comments in a section of their own, and I’d like to retain that capability. » Posted By Kim On July 9, 2009 @ 11:45 PM Have a safe trip and a great time! Will be checking out the chatbox and live video link tomorrow to see what’s happening up there. » Posted By Kim On June 5, 2009 @ 5:24 PM Michael nailed it. I go through this all the time with clients and other support forums that I provide support on. It can be extremely frustrating to play “20 questions” with someone when trying to provide answers to their problems. What should have taken only 2-3 responses ends up at 10+ (and several hours/days) before the real problem is found and a resolution provided. » Posted By Kim On May 9, 2009 @ 4:59 PM Vote For The New Header Design I don’t see anything wrong with the current header area in 2.7. I know that some people have complained about it with regards to making the side menu longer when they have certain menu sections open. There’s a plugin by Ozh that fixes that for them, and many have decided to use that instead. With regard to the contest entries, there isn’t one of them that interests me. The DR1: Fluency style, dark entry is leading at the moment with 457 votes, with the Current: keep the current style running second with 412 votes. Personally, I don’t care for the Fluency style at all, but I know that others do like it. However, rather than forcing the Fluency style on everyone, I feel it should continue to be a plugin that end users can install and activate on their own, if they so choose. You cannot please everyone, no matter what choice is made. There will always be people who will complain about one thing or another. My concern at this point is that WordPress changes the interface again, and risks the possibility of alienating yet another, possibly larger, group of users. » Posted By Kim On April 30, 2009 @ 12:02 AM @Nikko and @chris – I’ve got it working with WordPress 2.8.4. What exactly are the issues you are having with the WP Wiki plugin? Can you both provide more details? “Doesn’t work” and “killed it” aren’t enough for anyone to be able to help you troubleshoot the problems. » Posted By Kim On August 24, 2009 @ 9:41 AM Ohio WordPress Meetup April 23rd MapQuest puts it at 65 miles, just a little over an hour drive from here to Akron. Will add it to my calendar and see if I can make it up there for the first meeting. Might want to get it listed on upcoming.org so that more people know about it. » Posted By Kim On April 9, 2009 @ 9:47 AM Sounds cool! Any idea on how many people might be attending? » Posted By Kim On April 8, 2009 @ 8:23 PM Episode 44 – Interview With Brian Gardner Great show last night Jeff! Really enjoyed listening to Brian Gardner, and getting to talk with everyone during the after-show. It’s a shame that the streaming audio messed up – hopefully TalkShoe has gotten that issue taken care of. » Posted By Kim On March 7, 2009 @ 1:59 PM Fix For Filosofo Comment Preview Plugin Glad I was able to find the solution so you could use the Comment Preview plugin again. :) » Posted By Kim On February 1, 2009 @ 3:33 PM WordPress Needs To Revise Post Revisions @Andrew: The encoding for pages/feeds could be moved, but the rest of them need to stay in the UI. The whole purpose of this discussion (I thought) was to get the settings for the post revisions into the WP admin UI, to keep end-users from having to edit wp-config.php to set their preferences. The less often a user has to mess with wp-config.php, the better. WP has a lot of inexperienced users who could totally bork their blogs if they have to constantly edit the config file. For all users, it is just a pain to have to make those changes in the config file when the UI already exists to take care of them. Permalinks: This needs to stay in the UI. Troubleshooting an issue with someone’s blog may require setting the permalinks back to default and then reset them back. There are plugins (for example, WP Download Monitor) that require you to reset your permalinks after the plugin is upgraded. A user shouldn’t have to mess with the config file to do this. Timezone: For those of us who have DST, we would have to edit wp-config.php to change the timezone twice a year. Why move it, when we can already reset it via the UI? These are just a couple of items you mentioned, but there are reasons why each of them need to stay in the UI, since they are already there. The config file should be a “set it and forget it” once WP is installed. How about we work together to get the post revisions setting into the UI instead? » Posted By Kim On January 25, 2009 @ 8:30 AM I’ve seen this subject debated on the WP forum and on a few blogs at the time this feature was released. It’s a great feature for some situations, but most single-user blogs are rarely going to have the need for this feature. The first thing I do when prepping a wp-config.php file for a new WP install is to include the following beforehand: I turn them off completely, as I don’t want the headache of having to go back in and remove the old revisions from the database. PS/Jeff, seems you didn’t install the Filosofo Comments Preview plugin on this blog. Could that be installed on this one too? :) » Posted By Kim On January 24, 2009 @ 6:06 PMComments Posted By Kim
«« Back To Stats Page /** Change X to the number of post revisions you want WordPress to save to the database **/
define ('WP_POST_REVISIONS', false);