New Release: Brightcove Video Connect 1.7.2

This notice relates to the following platforms: VIP Go, WordPress.com VIP

A new version of the Brightcove Video Connect plugin has been committed to the WordPress.com shared plugins repository. Changes in this release include the following:

  • Fix: iFrame Padding issue
  • Fix: Stop showing inactive players from Brightcove studio in the plugin
  • Fix: Source select account bug

We encourage all sites using the Brightcove Video Connect plugin to upgrade to this new version.

To update:

On WordPress.com VIP, set the version parameter in wpcom_vip_load_plugin() like so:

wpcom_vip_load_plugin( 'brightcove-video-connect', 'plugins', '1.7.2' );

For VIP Go, add the latest reviewed version (v.1.7.2) to your plugins folder in your sites GitHub repository. The plugin can be downloaded from the WordPress.org repository.

If you have any questions, please open a ticket where we’ll be happy to assist you into transitioning to the latest version.

Ooyala v3.1 now available

This notice relates to the following platforms: WordPress.com VIP, VIP Go

A new version of the Ooyala plugin has been committed to the shared plugins repository. v3.1 is a feature release. Changes include:

  • Adding integration with Google AMP
  • Add integration with Facebook Instant Articles
  • Bugfixes for Jetpack Infinite Scroll

We encourage all VIPs using Ooyala to upgrade to this version by specifying the version parameter of wpcom_vip_load_plugin() like so:

wpcom_vip_load_plugin( 'ooyala', 'plugins', '3.1' );

For VIP Go, you can take advantage of the new version by updating to use the reviewed version (v3.1.0) from the WordPress.org Plugins repository.

If you have any questions please open a ticket where we’ll be happy to assist you transition to the newest version.

New Release: Co-Authors Plus 3.4

This notice relates to the following platforms: VIP Go, WordPress.com VIP

A new version of the Co-Authors Plus plugin has been committed to the WordPress.com shared plugins repository.

This adds several improvements and bug fixes including the below:

  • Added new filters get_coauthors for modifying coauthor data returned in get_coauthors(), coauthors_guest_authors_exported_extra_data to allow guest author to export data as regular author and get_avatar_url() to show in JS selection
  • Internationalization support for title and name in author archives
  • Fixed bug of coauthors_links_single() template tag displaying correctly when guest author has no website
  • Fixed bug of the number by “Mine” link showing incorrect listing of posts
  • Fixed bug of linked guest authors and users with different login names show inaccurate post counts
  • Fixed bug of being able to add co-author more than once
  • Fixed bug of being unable to delete users properly when guest authors functionality disabled
  • Fix incompatibility issue with Yoast of missing posts in author pages

To see all the fixes, please see the official changelog. We encourage all sites using the Co-Authors Plus plugin to upgrade to this new version.

To update:

On WordPress.com VIP, set or update the version in use by setting the version parameter in wpcom_vip_load_plugin() like so:

wpcom_vip_load_plugin( 'co-authors-plus', 'plugins', '3.4' );

For VIP Go, you can take advantage of the new version by replacing the old version with the latest reviewed version (v3.4) to your plugins folder in your sites GitHub repository. The plugin can be downloaded from GitHub.

If you have any questions please open a ticket where we’ll be happy to assist you into transitioning to the latest version.

New Release: Add SEO Meta Tags 2.0

This notice relates to the following platforms: VIP Go, WordPress.com VIP

A new version of the Add SEO Meta Tags plugin has been committed to the WordPress.com shared plugins repository.

This is a rewrite of the original plugin (Add Meta Tags Mod) with some UI improvements and the following changes:

  • New control panel location under “Settings” > “SEO Options”
  • Removed the filter mt_seo_title_append_separator
  • Added new filters:
    • amt_title_length
    • amt_metatags_array
    • amt_get_the_categories
    • amt_get_the_tags
    • amt_get_all_the_categories
    • amt_supported_post_types
    • amt_registered_post_types

We encourage all sites using the Add Meta Tags Mod plugin to upgrade to this new version.

