Changes between Initial Version and Version 1 of Ticket #8625, comment 3
- Timestamp:
- 01/29/2022 12:40:41 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #8625, comment 3
initial v1 1 1 Hi @r-a-y 2 2 3 Thanks for your report. Too bad we were not able to predict this scenario. Correct me if I'm wrong to see the issue happen, this means you are using the new Widgets Block Editor, otherwise BP Legacy Widgets would have been loaded.3 Thanks for your report. Too bad we were not able to predict this scenario. Correct me if I'm wrong: to see the issue happen, this means you are using the new Widgets Block Editor, otherwise BP Legacy Widgets would have been loaded. 4 4 5 So, if you are using the new Widgets Block Editor, you can now use the BP Widget Blocks we introduced in 9.0.0, simply by migrating the legacy one .5 So, if you are using the new Widgets Block Editor, you can now use the BP Widget Blocks we introduced in 9.0.0, simply by migrating the legacy ones. 6 6 7 7 The goal of deprecating BP Legacy Widgets is to avoid people who actually migrated to suffer from a bad user experience, see #8594 for more infos about this. 8 8 9 That being said, I agree we shouldn't that rough. We can be nicer without loading all BP Legacy widgets like your patch is doing. So a good compromise to me, is to carry on loading BP Legacy widgets that has been added to a sidebar (in other words: active).9 That being said, I agree we shouldn't be that rough. We can be nicer without loading all BP legacy Widgets like your patch is doing. So a good compromise to me, is to carry on loading BP Legacy widgets that has been added to a sidebar (in other words: active). 10 10 11 But I think we shouldcarry on the deprecation process. Please test the 8625.02.patch to confirm you can still load the BP legacy Widgets that are actives.11 But I think we need to carry on the deprecation process. Please test the 8625.02.patch to confirm you can still load the BP legacy Widgets that are actives. 12 12 13 13 About improving our documentation, I totally agree. We'll work on this during the next 4 to 6 months.