Det är lite långt innan poängen. Hang in there… Wait for it!

(Filmklipp lånat från Aftonbladet TV, typ som de lånade från SVT på Frode).

(Jag behöver uppdatera till 3.3.1 också, kör just nu 3.3. Sten. Glashus. Ni vet).

Jag kan hjälpa dig uppdatera Kenza. Jag gör det i utbyte mot lite modetips.

Jag har försökt få Grays att ta hem dem. Men tydligen är best-före-datumen så kort att när de beställer så är de ofta gamla redan innan de kommer fram. Hur de nu kan stämma då jag alltid har fått höra att kackerlackor och Twinkies är det enda som överlever ett kärnvapenkrig. I Amerikanska filmer har vi fått lära oss att Twinkies finns kvar när världen är full av Zombies. Och filmer ljuger inte!

Men tiderna förändras. Och tack vare Twitter och mitt frenetiska tjat om Twinkies när det uppdagades att Hostess, företaget som tillverkar Twinkies, var på väg att gå i konkurs, kom jag i kontakt med @USAGODIS. Denna fina butik, och konkurrent till Grays, meddelade mig att de skulle få in Twinkies. And my world got a little bit brighter that day. Det fanns hopp.

Jag beställde Twinkies…

Leveransen var snabb. Redan på Måndagen hämtade jag ut mitt paket. Jag var nu redo för Zombie-appocalypten.

Jag måste tyvärr avsluta denna recension på en lite lägre stämma. De är inte så goda som jag hade hoppats på. Det är en lite citronig sockerkaka, med en sorts smörig geggig mitt. Lite kemisk i smaken. De blev lite godare dagen efter när de hade legat i kylen en stund. Tillsammans med ett glas mjölk. Kanske var min hype bara alldeles för stor. Ungefär som i väntan till Episode I. När dessa 10 bitar är slut så kanske jag inte kommer kunna hålla mig utan vill ha mer? Men jag är inte helt säker. Only the future can tell. Mina ytterst noggrant tweakade smaklökar var i vilket fall ganska så besvikna.

Jag vill dock rikta ett tack till USAGODIS. Utan eldstjälar som er så skulle jag kanske aldrig ha fått prova en sådan kulinarisk raritet, som Twinkies, i skydd av mitt trygga hem.

Betyget blir 2 hemlösa katter av 5 möjliga.

Disclaimer: Jag skrev denna recension som svar till @USAGODIS fråga efter en. Men de har inte betalat mig i Twinkies för den. Mina åsikter är helt mina och kan inte köpas… Ännu… *hint, hint* … USAGODIS, ni har min adress…

 

 

This vacation week, when I was going to play Skyrim, but ended up watching all Alien movies on Bluray and coding some WordPress, I might have found my bug. A user in a WordPress dev Facebook group asked if anyone had received pingbacks on custom post types. He hadn’t and was starting to believe something was wrong within WP. I thought it sounded like a fun thing to investigate. So I did. And it turns out it is… I think.

The reason seams to be that the XML-RCP server uses a function called url_to_postid() to get the post ID from the pinged URL. So if the ping is for a regular post and the site is using permalinks it might be something like feedmeastraycat.net/2012/01/08/on-the-road-to-a-wordpress-core-patch/ in which case /2012/01/08/on-the-road-to-a-wordpress-core-patch/ is sent in and the post id is returned. The problem seams to be that it doesn’t handle custom post type urls.

If there is a CPT named “products” and you have a post with the slug/name “macbook” you might have the url test.com/products/macbook/. The url_to_postid() function goes through the rewrite rules and tries to find a match. Which it should do. It then creates a query for that match, which in this case looks like this:

Array
(
    [products] => macbook
    [page] =>
)

The problem here is that this query will fail. WP_Query requires a ‘post_type’ => CPT_Name parameter as well. It should look like this:

Array
(
    [post_type] => products
    [name] => macbook
)

During a regular page call, this is made in WP->parse_request() (here). Not in WP_Query.

Well. I created a ticket and I’ve also added a suggested patch. In a comment. Cause I don’t know how to do it as a real patch… I hope that I haven’t missed anything. And that the higher up:ers like my patch suggestion. It would be nice to get a patch in early and free up 2012 for new goals.

Dimman låg tät så ingen kunde se GP-fyrverkerierna. Men grannarna fixade biffen…

 

 

Edit: 2011-11-27 — Seams like Bethesda has released a patch during the night. Looks much better now! :-D

 

 

I guess the “problem” here is that switch_to_blog() doesn’t change the WP_Rewrite object. So when get_author_posts_url() calls $wp_rewrite->get_author_permastruct() it get’s the permalink for the main site blog plus the permalink for the selected blog.

Not sure if this is a bug. Or just a way that it have to work. Either way, I created a filter for author_link which solved the problem for us.

function my_author_link($link, $author_id, $author_nicename) {
	global $blog_id;
	if (is_main_site($blog_id)) {
		return $link;
	}
	else {
		return str_replace("/blog/author/", "/author/", $link);
	}
}
add_filter('author_link', 'my_author_link', 11, 3);

What we do here is getting the global $blog_id variable which contains the current blog’s id number. We run it through is_main_site() to see if this is for example the photo blog, or the food blog, or if it is the main site. If isn’t the main site, we do a string replace on /blog/author/ to just be /author/. But if it’s any other site we return the $link parameter as it is, unchanged.

