Pinterest Rich Pins have adopted the Open Graph standard, except for the ‘article:author’ meta tag value. The Open Graph standard expects the ‘article:author’ to be a profile URL or profile ID, where-as Pinterest expects a person’s name instead (and ignores any URL values). To correct this incompatibility, a new Pinterest publisher settings tab has been added to the SSO General settings page, with an option to include an author’s name specifically for the Pinterest crawler. The default value includes the author’s ‘Display Name’, but you may also choose the author’s ‘First and Last Names’ or ‘Nickname’ instead.
If you use a full-page caching front-end or plugin (Quick Cache, etc.), see the Performance Tuning notes about caches and Pinterest meta tags. Continue reading…
Recently, I needed to sync several directories on a backup / fail-over server with the same directories on a production server. Rsync over SSH takes care of this, but if you want to tighten security, you must use the “command” restriction in the SSH authorized_keys file — This restricts the authenticated key to running a single command, with a specific set of arguments. For example, let’s look at a typical command that might be run from a backup server to rsync daily database dumps:
backup$ rsync -av --delete -e "ssh -i $HOME/.ssh/prod-rsync-key" \
NGFB Open Graph+ can recognize and parse standard object / iframe embed code, but some themes and plugins offer a custom field for video URLs, which is then used to create custom / non-standard embed code. Version 7.1 includes a new ‘Video URL Custom Field’ option on the Advanced settings page, under the Custom Settings tab, where you can enter the name of such a custom field. If found, the video URL will be used to retrieve information on that video, just like if it was found embedded in the content. Typically, the custom field name will start with an underscore, and the default ‘Video URL Custom Field’ name is “_format_video_embed” (which may or may not be supported by your theme, or may be known under a different name).
Nginx Inc. provides access to the nginx-plus package and repository using SSL certificates. Their instructions cover the configuration of apt for Ubuntu, but for people using apt-mirror and Puppet to manage their internal servers, additional custom configurations are required.
The standard apt configuration for nginx-plus might look like this:
$ cat /etc/apt/apt.conf.d/90nginx
The connection to the nginx-plus repository must be made using HTTPS and authentication is handled by client certificates. As provided, apt-mirror is not able to manage SSL certificates, so two sections in the apt-mirror script must be modified. The
%config_variables array defines the settings read from its configuration files. We will add the ‘certificate’, ‘private_key’, and ‘ca_certificate’ settings to the array.
If you are concerned about the quality of your NextGEN Gallery v2.x resized images, this should be of particular interest to you.
Some months ago I contacted Photocrati to ask them how, in version 2.x, developers could retrieve the “actual” dimensions of a resized image. In the past, after resizing an image we could use PHP’s getimagesize() function on the resulting file, but in v2.x image resizing is dynamic and those resized images may not be available on disk. I had some concerns between the expected / calculated image dimensions, those returned by NGG v2.x’s methods / functions, and the actual image retrieved by the URL. All 3 dimensions were different! A resized uncropped image which should have been 300x200px, was reported as being 300x199px by the NGG methods / functions, and the image retrieved by URL was 298x199px!
This may not sound like much, but a few pixels here and there can lead to image distortion when rendered by browsers, alignment issues in page layouts, and failures when working with minimum image dimensions (for example, Facebook ignores images smaller than 200x200px).
Please note that support for NextGEN Gallery will be moved to the NGFB Open Graph+ Pro version in v6.21.0.
This will restore balance between the two versions – the GPL version has complete support for all Open Graph+ meta tags and WordPress features, including its gallery shortcode.
3rd party plugin support, like NextGEN Gallery, WordPress SEO, BuddyPress, bbPress, WooCommerce, and many more, is available in the Pro version.
I remain committed to providing a reliable and complete set of features in the GPL version – for free. There’s no need to contribute in any way, though a little help with forum questions is always welcome. ;-)