The WPSSO and NGFB plugins for WordPress are licensed based on the WordPress Site Address. Typically, a Development, Staging, and Production website – for example – will require 3 licenses. In the spirit of helping our fellow developers, we are offering a free license for every license purchased – on all past and future purchases. So, for example, if you purchased a license for example.com (or www.example.com), you can license and register the dev.example.com WordPress Site Address, using the same Authentication ID. This allows developers to purchase a license, develop a customer’s website, then change the Site Address upon delivery, without having to purchase an additional license for the production website.
Multisite licenses work the same way, licenses for example.com/myfirstsite/ and example.com/mysecondsite/ would give you two additional Free licenses for dev.example.com/myfirstsite/ and dev.example.com/mysecondsite/. If you use sub-domains instead for your multisite, then licenses for myfirstsite.example.com and mysecondsite.example.com would allow you to use dev.myfirstsite.example.com and dev.mysecondsite.example.com as well.
WPSSO version 2.4.5 and NGFB version 7.4.5 have been released together this morning. There are no updates to NGFB’s sharing buttons code, so both plugins share the same Changelog.
A new “author” meta tag has been added for Facebook. Since the “author” meta tag is not part of the Open Graph or Facebook standards, its associated ‘Author Name Format’ option has been included under the Google / SEO Publisher settings tab.
The “author” meta tag is different from the Open Graph “article:author” meta tag. The “author” meta tag contains the author’s full name (or variation there-of), where-as the “article:author” meta tag defines a URL to the author’s Facebook page. This allows Facebook to include the shared webpage author’s name bellow the timeline post. Unfortunately, the Facebook Debugger throws an error when both the “author” and “article:author” meta tags are present, so — to prevent confusion — this new meta tag is disabled by default.
There is a huge variety of available plugins for WordPress — 30,326 plugins as of today — and if you’ve tried more than a few, you’ll have noticed a marked difference in their quality as well (functionality, user interface, stability, etc.). If you know your way around PHP, you should take a moment to browse the source code of a plugin before installing it. You’ll notice quite a difference there as well. ;-) You can view WPSSO’s source code directly from WordPress.org’s SVN repository. If you do, please excuse the lack of comments — it’s on my To-Do list. ;-)
I’ve always kept an eye on performance, and used WordPress’s object and transient caches when possible, along with disk based caching when appropriate. NGFB and WPSSO are fast, but until recently, I’d never compared their performance to other plugins. As I prepare WPSSO v2.4.4 for release later this week, I took some time to double-check its performance and that of a few other plugins as well.
Surnia Ulula has switched to a lighter and more responsive theme. The theme is called Dazzling by Colorlib. I’ve made a few changes to the default stylesheet, but this is certainly not the end — just the beginning. ;-) Let me know what you think, and if you see any styling / layout issues, please let me know. :)
If you manage a DNS master, and push zones to several slaves / secondaries, you may have found that over time — as configuration files and firewall rules change — one or more slaves may have lost its ability to update its zone files. Perhaps the slave is no longer being notified, or it may have lost the necessary zone transfer permissions from the master. In a large distributed environment where DNS changes are frequent, checking the SOA serial number for all the NS servers in a zone can be quite helpful — a quick way to eliminate the DNS as a possible source of a problem. Here is a perl script I wrote a few years back to retrieve the SOA serial number for a given domain.