To update:

On WordPress.com VIP, set or update the version in use by setting the version parameter in wpcom_vip_load_plugin() like so:

wpcom_vip_load_plugin( 'add-meta-tags-mod', 'plugins', '2.0' );

For VIP Go, you can take advantage of the new version by adding the latest reviewed version (v2.0) to your plugins folder in your sites GitHub repository. The plugin can be downloaded from GitHub.

If you have any questions please open a ticket where we’ll be happy to assist you into transitioning to the latest version.

New Release: Sailthru 3.3

This notice relates to the following platforms: VIP Go, WordPress.com VIP

A new version of the Sailthru plugin has been committed to the WordPress.com shared plugins repository.

This adds a number of new options to the UI to help customers manage their content without requiring development work:

  • Add ability to combine WordPress tags with Sailthru interest tags via a UI setting
  • Added ability to combine categories with Sailthru interest tags via a UI setting
  • Added ability to add any available taxonomy to Sailthru tags via the UI.
  • Added a global whitelist of vars to be included in content api posts
  • Added a global tag option so a tag can be added to every post
  • Added ability to turn on/off Content API syncing via the UI

We encourage all sites using the Sailthru plugin to upgrade to this new version.

To update:

On WordPress.com VIP, set or update the version in use by setting the version parameter in wpcom_vip_load_plugin() like so:

wpcom_vip_load_plugin( 'sailthru', 'plugins', '3.3' );

For VIP Go, you can take advantage of the new version by adding the latest reviewed version (v.3.3) to your plugins folder in your sites GitHub repository. The plugin can be downloaded from the WordPress.org repository.

If you have any questions please open a ticket where we’ll be happy to assist you into transitioning to the latest version.

New Release: Expiring Posts 1.2

This notice relates to the following platforms: VIP Go, WordPress.com VIP

A new version of the Expiring Posts plugin has been committed to the WordPress.com shared plugins repository. The plugin has long been used to set the post status of a post to “expired” on a specified date.

This is a minor update which includes the addition of the exp_disable_expiration_for_this_post filter to allow the post expiry to be conditionally controlled

We encourage all sites using the Expiring Posts plugin to upgrade to this new version.

To update:

On WordPress.com VIP, set or update the version in use by setting the version parameter in wpcom_vip_load_plugin() like so:

wpcom_vip_load_plugin( 'expiring-posts', 'plugins', '1.2' );

For VIP Go, you can take advantage of the new version by adding the latest reviewed version (v.1.2) to your plugins folder in your sites GitHub repository. The plugin can be downloaded from the WordPress.org repository or GitHub.

If you have any questions please open a ticket where we’ll be happy to assist you into transitioning to the latest version.

New Release: Edit Flow 0.9

This notice relates to the following platforms: VIP Go, WordPress.com VIP

A new version of the Edit Flow plugin has been committed to the shared plugins repository. This update includes multiple enhancements and bug fixes:

  • Implement Block Editor compatibility for Custom Status module.
  • New filter ef_calendar_item_html for Calendar module that allows to print custom markup for each day
  • Add [NO ACCESS] and [NO EMAIL] to the list of notified users to indicate that a user doesn’t have the access to the post and that a user doesn’t have an email set, respectively.

We encourage all VIPs using Edit Flow plugin to upgrade to the latest available. On WordPress.com VIP platform, it can be done by specifying the version parameter of wpcom_vip_load_plugin() like so:

wpcom_vip_load_plugin( 'edit-flow', 'plugins', '0.9' );

For VIP Go, you can take advantage of the new version by adding the latest reviewed version (v.0.9) to your plugins folder. The plugin can be downloaded from the WordPress.org Plugins repository. or Automattic GitHub repository.

If you have any questions please open a ticket where we’ll be happy to assist you into transitioning to the newest version.

New Release: Safe Redirect Manager 1.9.2

This notice relates to the following platforms: WordPress.com VIP, VIP Go

