web analytics
Skip to main content

Relative url in og:image using WordPress Facebook plugin

I was struggling one of these days trying to figure out why my WordPress blog posts didn’t show the proper image when shared in Facebook.

I had already tried some different Facebook plugins, including the official Facebook plugin for WordPress, but I couldn’t find the reason. When I used the Facebook debugger, I always got an error message like this one:

Object at URL ‘http://mysite.com/mypost-path’ of type ‘website’ is invalid because the given value ‘/images/my_image.jpg’ for property ‘og:image:url’ could not be parsed as type ‘url’.

Strange, because my wordpress blog configuration looked fine, my theme (Atahualpa) supported featured thumbnails, and my posts had a featured thumbnail set.



Google will shut down its Translate API



Last May 26, Google announced that its Google Translate API, one of the most popular APIs of the search giant, has been officialy deprecated.

The Translate API is extensively used by a wide array of  Web publishers and applications focused on the creation of multilingual contents. It seems that this use was so huge that even the Palo Alto behemoth was “burdened”, as the official note states:

Important: The Google Translate API has been officially deprecated as of May 26, 2011. Due to the substantial economic burden caused by extensive abuse, the number of requests you may make per day will be limited and the API will be shut off completely on December 1, 2011. For website translations, we encourage you to use the Google Translate Element.

In fact, as one can read in the note, the translation services won’t be entirely shutdown, only its API. Google Translate Element will be an option for those who will still want to use the Google translation services. It allows the automatic translation of Web sites without using the API directly.

Nevertheless, plugins like WordPress Global Translator will not be able to access the Google Translate API, from December on. Luckily, in this case, the plugin already offers Babel Fish, Promt, and FreeTranslations engines as alternatives to Google translation services. The same can’t be told about other plugins though.

Anyway, it’s bad news for anyone who strongly bets on the cloud and its so-called advantages.

Together with the Translate API, Google has also deprecated and scheduled for shutdown on December other APIs (though those are not so popular as the Translation API):

Another seven APIs have been deprecated by Google, but still not scheduled for shutdown:

Which one will be next on queue? Google Maps? Make your own bet.

New Atahualpa 3.6 theme released

BytesForAll has announced the release of Atahualpa 3.6, a version that apparently does not bring many new features, just some improvements and adjustments in internal code.

Due to changes in the WordPress themes submission process, BFA has opted for not maintaining theme’s compatibility with older versions of WordPress (older than 3.0), so you must be careful before choosing to upgrade. Be sure you have latest WordPress 3.0.4 version (also because that version brings a critical security  patch).

Anyway, I’d recommend to wait for a couple of weeks before upgrading to Atahualpa 3.6, since it still has some bugs (and certainly other bugs will be found), namely the ones related to the removal of parts of old code that are not supported by WordPress anymore. According to BFA, in two weeks they will release an update of the theme (probably: Atahualpa 3.6.1) fixing the bugs found until then.

WordPress 3.0.4 critical update

WordPress has just announced that it has released a patch to solve a critical security problem in its HTML sanitation library (KSES). Apparently, the bug is really serious, since they have asked all site adminstrators to apply the patch ASAP, even before the holiday.

So, let’s run for the fix and prepare ourselves for a nice New Year’s Eve!

WordPress version 3.0.4 can be downloaded here (the update can also be made directly through WordPress Dashboard).

Debug WordPress

Many WordPress bloggers don’t know that , when you need to debug your WordPress blog (version >= 2.3.1) , you can activate the WP_DEBUG option in the wp-config.php:

define(‘WP_DEBUG’, true);

If this setting is not present in the wp-config.php, its value is false by default.

With this option set, you’ll see all debug messages produced by WP code. Besides, beginning with version 2.5, this option also sets PHP error_reporting option to E_ALL, meaning that you’ll also see warnings about deprecated functions you might be using. And last but not least, since WP 2.3.2, setting WP_DEBUG to true is the only way of having databases errors printed.

Another useful option for debugging is SCRIPT_DEBUG. With this option set, WordPress will use the development Javascript scripts, instead of the normal ones. So, instead of using, for example, wp-includes/js/comment-reply.js, it will use wp-includes/js/comment-reply.dev.js.

For activating the SCRIPT_DEBUG option, put this in your wp-config.php:

define( ‘SCRIPT_DEBUG’, true );