Make WordPress Core

Changes between Version 1 and Version 4 of Ticket #53993


Ignore:
Timestamp:
08/24/2021 09:24:20 PM (3 years ago)
Author:
sabernhardt
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #53993

    • Property Component changed from General to Widgets
  • Ticket #53993 – Description

    v1 v4  
    2929They don't support multiple instances and can be only used once. In addition, they don't benefit from the WP_Widget API.
    3030
    31 Widgets based on functions seem to be extremely uncommon and more of a BC artifact rather than a popular, actively used feature. They also [https://github.com/WordPress/gutenberg/issues/33104:required adding a lot of custom code into the new block-based widgets editor] and will continue to be a maintenance burden in the future.
     31Widgets based on functions seem to be extremely uncommon and more of a BC artifact rather than a popular, actively used feature. They also [https://github.com/WordPress/gutenberg/issues/33104 required adding a lot of custom code into the new block-based widgets editor] and will continue to be a maintenance burden in the future.
    3232
    33 In the Gutenberg repo there was a [https://github.com/WordPress/gutenberg/issues/33104:discussion about deprecating them to make life easier]. Now I'm opening this Trac issue so that we can either take action or decide against it.
     33In the Gutenberg repo there was a [https://github.com/WordPress/gutenberg/issues/33104 discussion about deprecating them to make life easier]. Now I'm opening this Trac issue so that we can either take action or decide against it.
    3434
    3535Technically speaking, I am not sure where to place the `_deprecated_function()` call. At first I thought about `wp_register_sidebar_widget` and company, but that API is internally used by `WP_Widget` itself: