Skip to content

Remove support for obsolete Google Web Light#58444

Closed
westonruter wants to merge 1 commit intowoocommerce:trunkfrom
westonruter:remove/googleweblight
Closed

Remove support for obsolete Google Web Light#58444
westonruter wants to merge 1 commit intowoocommerce:trunkfrom
westonruter:remove/googleweblight

Conversation

@westonruter
Copy link
Copy Markdown
Contributor

Changes proposed in this Pull Request:

This removes support for Google Web Light which was introduced in #26858 and 9f61045. The Google Web Light service was shut down in 2022 per Wikipedia:

On December 19, 2022, Google announced that it discontinued the Web Light service by removing the documentation and retiring the Web Light user agent. Increased affordability of more powerful smartphones was cited as the reason for this decision.[5]

See also the update from Google Search Central:

December 19: Removed the Web Light documentation and retired the Web Light user agent. We introduced Web Light to enable us to serve faster, lighter pages to people searching on entry-level devices. While this feature has worked as intended and enabled broader access to the richness of the web, increased affordability of more powerful smartphones has diminished the need for such functionality. We remain committed to evolving and refining the Search experience to meet the changing needs of our users.

So this is removing technical debt.

Changelog entry

  • Automatically create a changelog entry from the details below.
  • This Pull Request does not require a changelog entry. (Comment required below)
Changelog Entry Details

Significance

  • Patch
  • Minor
  • Major

Type

  • Fix - Fixes an existing bug
  • Add - Adds functionality
  • Update - Update existing functionality
  • Dev - Development related task
  • Tweak - A minor adjustment to the codebase
  • Performance - Address performance issues
  • Enhancement - Improvement to existing functionality

Message

Changelog Entry Comment

Comment

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jan 14, 2026

Warning

Rate limit exceeded

@jorgeatorres has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 8 minutes and 0 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 4697b87 and 33c6961.

📒 Files selected for processing (1)
  • plugins/woocommerce/includes/class-wc-cache-helper.php

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@woocommercebot woocommercebot requested review from a team and jorgeatorres and removed request for a team January 14, 2026 15:21
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 14, 2026

Testing Guidelines

Hi ,

Apart from reviewing the code changes, please make sure to review the testing instructions (Guide) and verify that relevant tests (E2E, Unit, Integration, etc.) have been added or updated as needed.

Reminder: PR reviewers are required to document testing performed. This includes:

  • 🖼️ Screenshots or screen recordings.
  • 📝 List of functionality tested / steps followed.
  • 🌐 Site details (environment attributes such as hosting type, plugins, theme, store size, store age, and relevant settings).
  • 🔍 Any analysis performed, such as assessing potential impacts on environment attributes and other plugins, conducting performance profiling, or using LLM/AI-based analysis.

⚠️ Within the testing details you provide, please ensure that no sensitive information (such as API keys, passwords, user data, etc.) is included in this public issue.

@jorgeatorres
Copy link
Copy Markdown
Member

Closing as this was already merged as part of #58445.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

plugin: woocommerce Issues related to the WooCommerce Core plugin. type: community contribution

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants