Technocrank

wp-Hyphenate 1.07 beta
GigPress 1.4.5

I have a site that uses GigPress and in order to get it to embed its own code you need to insert a [gigpress_upcoming] (or similar) code into the page.  However, when wp-Hyphenate is activated it seems GigPress gets skipped and the string literal “[gigpress_upcoming]” gets regurgitated onto the page.

Update: It is indeed a known problem by the developer who quickly got in touch with me and informed me that it’s fixed in the upcoming release.  If this is actually bugging you and you need a quick fix you need to edit wp-content/plugins/wp-hyphenate/wp-hyphenate.php around line 94.  Change:

[sourcecode language=’php’]
add_filter(‘category_description’, ‘hyph_preProcess’, 10);
add_filter(‘comment_text’, ‘hyph_preProcess’, 10);
add_filter(‘the_content’, ‘hyph_preProcess’, 10);
add_filter(‘the_excerpt’, ‘hyph_preProcess’, 10);
add_filter(‘the_title’, ‘hyph_title’, 10);
[/sourcecode]

to

[sourcecode language=’php’]

add_filter(‘category_description’, ‘hyph_preProcess’, 9999);
add_filter(‘comment_text’, ‘hyph_preProcess’, 9999);
add_filter(‘the_content’, ‘hyph_preProcess’, 9999);
add_filter(‘the_excerpt’, ‘hyph_preProcess’, 9999);
add_filter(‘the_title’, ‘hyph_title’, 9999);

[/sourcecode]

Which forces wp-Hyphenate to do its duty last.

Google‘s CEO Eric Schmidt is on record here and here saying that Twitter is a “sort of poor man’s email”.  I respectfully disagree.

Twitter is email lite.  Twitter is the icing of email’s cake without the heavy filling.  Twitter is the top of the muffin.  Twitter is the sex without the wet spot (was that too much?).

Basically, Twitter is email – except without the Body of the email.  It’s all Subject line.  You don’t even have to specify the recipient.  Ever wanted to send a message to somebody (or everybody) without specifying anybody and didn’t really want to say anything other than “I made it home”?  Twitter is perfect for this.

Picture this:


From: Crankie Tech <dont@spam.me>
To: Everyone I Know <*@internet*.*>
Subject: I Made It Home
Date: Thu, 5 Mar 2009 17:08:27

Well, I made it home.  That is all.

Sincerely,
Me

It’s short, but it’s easily 700 bytes longer than it needs to be, not including firing up the email client or web client, blah blah blah.  With Twitter, on a single data-light web page you get:

I am home.

Or occasionally:

Twitter also relieves you of having to fish the odd spam out of your Inbox because, well, honestly, it’s all spam.  However, it’s spam from people you know – which makes it only slightly less annoying because you asked for it.

jQuery Lightbox (Balupton Edition) 1.3.5

jQuery Lightbox (Balupton Edition) WP plugin 0.5

There are a million lightbox implementations out there and almost as many corresponding WordPress plugins.  My favourite is the jQuery Lightbox (Balupton Edition) which, in my opinion, is one of the best looking ones out there.  A lot of them go for flashiness but end up looking tawdry or, in their attempt to be pretty end up suffering usability issues.   The jLB is simple and attractive.  I use it in conjunction with the Add Lightbox plugin.

Read the rest of this entry »

The only problem with this chart is the fact there’s significant overlap between some of these, e.g. “People who can’t afford Match.com” and “Proud ownever of butterfly tramp stamps”.

WP Super Cache 0.91
Bad Behaviour

Not a conflict, as such, but if you have Super Cache 0.91 and Bad Behaviour running simultaneously, you’ll want to go here and grab the code for wp-content/plugins/wp-super-cache/plugins/badbehaviour.php and replace the contents of that file.  The shipped contents cause Super Cache to look for a directory called wp-content/plugins/Bad-Behaviour which won’t exist (that’s the old install directory); wp-content/plugins/bad-behaviour is the current plugin install.

The only down side to this not working properly (I think) is that BB needs static HTML files to work.  You can switch Super Cache to support BB, however, you’ll only have Half-On legacy WP-Cache.  I suppose this is fine, although, if that’s the case then you really don’t need Super Cache installed at all.  I can’t find a decent explanation for any of this so I might be wrong as to the why.  I could also find no explanation as to what level of armageddon will ensue if you disable the BB support option in Super Cache and allow it to serve dynamic pages.  My guess is BB will simply either not catch any bad behaviour or it won’t work quite right and maybe false positives (?).  However, upon looking at the foot of the page source, it’s stating that Super Cache had served it up dynamically.  Frankly, I don’t know what’s going on here.

I don’t know which is the worse trade-off: pages loading slower and blocking spam bots, or pages loading quickly but serving them up to any spam bots that come knocking.

Note: I would have assumed that the plugin would do it for me, but I reloaded a page which I think was probably previously cached as compressed and the browser told me the page was compressed with some unknown compression.  I cleared the Super Cache cache and reloaded and it was fine…for a while.  Now it sporadically does it.  I’ve reverted back to the previous options for now.