Developing plugins and themes for WordPress should be super easy — period. You shouldn’t have to care about installing a web server, fiddling with databases and virtual machines. It should be instantly available whenever the need exists. This is a small introduction to my setup using Docker when developing WordPress themes and plugins.
In an effort to make this blog load fast everywhere in the world and not just in Europe where the server happens to be located, I decided give Cloudflare a try, since they offer a free service in addition to their premium offerings. There are however some not quite so obvious steps to consider when starting to use a full-site CDN, especially when using WordPress as the site engine.
WordPress 3.9 has been released to the world, containing lots of exciting features including drag and drop for images and plenty of eye candy.
Ghost is a recently released blogging platform based on Node.js and probably a direct competitor to established platforms such as Medium.
According to the author of Gust, Ghost was in its conception thought to be a WordPress plugin but morphed into an entity of its own, and this is where Gust comes in.
At the begining, Ghost was supposed to be a fork of WordPress. Then there was a talk of a plugin, that would give a next-generation admin panel for WordPress. But in the process it became a new blogging platform, built on Node.js. This plugin is an attempt to bring the nice and clean admin panel of Ghost back to the WordPress ecosystem.
I gave it a go in my test WordPress installation and I am really impressed by it, given its early stage in the development process. Just a couple of iterations more adding support for featured image, post format and custom fields, and I could probably use it.
Its strengths lie in the realtime Markdown preview pane, which works really well. It currently doesn’t reflect the current website theme though, which may or may not be an issue.
WP Facebook Like 1.5.1 has now been released, containing two new features among other bugfixes. It is now possible to disable the like button by creating a custom setting for that specific post or page and setting wpfblike to false.
The other feature is the inclusion of the new Send button available from Facebook. When enabling this new button in the settings, it will show you a new button alongside the old Like button.
This new button makes it easy to privately share content to friends and family without having to post it on your public wall for everyone to see.[Download Now]
I know a lot of you have been waiting for this new feature, and a beta version of the new WP Facebook Like 1.5.0 has been released. The new version lets you turn off the button on specific posts and pages by creating a custom value like this:
Do note that this is a beta version and things may change a bit before the release, but the final version is scheduled to come out later this week.[Download WP Facebook Like 1.5.0 BETA]
I am pleased to announce the release of a new version of the WP Facebook Like plugin for WordPress! The plugin lets bloggers easily create a Facebook Like button for their posts. Changes from the previous version include:
- Added options for choosing to insert the button in pages and/or posts.
- Added a check to verify that the correct PHP version is used when activating. (PHP>=5 supported).
- Added settings link from the plugin list. (thanks udi86!)
- Added an automatic language detector, which is now the default. (thanks udi86!)
- Added Open Graph admins property, which will create a Facebook page for your current article.
I will go into the details of the update below, but if you are in a hurry, just download the new version, or wait for WordPress to automatically detect the new version and offer to upgrade automatically.
Options for inserting the button on posts and/or pages
There are a couple of new settings for enabling the automatic insertion of the button in pages and posts. Earlier, it was only possible to choose whether the button should appear on the front page or not. Now you can, in addition, control whether to show the button on normal posts and pages.
The new options are the first step for adding support for having the button in individual posts and pages.
Added new Open Graph headers
The new version will also insert new Open Graph headers, which are og:type and fb:admin. This lets you enter your Facebook user ID in the options, which will make you the admin of the current page. When you write a new post, just click the like button (you can unclick it right away). This will give you a page on Facebook where you can see who has liked your page and it lets you send them messages.
To get to this admin page, just select the admin link next to the like button.
Note that if you use the button_count layout, you will not see the admin link. Just go to Pages You Admin on Facebook to see all pages.
What are you waiting for? Download it now!
Facebook are currently having major issues with their social API, which means that the Like buttons on many sites simply return an error.
- References to connect_to_node_error.php
- The page at (URL) could not be reached.
If you are using my plugin (or any means of showing the like button), there is a big chance that it will currently not work. The Facebook team is surely hard at work fixing this, and I will post an update here when things seem to be working again.
Update 2010-06-02 02:45
from Mike Vernal <[email protected]> 2010-06-01 17:16:47
Sorry for delayed update. I wanted to let you know where we were.
We’ve been having trouble with outbound connectivity from the tier of machines that power the Like button. We’re still debugging this issue, but we’ve restarted the tier of machines a few times, and the situation does seem to be improving.
We have a number of people from our engineering and operations team continuing to work on the issue and hope to have a more definitive update shortly.
Sorry for the inconvenience here, and thanks for bearing with us.
-mike (Platform Engineering)
Update 2010-06-04 21:00
From Matt Trainer 2010-06-04 11:11:29
We’re reopening the bug to investigate the “Cannot be reached” bug. Thanks for the detailed repros.
For the international folks out there – we’ll look into extending the timeout, but the issues your sites are seeing are most likely linked to that issue and not the central issue of this bug.
I just updated to WordPress 3.0-dev which among millions of other things has support for custom post types! Movies and Galleries are natural candidates for getting their own post type, and bundled with custom taxonomies for each post type will be very interesting indeed!
Other cool things to look forward to include custom menus and a lighter admin interface, designed to keep you focused on the content.