Disclaimer: Not sure if the problem exists if you don’t have permalink structure. Haven’t even tested. :)

• WPSettings — a set of classes to create a WordPress settings page for a Theme or a plugin.
• WPCustomPostTypeArchive — add archive functionality to custom post types.
• WPGetLatestTweet — a simple lib to get and cache the latest tweet for a username.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Det var en superfin resa. Väldigt glad att den blev av. Glad att jag fick visa Røros för Emma. Och glad vi valde att åka Trollstigen och stanna en natt i Geiranger. Även om skillnaden med fjordutsikt ena natten blev ganska stor mot natten i Lillehammer där vi hade E6 som granne.

Nöjd med objektivet jag köpte också. Mindre nöjd att jag glömde ändra ISO några gånger bara…

Added explanation:

1) Find someone who has Google+
2) Have them share a link with you (or someone who hasn’t got Google+)
3) Click the link in the e-mail sent
3) Join from that page

If it doesn’t work, Google might have fixed it! :)

In other news I’ve added ShareThis and Flattr. So Flattr me and I’ll use the money for good. I promise!

Updated – Twitter says that Google has closed the backdoor now. It was fun while it lasted … :)

 

 

Nä. Jag har inte köpt en Golf. Jag och Emma har hyrt en. Och så har jag köpt ett nytt objektiv till min gamla D70. Ser fram emot min semester!

Have you read it? No? Ok. I’ll wait a couple of minutes more then…

Done now? Good.

With the help of my co-worker Per I have now a fixed version of Twitter Tools that seams to work 100% with all allowed Twitter tags. The new regexp is as follows:

'/(^|\s)#([\pL\w]+)/u'

I have also remove the double space insert/remove thingy. So the whole thing looks like this:

$tweet = preg_replace_callback(
	'/(^|\s)#([\pL\w]+)/u'
	, create_function(
		'$matches'
		, 'return aktt_hashtag_link($matches[2], \' #\', \'\');'
	)
	, $tweet
);

I’ve made another small change though to the aktt_hashtag_link() function. Which use to look like this:

function aktt_hashtag_link($hashtag, $prefix = '', $suffix = '') {
	return $prefix.'<a href="'.aktt_hashtag_url($hashtag).'"
	class="aktt_hashtag">'.htmlspecialchars($hashtag).'</a> '.$suffix;
}

See that trailing space after “</a>”, that should be removed. With that extra space the tag “#åsa-nisse” gets a space after “#åsa”, and looks like this: “#åsa -nisse”.

So here is the final look in my Lifestream (red color was added to links for this image only):

Compared to how Twitter does it on their page:

I think that’s a success!? I’m gonna go ahead and send this to Crowd Favorite and see if they can implement it into the plugin.

So here is the problem:

The tag should be #GöteborgsVarvet.

I started with The Google and found this thread on the WordPress support forum. But I didn’t like the look of it since it just adds to the reg exp character list. I could have just added my missing characters. But what if a Norwegian dude gets Internet and starts using The Twitter. That won’t do.

So I searched some more and came up with this solution. First I changed the reg exp to this:

'/(^|\s)#([\w\pL]{1,})(\W)/u'

It will search for any “word character” using unicode. Which should make it find å, ä, and ö. But also “the other ones”. From other languages. Then it breaks the tag when it finds any non-word character. For example a “-” or a “(” or something like that. This brings it closer to how Twitter does it:

What we see here is that Twitter gets all the strange tags, even with å or ö in them, but it breaks at the dash character.

However, I still had a problem with the reg exp. It couldn’t find tags in a row. If the tweet had three tags in a row it only matched the first and the last. I solved this, ugly, by first changing all white spaces to double white spaces. And after the hash tag match I change them back. So the full code now looks like this:

$tweet = preg_replace("/(\s)/", "  ", $tweet);
$tweet = preg_replace_callback(
	'/(^|\s)#([\w\pL]{1,})(\W)/u'
	, create_function(
		'$matches'
		, 'return aktt_hashtag_link($matches[2], \' #\', \'\');'
	)
	, $tweet
);
$tweet = preg_replace("/(\s\s)/", " ", $tweet);

The only problem left now is that if you have a tag with a dash, it will remove the dash. So instead of “#åsa-nisse” with a link on “åsa”, like Twitter does. It outputs “#åsa nisse” with a link on “åsa”. Like this:

All tags are found, but the dash is missing from “åsa-nisse”.

Now I just hope that the guys over at Crows Favorite sees my e-mail and fixes this in the official release. Hopefully with an even nicer solution.

By the way…

To fix this hack, from home, on a Saturday, I finally bought Coda in the Mac App Store. It’s a bit expensive. I’m using Eclipse at work, which is free and has more features. I really miss the autocomplete features. But for quick hacks on Saturdays, Coda is really nice. Eclipse is bloaty and slow. I hope I can find some good plugins for autocomplete or that Panic can add it. I would love to be able to Switch. Coda feels more like Xcode 4. I would love to be able to do all my work in Xcode 4. But since I code PHP and not Objective-C at work … Well. Let’s give Panic some money by buying Coda and hope for the best! /rant

Time to go and give my Emma some cuddle before she gets totally bored out of her mind. Peace.