Archive for January, 2007

WordPress 2.1 MySQL Requirements

0

Ryan Boren posted about MySQL requirements in the upcoming WordPress 2.1 release. WordPress 2.1 will require MySQL 4.0, MySQL 4.1 won’t be required until WordPress 2.2 comes around. So, WordPress 2.1 will require at least MySQL 4.0 to function correctly. No more MySQL 3 people. If you’re still using MySQL 3, it’s far past time to upgrade.

MySQL AB discontinued support for MySQL 4.0 back in September, so it’s likely hosting companies will be upgrading to 4.1 within a year or so.

Also, WordPress 2.1 beta 3 is out, it’s running on this blog right now.


Xbox 360: Towel Trick Fixes 3 Red Lights

573

The “Towel Trick” is an interesting solution to the 3 red lights on the ring of light (ROL). Supposedly, a user experiencing the 3 red lights on the ROL completely wrapped his Xbox 360 in a towel, with the red lights on, and let the Xbox 360 sit for about 10 minutes. He then turned his system off, then on again, and his Xbox 360 booted without issue. He was able to play for about 3 hours before the 3 red lights came back.

Sounds like an unlikely fix, but who knows? Well, I know, because I tested lastnight. The “Towel Trick” is bunk, total crap. You’re more likely to set your Xbox 360 on fire by doing this rather than fixing it. The best advice still is to contact Microsoft support. You can call them toll-free at 1-800-4MY-XBOX. They have an excellent support department lined up there for the Xbox/Xbox 360.

UPDATE: Here’s a video of the Towel Trick on YouTube.

UPDATE 7/14/2011: Rob left some good points in his comment below. A number of people in the comments on this post have suggested putting your Xbox 360 in a microwave to fix the 3 red lights issue. I would advise against this for a number of reasons.

Rob presented a number of things users should consider prior to microwaving any electronic device:

  1. 95% of all hardware failures are caused by very slight board
    warpage right under the G.P.U. where heat build up
    occurs . this will literally cause the Chips connections to pull
    away form the board.
  2. A standered refolw @ 255c will almost always get your console
    working.
  3. Specific Microwaves frequency acts on water molecules causing
    them to resonate ( absorb the energy) and then release it as heat
  4. you have a better chance of repairing using a heat gun or
    removing the xclamp and replacing it with screws and then
    force the G.P.U. only to over heat ( standered x clamp mod )
  5. Microwaves will cause metal objects to build up charges
    normally at or on sharp edges until it discharges causing sparks
    kina cool looking , try a Christmas ornaments.
  6. If you decide to stick you game console in your mw oven the ods are not in your
    favor and after the attempt fails your chances of a correct repair
    procedure are lost.
  7. Just use some common sense and realize if this had a high successes rate
    every one would be doing it . in fact people would be modified
    micro wave oven for that purpose only and they would be fixing consoles
    In volumes.

WordPress 2.1 Beta 2

5

I decided to make the early upgrade to WordPress 2.1. I just pulled down the latest version of beta 2 via subversion. Pretty much everything is working great so far. Out of all the plugins I use, only the Flickr RSS plugin caused problems. It refused to load anything, preventing anything below it to load. So, I promptly disabled it and everything was totally normal. I may dig into it later on tonight.

Also, I’m pleased to say that Unwakeable 1.2 works nicely with WordPress 2.1 beta 2.

I’m not gonna go into details on the changes in WordPress 2.1. Lorelle has already taken the time to put together a nice list of features we’ll see in WordPress 2.1. All thanks to Ryan Boren for blogging up a storm on what will be found in WordPress 2.1.

I’d like to thank all the WordPress developers for all their hard work. As usual, it’s very apparent the WordPress developers have put a great amount of work in WordPress 2.1. I’m really looking forward to the release of 2.1, Beta 2 has been great so far.


Mediacom Loses Sinclair Stations

9

Well, Sinclair Broadcast Group stations (at least here in Iowa) are no longer being carried by Mediacom. KCCI (cbs affiliate) had cameras outside a Mediacom office in Des Moines over the weekend. Thousands of people showed up to Mediacom offices to get a set of bunny ears so they can watch KDSM Fox 17 over the air.

