Khleomix Designs

Socialite wordpress plugin error

tim — Fri, 24 Sep 2010 18:51:26 +0000

If you are trying to use the Socialite plugin and your wordpress version is 3.0+ then you’re bound to get this particular error:

Warning: unserialize() expects parameter 1 to be string, array given in .../wp-content/plugins/socialite/include/socialite.inc.php on line 49

The fix is actually very simple but you would need to have a some knowledge in editing php codes or at least the tenacity to try… Don’t fret the process is just download, open, find, copy and paste and upload. You would need an ftp client to download and upload and a text editor (if you don’t have dreamweaver or the like, notepad will do) to edit the needed file. Or you can always use the native plugin editor of wordpress.

If you’re going to use ftp, download the socialite folder under wp-content/plugin/, open the file socialite/include/socialite.inc.php. Find the following (CTRL+F will do wonders):
// now unserialze the options to get the array of values $this->options = unserialize($this->options);

around line 48-49

replace: $this->options = unserialize($this->options);
with: $this->options = maybe_unserialize($this->options);

find:
// options are stored serialized into the wp_options table $val = serialize($opts);

around line 73-74

replace: $val = serialize($opts);
with: $val = maybe_serialize($opts);

Save the file and upload. That should be good until the next update.

The reason: This plugin is not compatible with wordpress 3.0. The newest wordpress version automatically serializes/unserializes data and since the plugin has not been updated, it still uses the old code thus the unserialize warning.

And of course, for those who are afraid of editing their files you can download the fixed socialize plugin after the jump

JUMP

Fatal error: Call to undefined method wpdb::get_blog_prefix() problem

tim — Mon, 19 Jul 2010 15:40:02 +0000

If you just upgraded to WordPress 3.0 and is using the db cache reloaded plugin, you might encounter the following error when you try to access some pages in your admin:
Fatal error: Call to undefined method wpdb::get_blog_prefix() in …/public_html/wp-includes/user.php on line 445

The fix is pretty simple:

disable the plugin.
manually delete the wp-content/db.php
delete the offending plugin
if you must need to use a caching plugin, I believe there is a patch around (google is your friend). the patch should be good until the plugin developer updates the plugin to be compatible with wordpress 3.0

Can’t upgrade to WordPress 3.0?

tim — Tue, 13 Jul 2010 03:44:53 +0000

Its been too long and I’ve neglected my own site, so here I was checking out my admin, deleting spam, upgrading plugins and was about to upgrade to WordPress 3.0… Everything went fine except the wordpress 3.0 upgrade.

When I pressed the upgrade now link, it redirected me to a page with this message: “You are not allowed to call this page directly.” Of course, I was about to pull my hair out (nah…), but Google will always be your friend although a little bit tricky this time. So I’ll save somebody else a few minutes of trouble.

If you get the “You are not allowed to call this page directly.” message, deactivate your NextGen ImageFlow plugin and try again. Don’t worry you can activate it again as soon as you’re done upgrading.

A brand new site

tim — Sun, 07 Mar 2010 17:53:03 +0000

I finally managed to start on my own site although I still have gazillion more projects to finish. This site is still a work in progress and content are mostly blank for now. I’ll eventually get to it… somehow…

I’m not really sure if I like the layout, but its a start… I do love the overall effect and I am currently in love with the colors. I think I’m going to implement the same layout in BeThumbed which is totally in need of a makeover… Or I might do something totally different.

Its 2AM and I’ve been working since 10AM yesterday, I should be tired but I’m not sure I am yet. I think I’ll start on one of my new projects or maybe finish the current ones. My mind is a mess, but then again, it usually is and I thrive in madness.