Timeline for WordPress core code contains things marked as deprecated by... Wordpress?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 19, 2018 at 13:47 | comment | added | Pat J |
It doesn't look like it. I had hopes for the deprecated_function_trigger_error filter, but it appears to globally turn deprecation notices on or off, instead of allowing you to pick and choose the notices to suppress.
|
|
| Mar 19, 2018 at 8:23 | comment | added | trejder | Can I (at all or how?) mute notices thrown by only this single plugin? Or is it either all notices (muted) or none? | |
| Mar 18, 2018 at 18:19 | comment | added | Pat J | I'd say you've got two paths to choose from: a) fork the plugin and replace the deprecated function calls with the recommended replacements, or b) make the conscious choice to ignore the Notices thrown by the plugin. | |
| Mar 15, 2018 at 22:14 | comment | added | trejder | You are -- of course -- correct. The sad thing here is that faulty plugin is "WordPress MU Domain Mapping". It is no longer updated, because it is no longer needed. However, I must keep using it, because cited counter-solution requires: (a) a clean install and (b) a dedicated IP address. Both things not possible in my case. | |
| Mar 15, 2018 at 22:12 | vote | accept | trejder | ||
| Mar 13, 2018 at 21:20 | history | answered | Pat J | CC BY-SA 3.0 |