Skip to:
Content

BuddyPress.org

Opened 6 weeks ago

Closed 6 weeks ago

#9306 closed defect (bug) (invalid)

14.4 assumes member and group type exists

Reported by: shawfactor's profile shawfactor Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Core Keywords: reporter-feedback
Cc: emaralive

Description

Team,

I am getting all sorts of errors that have started with 14.4

I cannot see the new version on github so I can't compare before or after but it now appears that buddypress assumes that the group type and member type taxonomy exists inall sorts of places it did not before

Whilst this would be the case for most installations core buddypress allows you to remove these taxonomies and I have as I don't want them via various buddypress provided filters

I have monkey patched buddypress in a number of places by adding checks to ensure blocks of codes are only run when the taxonomy exists but realistically the functions should be refactored in core to only look for these taxonomies if they exist.

Can this be fixed asap?

Attachments (1)

bp-diff-14.4-v-14.3.4.diff (17.3 KB) - added by dcavins 6 weeks ago.
Diff between WP repo downloads for 14.4.0 vs 14.3.4

Download all attachments as: .zip

Change History (6)

#1 @emaralive
6 weeks ago

  • Cc emaralive added

#2 @emaralive
6 weeks ago

  • Keywords reporter-feedback added

Hi @shawfactor,

Could you be more specific about the errors that you are receiving? Additionally, I'm not sure why you can't see the tag for 14.4.0 in GitHub, perhaps you could elaborate a bit more.

#3 @dcavins
6 weeks ago

Well, that is a mystery. I'll attach a diff showing what changed between 14.4.0 and 14.3.4 as downloaded from the WP repo. I am not seeing anything about groups or member types changing. Please take a look and let me know if you see anything that would be causing your problems.

@dcavins
6 weeks ago

Diff between WP repo downloads for 14.4.0 vs 14.3.4

#4 @espellcaste
6 weeks ago

I'd also check in your site for any custom rewrite rules. Non-BuddyPress rewrite rules that could be setting the taxonomy "in places where it didn't".

#5 @shawfactor
6 weeks ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

I think you can close it then guys.

It must be something to do with the loading order being changed when the plugin was upgraded

Note: See TracTickets for help on using tickets.