Skip to content

[Step 2] mu-wpcom: remove the COLOURLovers Customizer deprecation notice#50012

Open
Copons wants to merge 1 commit into
dotcom-1758-stop-the-colourlovers-feature-from-workingfrom
dotcom-1758-remove-colourlovers-deprecate-notice
Open

[Step 2] mu-wpcom: remove the COLOURLovers Customizer deprecation notice#50012
Copons wants to merge 1 commit into
dotcom-1758-stop-the-colourlovers-feature-from-workingfrom
dotcom-1758-remove-colourlovers-deprecate-notice

Conversation

@Copons

@Copons Copons commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

⚠️ Stacked on #50011 — review/merge that one first. Base is set to the PR1 branch, so this diff shows only the deprecation-notice removal.

Proposed changes

  • Remove the wpcom-colourlovers-deprecate feature — the Customizer notice that asked users to update their COLOURLovers background image before the deprecation deadline. COLOURLovers support has been discontinued and the deadline has passed, so the warning is stale. [Step 1] Custom colors: stop serving discontinued COLOURLovers backgrounds #50011 already blanks COLOURLovers backgrounds at render time.
  • Deletes the feature's PHP + JS and its loader line in class-jetpack-mu-wpcom.php.

Related product discussion/links

Does this pull request change what data or activity we track or use?

No.

Testing instructions

  • Build jetpack-mu-wpcom and deploy to an Atomic site.
  • On a site that has a COLOURLovers background image set, open the Customizer → confirm the "update your background image" deprecation notice no longer appears.
  • Confirm the site loads without errors and function_exists( 'wpcom_colourlovers_deprecate_warning' ) is false.

COLOURLovers support has been discontinued and the deprecation deadline has passed, so the Customizer warning that asked users to update their background image is now stale. PR1 already blanks COLOURLovers backgrounds at render. Remove the wpcom-colourlovers-deprecate feature (PHP + JS) and its loader in class-jetpack-mu-wpcom.php.
@github-actions

github-actions Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (WordPress.com Site Helper), and enable the dotcom-1758-remove-colourlovers-deprecate-notice branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack-mu-wpcom-plugin dotcom-1758-remove-colourlovers-deprecate-notice

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • 🔴 Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

@github-actions github-actions Bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Jun 26, 2026
@Copons Copons requested a review from Copilot June 26, 2026 16:55
@Copons Copons self-assigned this Jun 26, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Removes the now-stale COLOURLovers background deprecation notice feature from jetpack-mu-wpcom, including its PHP/JS implementation and loader hook, and records the removal in the project changelog. This aligns with COLOURLovers support being discontinued and the deadline having passed (with related behavior already handled in stacked PR #50011).

Changes:

  • Delete the wpcom-colourlovers-deprecate feature PHP and its Customizer warning script.
  • Stop loading the removed feature from Jetpack_Mu_Wpcom::load_wpcom_user_features().
  • Add a jetpack-mu-wpcom changelog entry documenting the removal.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
projects/packages/jetpack-mu-wpcom/src/features/wpcom-colourlovers-deprecate/wpcom-colourlovers-deprecate.php Removes the PHP hook that enqueued/localized the Customizer deprecation warning.
projects/packages/jetpack-mu-wpcom/src/features/wpcom-colourlovers-deprecate/js/colourlovers-deprecated-message.js Removes the Customizer UI notification logic for the deprecated COLOURLovers background warning.
projects/packages/jetpack-mu-wpcom/src/class-jetpack-mu-wpcom.php Removes the require_once loader line for the deleted feature.
projects/packages/jetpack-mu-wpcom/changelog/dotcom-1758-remove-colourlovers-deprecate-notice Adds a changelog entry documenting the removal of the stale Customizer notice.

@jp-launch-control

Copy link
Copy Markdown

Code Coverage Summary

No summary data is available for parent commit 62905de, so cannot calculate coverage changes. 😴

If that commit is a feature branch rather than a trunk commit, this is expected. Otherwise, this should be updated once coverage for 62905de is available.

Full summary · PHP report · JS report

@Copons Copons changed the title mu-wpcom: remove the COLOURLovers Customizer deprecation notice [Step 2] mu-wpcom: remove the COLOURLovers Customizer deprecation notice Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[mu wpcom Feature] Wpcom Colourlovers Deprecate [Package] Jetpack mu wpcom WordPress.com Features [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants