Yes I did, on February 3rd.
But at that moment, the change with the floating save button had not been implemented yet (that was the end of February, I think). There wasn’t an additional update in that topic or elsewhere to reflect those changes.
Any of these:
- a timely technical announcement targeted towards plugin developers
- temporary automatic fallback to the old logic (like has been done for the topic list, whenever there was legacy plugin code it automatically fell back).
- temporary fallback code that keeps the legacy functionality working (detect inputs outside forms and include them in the settings that need to be saved). That could have saved you guys the effort of all those
{{#if this.siteSettings.enable_simplified_category_creation}}branches as well. - browser development console warnings when legacy code is detected
- a static scan of known plugins, like I did yesterday (took me 10 minutes and I even found some official plugins that were overlooked
)
That would be much appreciated!