Deprecate and remove the Recommendations Widget
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 66
- Forks
- 36
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Is your feature request related to a problem?
The Parse.ly plugin includes a Recommendation Widget, and since WordPress 5.8 it's possible to use blocks as a widget. Since this widget is pretty much the same - feature-wise - as the recommendation block, we can likely deprecate it and remove the widget.
Describe the solution you'd like
Remove the entire class-recommendation-widget.php file that contains the Recommended_Widget class.
Describe alternatives you've considered
If we want to deprecate the widget before actually removing it from the codebase, we could try to detect if it is in use, and recommend changing to the Recommended Block instead, and keep it for a few releases.
Alternatively, we could keep a striped down version of the recommended widget that would be a wrapper for the recommendation block - not sure how technically feasible this is, but might be worth exploring.
Additional context
The only caveat I see from this deprecation, is users that are using the Classic Widgets plugin. Although, accordingly to the plugin page, the plugin "will be supported and maintained to 2024, or as long as is necessary", so eventually the ability of using classic widgets will be entirely unsupported in WordPress.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with class-recommendation-widget.php, which contains the Recommended_Widget class, and check how the widget is registered or referenced before removing it. Confirm whether the intended outcome is immediate removal or deprecation first; done means the widget is no longer present while the recommendation block remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100