WordPress.org
Get WordPress

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #57643, comment 4


Ignore:
Timestamp:
02/06/2023 02:36:59 PM (2 years ago)
Author:
hellofromTonya
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #57643, comment 4

    initial v1  
    33@azaozz [https://github.com/WordPress/wordpress-develop/pull/3775#issuecomment-1405916513  summarized options here] (copying since the PR was linked after the comment):
    44
    5 As far as I see it there are three options here:
    6 
    7 1. Remove `wp-nux` completely from everywhere, including scritp-loader. Scripts that still depend on `wp-nux` will not be loaded, so the plugins that add them will not work. As `wp-nux` has been deprecated and throwing errors for quite some time, it's very likely that these plugins haven't been working for years.
    8 2. Add stubs for the public methods in `wp_nux` and keep it in script-loader. Some features in plugins that use it as a dependency will not work (this has been the case for over two years anyway), but other things there (if any) may still work.
    9 3. Leave the JS for `wp-nux` in place, remove the CSS. This is pretty similar to number two as `wp-nux` has been throwing js errors for a long time, i.e. plugins that are using it as a dependency haven't been working properly anyway.
    10 
    11 Assuming that `wp-nux` have been causing errors and not working for over two years, perhaps option 1 seems most desirable? Then monitor bug reports during WP 6.2 beta and RC (that's nearly two months) and if there are many affected plugins and themes switch to option 3?
     5>As far as I see it there are three options here:
     6>
     7>1. Remove `wp-nux` completely from everywhere, including scritp-loader. Scripts that still depend on `wp-nux` will not be loaded, so the plugins that add them will not work. As `wp-nux` has been deprecated and throwing errors for quite some time, it's very likely that these plugins haven't been working for years.
     8>2. Add stubs for the public methods in `wp_nux` and keep it in script-loader. Some features in plugins that use it as a dependency will not work (this has been the case for over two years anyway), but other things there (if any) may still work.
     9>3. Leave the JS for `wp-nux` in place, remove the CSS. This is pretty similar to number two as `wp-nux` has been throwing js errors for a long time, i.e. plugins that are using it as a dependency haven't been working properly anyway.
     10>
     11>Assuming that `wp-nux` have been causing errors and not working for over two years, perhaps option 1 seems most desirable? Then monitor bug reports during WP 6.2 beta and RC (that's nearly two months) and if there are many affected plugins and themes switch to option 3?