BuddyPress Profile notifications tab throwing error

[mitchcan]

Hi,

I am getting the following error in BuddyPress on my /members/username/notifications/ page:

Fatal error: Call to undefined function bp_notifications_bulk_management_dropdown() in /URL…/wp-content/themes/kleo/buddypress/members/single/notifications/notifications-loop.php on line 31

Line 31 is: <?php bp_notifications_bulk_management_dropdown(); ?>

ALL plugins off except for BuddyPress, VC, K-Elements.

This error does NOT display when I change from the Kleo theme to another theme.

I am using:
WP 4.1.1
BP 2.1.1
Kleo 2.4.1

Thanks for any help you can give to resolve.

[sharmstr]

I’ll let abe know. The bulk management dropdown wasn’t available until BP 2.2. Any reason why you dont want to update?

Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution

This support site is not about custom work. If you need custom development please contact cornel@seventhqueen.com

[mitchcan]

Valid question. I do want to update, it’s just that a plugin that we deemed important to what we are doing – ‘BP Activity Privacy’ – seems to be broken in BP 2.2+. We’re hoping for a timely fix, but we needed to keep it working on one site as we determined what our options were.

If it’s trouble to resolve, I can hide it as we work to figure out our next move and get to 2.2+. I’m not looking to create unnecessary work. 🙂

[sharmstr]

Ahhhh. Got it. I think abe will want to put the change in the next update to make Kleo backward compatible. I know he put some code in 2.4.1 for backward compatibility.

Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution

This support site is not about custom work. If you need custom development please contact cornel@seventhqueen.com

[mitchcan]

Yeah, 2.4.1 fixed a number of backward compatibility conflicts with BP 2.1.1, good update. This issue must have just been overlooked. If I see anything else, I’ll pass it along for his next update.

Thanks!

[sharmstr]

Cool. Add it here since I’ve assigned this to abe

Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution

This support site is not about custom work. If you need custom development please contact cornel@seventhqueen.com

[Abe]

Hello, fixed this for the next update. Until then you can replace this file content /wp-content/themes/kleo/buddypress/members/single/notifications/notifications-loop.php with the content from the attached file.

Cheers

Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution

---
@ SeventhQueen we do our best to have super happy customers. Thanks for being our customer.

Attachments:

You must be logged in to view attached files.

[mitchcan]

Hello Abe,

This code has resolved that error. Thank you.

BUT, I have another error that I am not sure if its related:

“GET //URL/wp-admin/admin-ajax.php?action=kleo_bp_notifications_refresh&current= net::ERR_INSUFFICIENT_RESOURCES”

I only ask if its related because it also references something to do with bp notifications.

It sends my js errors numbers crazy in console, and ultimately throws the site into a 500 server error.

If it’s not related, do know what might be causing it?

Thanks!

[Abe]

Maybe you have modified the timeout of the notifications requests that are sent. the setting is in WP admin – Theme options- Buddypress and the default value is 20000

Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution

---
@ SeventhQueen we do our best to have super happy customers. Thanks for being our customer.

[mitchcan]

Oh, I have, good call. I was simply looking to make the requests fewer in number, so I increased the value to 60000. I (maybe mistakenly) thought this would mean fewer requests and better site performance? Would that matter?

I will change that back to 20000 and see if it resolves. Thanks for the guidance.

[Abe]

20000 is 20 seconds since it is expressed in miliseconds. So 60000 would mean 60 seconds

Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution

---
@ SeventhQueen we do our best to have super happy customers. Thanks for being our customer.

[mitchcan]

Right, so I thought that meant a greater delay in the time that it looked for updates (60 seconds vs. 20 seconds) which I thought would be a good thing. Serves me right for thinking, always gets me in trouble. 🙂

I must have misunderstood this setting, thinking it was the time between checking for updates – not the length until a timeout. It’s my fault, I’ll change it back to default. Thanks again!

[Abe]

Maybe I explained it a bit complicated but is exactly how you say, it is the time between the requests that checks the notifications.

Put a link to your site along with a demo user to check if you have some sort of Javascript problems.

Cheers

Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution

---
@ SeventhQueen we do our best to have super happy customers. Thanks for being our customer.

[mitchcan]

Hmmm. I have changed the setting back to default; updated to BP 2.2.1; removed the multitheme plugin; set Kleo as default theme — and the error remains. I will submit some site login info…

[mitchcan]

This reply has been set as private.

[Abe]

I went to your /register page but don’t see errors

Try to disable some plugins you are using and may cause this

Hi there!!! Help others from the community and mark any reply as solution if it solved your question. Mark as a solution

---
@ SeventhQueen we do our best to have super happy customers. Thanks for being our customer.

[mitchcan]

It was actually on the /membership-account/membership-levels/ page, not the register page.

Still, it was indeed a plugin issue. But funny enough, it wasn’t that I had too many, it was that I didn’t have ones Active for that page. Without BuddyPress and the bp-custom plugins active, that generated the errors. When I went through to look at deactivating some, I tested with those on and it works.

Thanks for thinking through this with me.

[gregkamphuis@hotmail.com]

@mitchcan I have the exact issue you describe, although it happens on every page of my site, any advice with what you found out would be hugely appreciated!

[mitchcan]

@gregkamphuis@hotmail.com

Hmmm, I tried so many fixes, I’m not sure if I recall the exact one that worked. 🙂

If I’m not mistaken, my issue ultimately had something to do with using “Live Notifications” and my specific plugin stack. I have removed that feature from my menus, made also sure that BP was active on any pages that had BP-related menu items, and I haven’t seen a reoccurrence of the issue.

If I think of anything else, I’ll jump back in, but hope that helps trigger some options for you.

Good luck.

[gregkamphuis@hotmail.com]

Oh man, you saved my life, the problem was have VC elements that called for BP menu items that weren’t active, wow, I spent over week trying to figure this out, and was near the point of giving up, thank you so much @mithccan

[mitchcan]

Happy to help. It was driving me crazy too, so I know your pain. Good luck!

[Author]

Posts