Opened 9 years ago
Closed 8 years ago
#7502 closed defect (bug) (fixed)
Legacy forums do not work with WordPress 4.7
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 3.0 | Priority: | normal |
| Severity: | normal | Version: | 2.7.1 |
| Component: | Forums | Keywords: | has-patch |
| Cc: |
Description
WordPress 4.7 introduced the WP_Taxonomy class. BackPress also has a class called WP_Taxonomy.
But our legacy forum bridge code is throwing a fatal error because we are attempting to load the BackPress version of the WP_Taxonomy class when it already exists in WordPress 4.7 now. (Also both classes are entirely different, code-wise!)
Attached patch does a dirty workaround by doing the following:
- Copies the BackPress version of the
WP_Taxonomyclass and renames the class toBackPress_Taxonomy. - Copies the bbPress (v1) version of the
BB_Taxonomyclass and extends it to use our customBackPress_Taxonomyclass instead ofWP_Taxonomy.
Attachments (2)
Change History (12)
This ticket was mentioned in Slack in #buddypress by dcavins. View the logs.
9 years ago
This ticket was mentioned in Slack in #buddypress by r-a-y. View the logs.
8 years ago
This ticket was mentioned in Slack in #buddypress by r-a-y. View the logs.
8 years ago
This ticket was mentioned in Slack in #buddypress by djpaul. View the logs.
8 years ago
#7
@
8 years ago
In the above lined Slack mention, I had a chat with @boonebgorges and @johnjamesjacoby and @hnla. We decided to put this patch into 2.9.x, release that in January, and for 3.0, pull out all the bbPress 1.x legacy support / compatibility code.
As things stand, the Classic Forums component can be enabled and the config file is written, but the fatal error occurs whenever you try to access a group forum on the front-end (or enable it in a new group). This'll only work with WP pre-4.7, which is just over a year old.
02.patchdoes the following:01.patch)wp_usersDB tablebp_get_forum_topic_posts()is used more than once on the same forum topic page