Updated WordPress Theme
Hey all,
Just updated my site’s wordpress theme to Desk Mess Mirrored.
Bit more of a personal touch to it.
Kinda got tired of the old theme.
Yes yes, I’m meant to be blogging but haven’t got around to it :S
Currently I’m working on a mini javascript project which provides an API to access Google Analytics cookies easily. On top of that, I’m also working on writing a search funnel script that tracks the funnel of keywords that users (new & returning) use through the organic medium.
Hopefully I’ll get to post that up soon :)
New WordPress Theme Launched!
Ok, I’ve finally managed to spend a good portion of my Saturday evening tweaking, testing and configuring this new theme locally. Seems like I’ve ironed out most of the bugs I encountered earlier and viola, this theme is finally live!
Since I couldn’t be bothered hacking the social bookmarking plugin using jQuery, I decided to look for a plugin that uses jQuery already. SocioFluid is a great social bookmarking plugin that uses jQuery. It has a cool feature which is similar to your navigational bar on mac computers.
I’ve also added adsense in the header and within the posts in hopes of generating some dollars from this website, but mainly to try it out and see what it is capable of since I’m working in the search industry. It’d be quite a handy piece of knowledge to have and master :)
There are also 4 125×125 banner ads available for advertising, so feel free to contact me if you’re interested. Most likely I’ll charge a flat rate rather than CPM/CPC models as I couldn’t be bothered going through tracking systems.
If you do encounter some strange or unexpected behaviours on the site, please let me know and I’ll fix it. Obviously I’m unable to go through each post and make sure they all look correct.
Tell me what do you guys think. Is it better? Worse?
Better I hope :)
WordPress: Getting unwanted 302 redirects locally
If you’re trying to do some testing on your existing WordPress website locally (using something like XAMPP) using the same files and database but find that it keeps 302 redirecting to your website rather than running it locally, you will have to configure your WordPress options to set your home and site URL to your local address.
Since you can’t even access your WordPress admin interface because of the redirects, you’ll have to configure this on the backend, your database.
Run your trustworthy phpMyAdmin or your favourite SQL client, connect to your local database and browse to your WordPress database (this is usually prefixed with wp_). Then browse to a table called wp_options or wp_kicpl0_options and look for a table field called siteurl.
The current value of this field should be your website. Edit this field value to your local address (i.e. http://localhost/wordpress). Remember NOT to use a / at the end. Save this.
The next field to edit is called home. If you can’t find this field on your current view in phpMyAdmin, it’s probably on the next page of fields. Edit this field value to the same value you used in siteurl. Save this.
Once you’ve edited both fields, just simply type in your local address again in your browser and you should be running your website locally instead of being redirected to your online website.
WordPress Fatal Error: Cannot redeclare pclziputilpathreduction
If you’re using WordPress 2.7 and you’re trying to upgrade to WordPress 2.7.1 and you come across an error message like “Cannot redeclare pclziputilpathreduction()“, make sure that your WordPress Automatic Upgrade plugin is disabled/deactivated.
Then proceed to upgrade your WordPress to version 2.7.1 from your dashboard and it should work fine (make sure your backup your files & database before hand!).
Seems like WordPress has already incorporated automatic upgrade into its core features already which will probably render the WordPress Automatic Upgrade plugin useless now.
Thanks though to the plugin creator for all your hardwork as it was probably one of the best plugins available ever since it came out.
Limitations of Client-Side Javascript Redirect – Blogger to WordPress
You may have read my previous entry on performing a 301 redirect from Blogger to WordPress, where I wrote a script that will capture all traffic to your old Blogger site and redirect it to your new WordPress site. Ideally you’d want to do the 301 redirects from the web server, but unfortunately Blogger doesn’t allow you to do that and thus, you’re left with the client-side solution: Javascript.
First of all, let me clarify briefly on my previous post and inform you what the core strengths of my script are.
- Client-side redirect will not work without Javascript. Pretty obvious huh? What that means is that search engine crawlers aren’t able to follow the redirect. Nasty limitation in a simplistic sense.
- Strengths of my script are:
- It works.
- You need a client-side solution if you’re on Blogger. No other way.
- It captures and redirects all traffic from your old site to your new site.
That being said, let me now expand on these two major points: the limitations of search engine crawlers and why is capturing traffic important.