Adding a Google Wavelet to your wordpress blog
Now that more and more people are getting access to Google Wave it's getting interesting to use it.
Google Wave has allot of possibilities but one of the coolest is the possibility to embed a wavelet to your blog.
Adding a Wavelet is quite easy and isn't that different from adding some other kind of media to your blog.
To do this just follow these simple steps:
- Install the wavr plugin on your wordpress blog and activate it.
- Start writing a new blogpost (Notice that there is a Google Wave button in your Kitchen Sink now)
- Click the button and fill in the ID of your Wavelet (don't forget to change %253B to +)
For example googlewave.com!w%252Bda8ZC1YwA.1 changes to googlewave.com!w+da8ZC1YwA.1 - Fill in the other stuff you want to change, things like the backgroundcolour or the font
- Publish your post
You'll still need to remember one important thing, people need a Google Wave account and should be logged in to see the Wavelet. Also don't forget to make the Wavelet public. Below you can see an example.
Thanks to Mike from Mimor.Be for the Google Wave invite ^^
Stolen Google wave accounts
It seems that some people of the feline race have been hacking in the Google database and stole some account credentials.
Here's a message from their leader.
WordPress Update Errors
Today I've encountered a rather annoying problem.
A friend of mine told me that there was a bug in the current WP version and that I needed to upgrade.
As it was a quite annoying bug (one that made it possible to ask for a password reset without confirmation),
I decided to upgrade as soon as possible. And I still curse that moment...
After the upgrade I wasn't able to upload or install things on my page. Still getting the same messages over and over again:
"Unable to locate WordPress Content directory (wp-content)"
"Warning: ftp_rawlist (): open_basedir restriction in effect. File (/tmp) is not within the allowed path(s)"
At first I just scratched my head and tried again, but the error was quite consistent, as it came back every time it tried.
Then I started to check all my files on the server, and just like I expected everything looked just like it's supposed to be.
Perhaps there went something wrong with the upgrade, so I decided to restore a backup. To my greatest horror the restore gave the same result. That was the moment that I started to search the tubes for more information.
Now we're a little hour later and I found a sollution.
- In your WP root create a folder called "tmp"
- Then ad the following string to your wp-config.php --> define('WP_TEMP_DIR','/tmp');
- Save the file
Those three simple steps solve the problem, at least it worked for me.