We are happy to announce that version 3.17 of the Parse.ly plugin will become available in VIP staging environments on Tuesday, November 12, 2024. Before using it in production, we recommend testing the new release in staging.
This release will become the default in production on Tuesday, November 19, 2024, and all non-pinned environments will be auto-upgraded to this version. These changes do not affect customers who don’t use wp-parsely, or use an integration method outside of mu-plugins.
What’s new
In terms of features, the Excerpt Suggestions tool is now accessible through the Content Helper Sidebar in the Post Editor, and it’s now possible to customize the tone and persona of the suggested excerpts.
As we’re preparing to introduce more features into the Content Helper, this is mainly a maintenance release geared towards making our codebase more flexible and easily maintainable. We’ve done this by:
Refactoring our WP REST API endpoints.
Adding more tests, making our integration tests run against PHP 8.4, and migrating our E2E tests to Playwright.
Using Composer autoloader and creating a new plugin release workflow.
Making a handful of smaller adjustments and fixing a couple of issues.
The WordPress 6.7 Release Candidate 1 is now available on WordPress VIP. Use the Software Management page to update your non-production sites to WordPress 6.7 for testing.
What’s Changing?
Testing this release candidate is the next step in preparing your site for the WordPress 6.7 release slated for Nov 12, 2024.
How to test WordPress 6.7
Local Environment
Ensure VIP-CLI is updated: npm update -g @automattic/vip
Alternatively, you may update a non-production site to WordPress 6.7 RC1 now.
Within the Software Management section of the VIP Dashboard, you can select your non-production environment and change the WordPress version to “6.7″ within the “Testing” section.
Testing is vital to polishing the release during the Release Candidate and a great way to contribute. ✨
Not for Production Environments
WordPress VIP does not recommend using Release Candidate or Beta versions in production environments. Any sites that have managed updates will automatically be updated to WordPress 6.7 when released on Nov 12.
Questions?
If you have testing feedback or questions related to this release, please open a support ticket, and we will be happy to assist.
WordPress 6.7 Beta is now available. This is the first beta released as part of the 6.7 development cycle and can be deployed to non-production environments in your WordPress VIP dashboard.
The current target for the final release is November 12, 2024
What is being added or changed?
Zoom Out to Compose with Patterns
The Zoom Out view simplifies your editing experience by allowing you to create and edit at the pattern level rather than focusing on individual blocks. Easily toggle this view from the toolbar to streamline your site-building process, making it faster and more intuitive to design pages using patterns.
Preview Options API
The latest WordPress release enhances the Preview Options in the block editor, empowering developers to customize content previews. A new API allows plugins and themes to add custom items to the preview dropdown menu, enabling users to see content in different formats or environments. This flexibility enriches the editing experience while maintaining the existing familiar Preview dropdown structure.
Manage Block Bindings Directly
Updates to this API in 6.7 polish and open most of the underlying APIs, improving the overall user experience, and add a user interface (UI) that allows you to connect attributes with custom fields to their binding sources. This new UI makes it possible to create bindings directly in a block instead of needing to use the Code Editor. By default admin and editor users can create and modify bindings, but this can be overridden with `block_editor_settings_all or map_meta_cap` filters.
Simplified and Smarter Query Loop Block
The Query Loop block is improved, as it now automatically inherits the query from the template by default, eliminating the need for manual configuration. This means your posts display immediately in both the editor and on the front end, streamlining the process so users can focus on content without extra configuration needed.
Jetpack 13.9-beta is available now for testing and the download link is available here
Jetpack 13.9 will be deployed to VIP on Wednesday, October 16, 2024*. The upgrade is expected to be performed at 17:00 UTC (1:00PM ET).
*This deployment date and time are subject to change if issues are discovered during testing of the Jetpack release.
A full list of changes is available in the commit log.
What is being added or changed?
Major Enhancements
Jetpack plugin: Remove the 'WordPress.com Toolbar' module.
Enhancements
Blocks: Transition from an option to a module to improve caching.
My Jetpack: Visual update to the GlobalNotice component for better mobile presentation.
Performance: Set the concatenated CSS to off by default. The era where this was helpful is passing.
Improved compatibility
Dashboard: Disable portfolio toggle if theme supports portfolio for specific environments.
Bug fixes
Shortcode: Fix the YouTube URL for the /embed type.
Subscriptions: Fix added slashes in the Follow Blog widget.
What do I need to do?
We recommend the below:
<ol>
<li>Installing the release on your non-production sites using <a href="https://docs.wpvip.com/how-tos/jetpack/version-updates/#h-pinning-to-a-version" target="_blank">these instructions</a>.</li>
<li>Running through the testing flows outlined in the <a href="https://github.com/Automattic/jetpack/blob/trunk/projects/plugins/jetpack/to-test.md" target="_blank">Jetpack Testing Guide</a>.</li>
</ol>
As you're testing, there are a few things to keep in mind:
<ul>
<li>Check your browser's <a href="https://wordpress.org/documentation/article/using-your-browser-to-diagnose-javascript-errors/" target="_blank">JavaScript console</a> and see if there are any errors reported by Jetpack there.</li>
<li>Use <a href="https://docs.wpvip.com/how-tos/enable-query-monitor/" target="_blank">Query Monitor</a> to help make PHP notices and warnings more noticeable and report anything you see.</li>
</ul>
<h2>Questions?</h2>
If you have any questions, related to this release, please <a href="https://docs.wpvip.com/technical-references/vip-support/" target="_blank">open a support ticket</a> and we will be happy to assist.
Starting Monday, October 7, 2024, all users who sign in to the VIP Dashboard with GitHub or WordPress.com will be required to upgrade their accounts to use VIP Authentication.
As outlined in our previous post, we’ll be rolling out VIP Authentication on October 7 to all VIP Dashboard users who sign in with GitHub and WordPress.com. This post will walk you through the new features, the upgrade process, and important dates to ensure a smooth transition.
Users who sign in with Single Sign-On (SSO) will see an updated VIP Dashboard login page, but will otherwise not be affected by these changes and do not need to take any action.
What’s new
Updated login page: We’ve simplified the VIP Dashboard login page to streamline your login experience.
Multiple authentication methods: VIP Authentication offers the same Multi-Factor Authentication (MFA) methods to verify your identity: passkeys, authenticator app, and SMS. Additionally, we require you to set up backup codes alongside your primary MFA method as an alternative verification option.
MFA Management tool: Our new MFA Management tool gives you full control over your account’s security directly from the VIP Dashboard. Add additional MFA methods as a secure alternative to your primary method, edit or remove existing methods, regenerate backup codes, and set your preferred MFA method—all from one place.
Email alerts: Receive emails for every MFA action you take for increased visibility and security around your account. Emails are sent from [email protected] to the email address set in your GitHub or WordPress.com account.
Reauthentication: We’ll prompt you to verify your identity again before performing sensitive actions, like viewing the MFA Management tool, to ensure your account is always protected.
Upgrade timeline
Users who sign in with GitHub or WordPress.com will need to upgrade their VIP Dashboard accounts to use VIP Authentication. We want to make this transition as smooth as possible for all users. Here’s the timeline for the transition:
Opt-in period: [Currently ongoing] VIP Authentication is available to a limited group of users for feedback.
Mandatory upgrade: [Monday, October 7, 2024] All users will be required to upgrade to VIP Authentication.
We expect all users to have upgraded by February 2025, when legacy authentication methods will be deprecated. Users who haven’t upgraded will lose permissions to their VIP Dashboard account and will need to reach out to their Org Admin to reinstate permissions.
How to upgrade
Starting Monday, October 7, 2024, all users who sign in with GitHub and WordPress.com will be required to upgrade their VIP Dashboard accounts to VIP Authentication. Upgrading to the new system is simple. Here’s how:
If you’re already logged in to the VIP Dashboard
While logged in to the VIP Dashboard, you will see a VIP Authentication banner at the top of your screen. Click on “Upgrade Now”
Alternatively, access the Settings page by clicking on your profile picture on the top right, and selecting “Settings”. Click on “Upgrade your MFA” in the left sidebar.
In the next screen, you will see more information about VIP Authentication. Click on “Get Started” to continue.
You may be prompted by WordPress.com or GitHub to authorize the VIP Dashboard access to your account information.
Once authorized, verify your identity using your current VIP Cloud multi-factor authentication (MFA) method.
You will land in the new VIP Authentication setup screen. Select either a Passkey, an Authenticator app, or SMS as your new authentication method to set up.
After the setup, make sure to save your backup codes in a safe place.
And that’s it! Once VIP Authentication is set up, you can add or edit authentication methods directly from the VIP Dashboard Settings page.
Log in to the VIP Dashboard using WordPress.com or GitHub as you normally would.
You will be prompted by WordPress.com or GitHub to authorize the VIP Dashboard access to your account information.
Once authorized, verify your identity using your current VIP Cloud multi-factor authentication (MFA) method.
You will then land in the new VIP Authentication setup screen. Select either a Passkey, an Authenticator app, or SMS as your new authentication method to set up.
After the setup, make sure to save your backup codes in a safe place.
And that’s it! Once VIP Authentication is set up, you can add or edit authentication methods directly from the VIP Dashboard Settings page.
FAQs
Q: What if I don’t want to upgrade right now?
A: Starting October 7, 2024, upgrading your account will be required for all users who sign in with GitHub and WordPress.com. You won’t be able to bypass this update, and we recommend upgrading as soon as possible to avoid any disruptions and to take full advantage of the security enhancements and new features. Once you’ve upgraded, logging in will feel almost the same as before, with the added benefits of the new system working seamlessly behind the scenes.
Users that are logged out of the VIP Dashboard will be taken through the upgrade process upon log in. If you’re currently logged in to the VIP Dashboard, you can start the upgrade process by clicking on the “Upgrade now” banner that will be displayed starting October 7th.
Q: Can I rollback the upgrade if I run into issues?
A: No, rollbacks won’t be available. In the unlikely event you run into issues, please contact us, and we’ll be happy to help.
Q: What happens if I don’t upgrade in time?
A: Permissions for your VIP Dashboard user account will be revoked, and you will not be able to view any applications or organizations you previously had access to. You will have to reach out to your Org Admin to reinstate your permissions. You will need to set up MFA on VIP Authentication once your permissions are reinstated.
Q: Why do I need to do this?
A: Security is at the core of WordPress VIP. We’re increasing security measures to provide stronger protection for your account, expanding authentication options for redundancy and resilience, increasing visibility into your account actions, and adding an additional layer of security for sensitive actions.
We’re providing tools to help you have more control over your MFA methods, along with an improved UI to make logging into the VIP Dashboard both safer and more intuitive at the same time.
Q: I use SSO to sign in. Do I need to upgrade as well?
A: No, users who sign in with Single Sign-On (SSO) are not affected by these changes and do not need to upgrade their accounts. However, the VIP Dashboard login page will be updated for all users, including those using SSO.
If you are an Org Admin user signing in with SSO, you will still receive communications about changes that may affect other users in your organization.
Q: What are passkeys, and should I use them?
A: Passkeys are a secure and convenient Multi-Factor Authentication (MFA) method. They allow you to authenticate by using devices like YubiKeys, your phone, or other options supported by your browser. We encourage you to try them for a smoother and quicker authentication experience!
Q: Can I add more than one MFA method?
A: Yes! You can add multiple MFA methods through the MFA Management tool. We encourage you to add additional MFA methods in case you lose access to your primary method.