| 5 | | Unfortunately, from having done a lot of hours of testing and research, I don't think this is going to be possible to fix moving forward without backwards compatibility breaks. I would suggest those breaks still be made, but that this goes in first thing into 5.2, and it be announced to plugin developers straightaway so they have the entire cycle to make a very quick addition. Sadly while this would have been very easy to address & fix 7 years ago, doing so now is no longer as straightforward. |
| | 5 | Unfortunately, from having done a lot of hours of testing and research, I don't think this is going to be possible to fix moving forward a without backwards compatibility break, specifically the one the patch would make. I would suggest those breaks still be made, but that this goes in first thing into 5.2, and it be announced to plugin developers straightaway so they have the entire cycle to make a very quick addition. Sadly while this would have been very easy to address & fix 7 years ago, doing so now is no longer as straightforward. |