Changes between Initial Version and Version 4 of Ticket #3211
- Timestamp:
- 12/03/2018 08:28:48 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #3211
- Property Summary Shim favs/subs back-combat via BBP_User_Engagements_Base → Shim favs/subs back-compat via BBP_User_Engagements_Base
-
Ticket #3211 – Description
initial v4 1 In 2.6, we changed the way that engagements are stored in the DB. There is a migration script for small bbPress installs (with less than 10k users) but there is no back-com bat for larger installs that haven't upgraded yet.1 In 2.6, we changed the way that engagements are stored in the DB. There is a migration script for small bbPress installs (with less than 10k users) but there is no back-compat for larger installs that haven't upgraded yet. 2 2 3 We should extend `BBP_User_Engagements_Base` and provide back-com bat for favorites & subscriptions to provide backwards compatibility to large 2.5 installations.3 We should extend `BBP_User_Engagements_Base` and provide back-compat for favorites & subscriptions to provide backwards compatibility to large 2.5 installations. 4 4 5 5 We'd do this by setting the "engagements strategy" in `bbPress::setup_variables()` based on the database version. Right now, we've hard-coded it to use the new one (`BBP_User_Engagements_Meta`) but we'd selectively use the back-compat one if until the database upgrade is completed.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)