Version 1.0.3 has been released, which fixes a few minor bugs and introduces a new option. It is still considered to be in a Beta stage, which most likely will change with the next release.
Changes
- A new option has been introduced to hide the license and attribution information in the footer.
- Bug fix: Config hash file was never initialized
- Bug fix: Enabling “cacheable” option resulted in fatal PHP errors in some cases
- Bug fix: Preview option did not work when “cacheable” option was enabled
- Bug fix: “All Rights Reseved” licenses had no URLs
In addition, WP Flickr Background is no longer compatible with WordPress version 2.8 or older.
Links: Direct download WP Flickr Background (192) | WordPress Plugin Directory
Well, a little over a month ago I had put the final touches to the WP Flickr Background plugin and entered it into Alpha stage. Over the entire month and with a few thousand visitors, there were only two issues reported (one of which was unrelated).
Satisfied with this, I’ve now made version 1.0.2 available as a Beta product. That means you can now use it for your own purposes, however I do not recommend using this in a production environment just yet (although nothing is stopping you from doing so – use at your own risk!). View Full Article »
If you’re new to this website, you probably haven’t noticed. But the background you’re seeing is actually something new. And random. And streamed from Flickr. It’s a new plugin that I am developing for WordPress called ‘WP Flickr Background’.
A little over two weeks ago I changed my theme to Motion by 85ideas, and was intrigued by its effective use of transparencies and the background. And since I quickly get bored looking at the same thing, I thought ‘Why not make this background random’? Flickr provides millions of photos, many of them under a Creative Commons Attribution License, and this would be an excellent source for those random backgrounds. So I started coding… View Full Article »
A while ago my blog started to act up by randomly showing translated pages in place of the desired language. The culprit was a WordPress caching plugin (Hyper Cache) that started to misbehave with the latest upgrade. I promptly disabled it and went on a search for a replacement.
As you may have read in one of my previous blog entries, specifically “NginX and Apache, but no memcached”, I prefer to use NginX as the front-end serving static files, and Apache as a back-end dealing with the dynamic pages. So it would be ideal if NginX could serve up static WordPress files, which is exactly what I am doing now with the help of WP Super Cache. View Full Article »
Since I started this blog I have been using WordTwit by BraveNewCode (they ran out of spaces apparently). It’s a simple to use plugin for WordPress that will update your Twitter status whenever you publish a new blog article.
You can customize your message and use [title] to replace it with the article’s actual title and [link] with a (shortened) URL to the article. So you could do something like “New blog entry ‘[title]‘ posted at [link]“ – Well, perhaps you’d want to keep it as short as possible though, but it’s to give you an idea.
So given that you can customize your message, you can also add one or two hashtags. But these are all done manually, for example “Blog [title] – [link] #blog” is what I was using myself.
But the #blog hashtag isn’t really something a lot of people will search for. So why not re-use the tags that I already have added to my article with WordPress? Like this article for example, can’t I use its customization tag as the #customization hashtag in my Twitter update? Well, with some modifications to WordTwit, it’s possible. Here’s how. View Full Article »
