Wedge

You can add the setlocale call first before the wp_remote_get call if you like.

Uhm.. dates are still in english..

And another question.. would it be faster (and better) to use file_get_contents or wp_remote_get (a WP function that uses the HTTP GET method..)? :)

http://php.net/manual/en/function.date.php:

Warning: date() expects parameter 2 to be long :blush:
I'm doing it wrong.. right? :P

Yes, you're doing it wrong. Don't use date, as I said, it doesn't do what you want. And plugging in strftime has broken it because date wants a number, not a string, hence the error.


It won't work on Windows, though as %e isn't supported.

Oh! Clear now. :)
Am I wrong or the line $date = $tweets['created_at']; is useless (because then I decode the date directly from the JSON)..? It confused me a bit... I thought I needed to change that too but then I realized I don't need that... Right?

Yup, it is useless, unless you want to directly use $date itself into the echo statement.

Clear. :)

And about..:

Considering that I have no idea what wp_remote_get does (and note that file_get_contents with the URL wrapper does also use the HTTP GET method), I cannot answer that question, and no, I'm not about to trawl through the shit-heap that is WP's source to find out.

What I can tell you is that if file_get_contents works, it's certainly workable. But it has limitations, namely that it's not particularly flexible across servers since it's easy to disable it at the config level, and it isn't robust in terms of handling time-outs. If WP's function handles *any* of that (and even my lack of faith in WP's code suggests that it would handle *some* of it), run with it.

If this were file_get_contents vs Wedge's equivalent (the weget class), I'd have no hesitation in recommending Wedge's own much lengthier and likely slower - but far far more robust solution. I would likely argue the same for WP's case.

Reasonable. :)

I "applied" htmlentities to my decoded data: '.htmlentities($value->caption->text).'
The downside is that accents are broken, example:  ì becomes Ã~

Page char-set is UTF-8. I thought it would have handled accented chars properly...!

The incoming data isn't UTF-8, it's probably likely ISO-8859-1.

This code works, is it also correct? :)
'.htmlentities($value->caption->text, ENT_QUOTES, "UTF-8").'

If it works, it's probably correct... ;)

TBH, it was a niche app at best before they released the Mandroid version (and got bought by Facebook).