A new version of the Safe Redirect Manager plugin has been committed to the shared plugins repository. This update includes multiple enhancements and bug fixes:

  • Enhancement: Added redirect notes feature and custom redirect capability.
  • Enhancement: Added filters for request path and redirect path and to only apply redirects on 404.
  • Fix: No more PHP 7.2 errors.
  • Fix: No more broken HTML and root redirect in subdirectory bug.

We encourage all VIPs using Safe Redirect Manager plugin to upgrade to the latest available. On WordPress.com VIP platform, it can be done by specifying the version parameter of wpcom_vip_load_plugin() like so:

wpcom_vip_load_plugin( 'safe-redirect-manager', 'plugins', '1.9' );

For VIP Go, you can take advantage of the new version by adding the latest reviewed version (v.1.9.2) to your plugins folder. The plugin can be downloaded from the WordPress.org Plugins repository.

If you have any questions please open a ticket where we’ll be happy to assist you into transitioning to the newest version.

New Release: Getty Images 4.0

This notice relates to the following platforms: WordPress.com VIP, VIP Go

A new version of the Getty Images plugin is now available to WordPress.com VIP clients. Getty Images v4.0 is a feature release that adds Gutenberg block support.

We encourage all VIPs using Getty Images to upgrade to this version by specifying the version parameter of wpcom_vip_load_plugin() like so:

wpcom_vip_load_plugin( ‘getty-images’, ‘plugins’, ‘4.0’ );

This also means that we are now deprecating v2.5 and intend to remove the plugin on January 3, 2019. Getty Images v3.0 will remain available for those who want to use it, but we strongly encourage you to upgrade to v4.0.

As we approach the removal date for v2.5, we’ll contact any VIPs still loading that version to help you update any themes that haven’t migrated by that date.

For VIP Go, you can take advantage of the new version by adding the latest reviewed version (v.4.0) to your plugins folder. The plugin can be downloaded from WordPress.org.

If you have any questions please open a ticket where we’ll be happy to assist your transition to the newest version.

Gutenberg users: Stay current with the plugin ahead of WordPress 5.0

This notice relates to the following platforms: VIP Go

As previously announced, the WordPress 5.0 update is targeting a November 19th merge. Many of you are already using the Gutenberg plugin (loaded by Ramp) on your sites, and we applaud you! We specifically built Ramp to support the development needs of those early adopters of Gutenberg, as well as maximize the opportunity to test out the new editor. However, as we near the WordPress 5.0 release, there is an action item for you early adopters:

Because of the way WordPress 5.0 loads the new editor (Gutenberg), all sites currently using the Gutenberg plugin must be using version 4.1 or higher. Gutenberg 4.1 release candidate is already available, and there is an expected UI freeze with this version. Gutenberg 4.2 is expected to signal the API freeze, and mark what is expected to be the final version of the editor that gets included in WordPress 5.0.

Recommended approach

To minimize risk of unexpected incompatibilities with the editor that ships in WordPress 5.0, we recommend getting your site updated to the latest version of the plugin now, and planning to update again with each incremental release. It’s imperative to be updated to at least Gutenberg 4.1 ahead of the WordPress 5.0 release, as previous versions will become incompatible.

Rather than waiting for Gutenberg 4.2 and just updating then, we recommend updating to 4.0 or 4.1 (release candidate available) now so you have more time to test this version and make any updates if needed. This is increasingly important for those currently running versions of the plugin that are more than a few releases behind (3.6 and older). Then, the update to 4.2 should be a very minimal update.

But everything will stay the same, right?

Yes! After the 5.0 merge, your editorial experience will stay the same. Gutenberg’s functionality will be opt-in for VIP clients.

For those that still haven’t tried out the new editing experience, you can try it out here to learn more about the block-based editing experience of the (near) future. If you decide you want to enable Gutenberg, you’ll be able to take advantage of our Ramp plugin, which allows you to selectively enable Gutenberg via post type or post ID.

For everybody, keep an eye out for future Lobby posts with more WordPress 5.0 details as well as VIP News for exciting things some of our clients are doing with the new editor.