It has been confirmed, I will be speaking at WordCamp Minneapolis on November 13th, 2010. My presentation is titled How-to: Reporting Issues. I will be covering troubleshooting techniques, determining if an issue is a bug, and best practices for reporting bugs. This includes a quick primer on using the WordPress Trac. You will find this presentation in the beginner track, though it can be a good refresher for more advanced users that are not used to dealing with troubleshooting.
By the way, you may want to watch the WordCamp Minneapolis website for an announcement around October 4th. Yes, I already know what it is (it involves a change in venue, you didn’t hear this from me, capisce?).
No, the webhost did not change, I finally shelled out some cash for a domain name of my own. This in preparation of some future projects, and WordCamp MSP in November. More details on the projects will come later. In the mean time, feel free to start updating your links. Note that mtekk.weblogs.us will still link to the same blog for as long as it is hosted on weblogs.us (I do not have any intention of switching hosts any time soon).
As of July 1st, 2010, Mtekk’s Testimonials and Iframe-B-Gone will reach EOL. The last time either of these plugins were updated was back in 2008. Since that time, much has changed and equivalent plugins have been released by other authors.
In the case of Iframe-B-Gone, the WordPress Exploit Scanner by Donncha O Caoimh is a all around better solution. It has more features, and does just about everything Iframe-B-Gone does, minus attempting to autofix issues—a stupidly dangerous thing to do, by the way.
As for Mtekk’s Testimonials, it needs a substantial overhaul with the advent of custom posts. There is also the problem that it uses mootools while just about everything else in WordPress uses jQuery. At the moment I am not interested in rewriting this plugin. In the future, if the need arises, this plugin may get rewritten, but I doubt it will be this year.
Both of these plugins will remain available into the foreseeable future. However, I will no longer support them after July 1st, 2010. All of the plugins about to be EOLed have been moved to the “Historical” subpage of “Code”, and will have their comments closed on their EOL date.
That’s correct, there will be a WordCamp in Minnesota this year. It will be held on November 13th, at the Egan Community Center. Mark your calendars as this will be an exciting and busy, day-long event for users and developers of all skill levels. Additional information will be made available in the coming months.
Oh, and I will be speaking at this event. More information regarding this, including the topic will be announced this summer.
This really has not been a problem in the past, but one feels compelled to spell this out due to the actions of a few commenters in the past month or so. On this site, one reserves the right to delete or modify any comment deemed unacceptable. Modifications may include, but are not limited to:
Removal of offensive language
Removal of information that may compromise the security of the commenter’s web server
Removal of excessive links
When selecting a name, please use either your real name (e.g. John, John Doe, John D., or J. Doe) or an appropriate pseudonym (e.g. miller). Do not use overly generic names, or names that look to be SEO baiting in nature (e.g. friend, buddy, Plugin Developer, WordPress Experts, etc.). Do not impersonate the admin, or any registered users (e.g. admin, mtekk, John Havlik). Failure to adhere to these guidelines will result in your name being changed (if one values the content of your comment) or your comment being deleted.
Although this site’s primary audience is over 18, please keep your comments suitable for work. One does not need this site to be blacklisted by the likes of Websense. Remember, anyone can read these comments, including current or future employers.
When posting errors presented by PHP, please reduce strings like “/var/www/sitename/htdocs/wp-contents/plugins/breadcrumb-navxt/breadcrumb_navxt_class.php” to “…/wp-contents/plugins/breadcrumb-navxt/breadcrumb_navxt_class.php”.
Unless the link pertains to the content of your comment, please leave it out.