[edit: i've now added Starred Review to the Wordpress Plugin Directory as version 1.1a which from now on automatically updates itself. enjoy]
I’ve added support for Wordpress Widgets to Starred Review. Along with some minor backend formatting alterations, no where near the quality it should be, but that’s for another day. I’ve also tidied-up the actual output, a bit more readable- less of that ‘classes’ jumble.
So Download Starred Review 1.1a, just overwrite the current plugin and make sure (if you’re not using widgets) you’ve got the new badge code:
<?php starred_review_badge('limit', 'category');?>
Starred Review 1.1 supports Wordpress 2.7.1, will soon have a Dashboard Widget for OS X and be listed on the WP Plugin Repository (if only they’ll email me confirmation?) all that good stuff just round the corner! Thanks to Peter at Apartment One Six for his widget tutorial.
If you’d like to see any future updates / additions, just let me know (via the comments feed or email). I’m pretty happy with this revision but let me know if you find any issues with this one!
Looking to add widget support to a wordpress plugin. There’s a lot of misinformation online, its out of date, incomplete or just wrong- I know because I’ve been working on bringing my plugin: up to date.
Peter’s Widgetizing a Wordpress Plugin was an invaluable resource- i can’t say better than that. Read his thorough and exact example for a quick way into wordpress widgets, and check out the rest of Apartment One Six.com I can see it being very helpful in the future.
Redirecting the most common mobile browsers (and then some) can be done through a couple of simple Rewrite conditions in your .htaccess file. I think this is beneficial over the multitude of Javascript and CSS hacks out there for a number of reasons, the primary one (as an iPhone user) is speed; who wants to load the whole of a html page, all of its links and css before redirecting to a ‘mobile safe’ page (more load time… more redirects). Most of the how-to’s I found online were concerned with .js hacks… ugh, when you’ve got your own server there really is no excuse. Now:
I need to redirect visitors to my portfolio (which is heavy on images and js, there’s a flash ‘autoviewer’ in there too) to a mobile-safe version, this has lower dimension versions of the same photos in my flash gallery with little of the fuss (read: graphic design). I’m working on the design of that right now. But here’s the crux- the .htaccess required to redirect visitors to a certain folder to a subdomain within that location.
callumalden.com/photography/
magically directs to….
callumalden.com/photography/mobile/
Without loading the /photography/index.php and additional redirect code this is surely the best way to direct mobile users. This bit of code is useful because it also redirects all pages within the ‘photography’ folder to the ‘mobile’ pages. So an attempt at /photography/portraits.php will direct to /mobile/
rewriteengine on
rewritecond %{request_uri} !^/photography/mobile/.*$
RewriteCond %{HTTP_ACCEPT} "text\/vnd\.wap\.wml|application\/vnd\.wap\.xhtml\+xml" [nc,or]
rewritecond %{http_user_agent} "sony|symbian|nokia|samsung|mobile|windows ce|epoc|opera" [nc,or]
rewritecond %{http_user_agent} "mini|nitro|j2me|midp-|cldc-|netfront|mot|up.browser|up.link|audiovox"[nc,or]
rewritecond %{http_user_agent} "blackberry|ericsson,|panasonic|philips|sanyo|sharp|sie-"[nc,or]
rewritecond %{http_user_agent} "portalmmm|blazer|avantgo|danger|palm|series60|palmsource|pocketpc"[nc,or]
rewritecond %{http_user_agent} "smartphone|rover|ipaq|au-mic,|alcatel|ericy|vodafone/|wap1.|wap2.|iphone|android"[nc]
rewriterule photography/$ /photography/mobile/ [l,r=302]
It may just be my server setup, but I had to use the whole address on the bottom line to achieve the redirect, this is the same on all my .htaccess files. Odd, No? Anyway- pretty handy. If you want to test out the redirect, just change something up there like ’sony’ to ’safari’ or whatever your browser happens to be, save and refresh the browser and you can emulate the iPhone experience. Now, off to code some Blackberry/iPhone-savvy html!
Not a return to form as such. A return to formlessness and oddly enough it does fit. 4 Years have passed, time to catch up. Podcast 11:
Drag the above link into your iTunes ‘library’ (or Firefox Bookmarks / alternate Podcatcher) that’ll install the feed- you’ll now recieve the updates as/when we make ‘em. Or you can subscribe through the iTunes Store. Enjoy.
I don’t like the K2 404 page. You’ll only see this when the author (that’s me in this case) makes a fatal mistake or the hosting server has hiccups… but the basic ‘file not found’ page that ships with Wordpress’ most popular theme is awful. The problem is it doesn’t look like a warning page. It offers no additional options, simply points users in the right direction, basically says- “pff, work it out”.
What was not obvious to me was how to override this mess of a information page. How to do it? PHP includes? some form of redirect or did it involve .htaccess
No. To override the default K2 404, which is automatically generated from theloop.php all you need do is place an a file in your wordpress directory called 404.php
Wonderful. What do you think: metacomment.com/blog/404.php
I know there’s a magic plugin out there called ‘recommended posts’, I’d love to tie this in with the 404 page (using the faulty address as a starting point), to give suggestions. Maybe even implement live-search, perhaps a quick email to the blog’s author. Subject: Another 404
