hwa2u.com

New gallery is up now! This time no more Lazyest Gallery screw that it’s too old already, I’m now using the NextGEN Gallery by Alex Rabe. 🙂

Here I am again!! After more than a year I didn’t updating my blog, except for the one with my tortoise passed away, it’s a remembrance post for my poor little Betty. 🙁

Anyway let’s continue with my blog updates! As you can see we have a totally new theme here, nothing special about it still dual pane with sidebar on the right side, just the way i wanted it always. 😉

For your information this theme is actually from TechJunkie 1.0 by Theme Lab, however the CSS is heavily reconstructed by me, and also some minor changes.

Guys! After more than a year i disabled my ShoutBox, now it’s back!!! 😀 But i disabled my Recent Comment.

The reason i bring back my ShoutBox is because sometime when people just want to say something to me, let’s say hi, they will go to any topic and post a comment there, which will ended up as spam, so i decided to put a ShoutBox so people can say whatever they want to me as long as it’s make sense. 🙂

Actually, the SboutBox is an improved version of the WP-ShoutBox by Ryan Mack, most of the modification i made are for the back-end, which is the admin part, other than that my version of ShoutBox is validated as XHTML Strict!! 😉

Now that if you haven’t notice this, i did a minor update to my current theme, changed a bit the sidebar as well as a whole new date design in each post. 😉

Changed a whole new set of icons for my theme, better than previous one created by me, which i think is kinda sucks. 😆 I’m now using the Silk icon set by famfamfam, it’s a very nice icon really, a big thanks to Mark James for this great icon set! 🙂

Just updated my WordPress to the latest version, WordPress 2.0.6, and also applied the FeedBurner fix, where sometime FeedBurner will return an error telling that you have invalid xml, or an error message like below:

Your server disconnected us before sending the full source feed content. If your blogging platform is TextPattern, this is a known bug, and a fix can be found here: http://forum.textpattern.com/viewtopic.php?id=11247

Here’s an explanation from NeoSmart:

Explanation

FeedBurner uses something called “Conditional Get requests” to ask your server whether or not the page has changed since the last it viewed it, in order to save you some bandwidth. Depending on how popular your site is, FeedBurner may hit up your feed up to hundreds of times a day, so this is a really good idea! Unfortunately, in WordPress 2.0.6, your site doesn’t respond in a way that FeedBurner recognizes. The 304 headers it sends back to let it know that the content hasn’t changed are malformed and corrupt – and FeedBurner has no idea what they mean.

To fix this problems is easy, all you have to just open up your functions.php inside your wp-includes folder, go to line 2231, 2233 and 2234 and comment out this three lines, like below:

That should fix your feed problem, there are a few more solutions from Mark Jaquith and NeoSmart, head over to their blog and find the one suit you most! 🙂

Few days ago i saw this from Weblog Tools Collection, it’s about the image placement for Google AdSense.

Some bloggers will use plugins that will place an image beside their AdSense advertisement in believe that it will increase the CTR (Click Through Rate), i’m not sure how true it is but one thing for sure is that it will draw your visitor’s attentions, and this make the advertisement looks nicer too, that’s what i like about it.

At first Google AdSense said that it’s alright as long as we place a line to separate the image from the advertisement, and the image should not included as the link for the advertisement, but still we don’t know whether or not this violate Google AdSense’s Terms and Conditions.

Until recently Google had make a clear statement regarding the image placement policy. From what i understand, Google don’t allow we put images that is looks like part of the advertisement, so even though we put a line separating the advertisements is still wrong.

It’s December! And December makes people think of Christmas, and Christmas makes me think of snows, but sadly in my country, there ain’t no snow here, it’s sun shine throughout the years.

Shame to say that i never see or touch a real snow before, 😳 wish that someday will have a chance to see a real snow.

However, here in hwa2u.com, nothing is impossible, even a snow will fall in the world of Internet. Early season greeting to you guys from hwa2u.com, Merry Christmas 2006~!! 🙂

For those who broadcast YouTube in their blog before, you should know that the YouTube embed tag is actually not XHTML valid, it’s because the <embed> had been deprecated from XHTML 1.0.

By default the YouTube embed tag should looks something like this:

But it contain the <embed> HTML tag which is not allow in XHTML 1.0 Strict, so in order to make it pass the validation, i change the above code to something like this:

YouTube plays well with the new tag, and it doesn’t have the <embed> tag, which is XHTML 1.0 Strict valid!

While developing my new theme, one of my target is to achieve XHTML 1.0 Strict validation, at first i thought it won’t be that easy because it’s not only the templates i need to validate, but the plugins as well, so i guess it won’t be an easy job.

However i still manage to fix everything then pass the XHTML 1.0 validation, and now i’m happy with it. 🙂 but on second thought it’s not that hard to reach XHTML 1.0 Strict validation, all you have to do is just follow the rules right and you won’t go wrong.

There are a few thing that i learned while developing this theme, some WordPress tricks and valid XHTML stuff, will share them out within this few days, but for now, please let me take a break first. 🙂