Mediacoms antenna supply was drained due to the number of customers that showed up. KCCI says they checked with several local retailers, including Best Buy, Wal-Mart, and Target, to see if they had any antennas available. None of those stores had any antennas in stock when KCCI checked. Mediacom was giving them away for free, so they should have expected a pretty large turnout. It was really encouraging to see so many people out there. It just shows how many people are supporting Mediacom and choosing not to switch to DirecTV or another satellite provider.

Commenter BobH got his free antenna from Mediacom. However, KDSM Fox 17 (I assume) is the only station he can’t pick up over the air. I’m in the same boat he is. When I try to get KDSM Fox 17 over the air, all I see is snow. I thought KDSM had a decent over the air broadcast range, but they obviously don’t. I’m no more than 40 miles from Des Moines.

Hopefully Mediacom will keep pushing Sinclair to make a deal. I’m betting Sinclair will notice the negative effects this will have on their stations fairly soon.


WordPress Theme: Unwakeable 1.2

84

Unwakeable 1.2 is out! You can download it or you can visit the Unwakeable page for some more details. You may also be interested in the ChangeLog, although I’ll go over a number of the changes in this post.

Probably the most notable change is the separate options for Unwakeable in the wp_options table. Let me explain a little bit. Basically, I’ve renamed the options to be unwakeable specific. Previously, Unwakeable would pick up options already set in K2 or it would just set the default values, still with the K2 names. So, if you’re upgrading to Unwakeable 1.2 from an earlier version, you’ll want to click the “Copy Options” button from the Unwakeable Options page. Clicking that button will take the options you had set in previous versions and will update them to work with Unwakeable 1.2. You can also copy your options from K2 to Unwakeable 1.2 with this button. If you’re installing Unwakeable for the first time, this probably doesn’t apply to you.

Now, if you’d rather not copy your old options over, that’s OK. You can just go into the Unwakeable Options page and set the options as you normally would. If this scares you, don’t worry, you can’t really break anything by not copying options over. Really, you can’t break anything even if you do want to copy your previous options over. If you have any questions, just get in touch with me.

I’ve also added support for two more plugins, Landing Sites and Gregarious. Gregarious is a replacement for the Digg This Reloaded plugin, which is now dead. Unwakeable 1.2 still has support for the Digg Integrator plugin also. I suggeset you use Gregarious if you want Digg buttons on your pages. It makes use of the new Digg API where Digg Integrator loads Digg buttons in an iframe, not the ideal way to display Digg buttons these days.

Now, you may be wondering why I built in support for Gregarious. Gregarious has a feature called auto-append that will automatically place a Digg button on your page. However, that feature isn’t enabled by default. And, there’s no option to place the Digg button in the sidebar with the auto-append feature. So, I added some code that will detect if auto-append is enabled. If auto-append is enabled, the Digg button isn’t displayed on the sidebar. However, if auto-append isn’t enabled, the Digg button will be displayed in the sidebar. That way you still have the option of displaying the Digg button in your sidebar, even if you use Gregarious.

Also, I’ve made a small fix to the CSS that should get rid of the few pixels of whitespace that were showing in the header, between the black and gray sections. The black in the header is now flush with the right side of the page. You can see what it looked like previously in this image. And you can see it fixed in this image (or right here on this blog). I’d like to thank Jason for pointing out that whitespace.

Is there anything you guys would like to see in the next version of Unwakeable? Could be anything from support for a plugin to design changes. Anything? Anybody?

Enjoy this new version and let me know if you have any problems getting Unwakeable functioning properly. I will provide almost unlimited support for people having issues with Unwakeable. Although, I won’t always be able to support Unwakeable if you’ve made numerous changes to the CSS or PHP for your site.

And lastly, a big “thank you” to everyone who is using Unwakeable. I never anticipated that this theme would become so popular. At my last rough count, there’s about 300 blogs using Unwakeable, I expected maybe 20. :) Thanks again everyone for your support! It’s now far past my bed time…


Post navigation