I’m getting the following PHP error when posting updates with Activity as Wire activated (please note that I’m using 1.0.1 as I’m still running BP1.8):
PHP Warning: Missing argument 2 for devb_aawire_update_activity_action() in [URL REMOVED]/wp-content/plugins/bp-activity-as-wire/bp-activity-as-wire.php on line 140
How can I this fix this?
- This topic was modified 7 years, 8 months ago by ljmac.
I can confirm that in 1.8. The problem is , The plugin assumes you have 2.0 or above. In 1.8, The $activity is not available as the 2nd parameter causing the problem.
I am unable to think of a solution as we are heavily relaying on activity id which is not available in case of 1.8.
May be you should try 1.0 of Bp activity as wire instead.
PS: If possible, I will suggest upgrading to BP 2.2(or 2.0) as a lot of things have come in these two versions.
Okay, thanks for the info. I am reluctant to upgrade BP as I depend on a few older plug-ins that will very likely be broken. I also have to say that the most of the new stuff that has been added is not terribly useful to me (and what is useful was already well covered by existing plug-ins), while frustratingly they continue to avoid adding the stuff that should have been there from day one (most notably, privacy settings throughout, instead of just for the profile fields where it’s probably needed the least). The continued lack of integration with existing WordPress core features is also frustrating, while they waste code and effort reinventing the wheel. Why did they create user types for BP instead of leveraging the existing user types in WordPress, for example? Why can’t we favourite stuff in the front end? Etc. etc.
Anyway, enough ranting. I’ll try 1.0.
I am sorry to hear about that. There are things that needs to be done and BP is moving in that direction. I can understand the frustration but there are reasons for using separate member types. WordPress has roles, fixed roles system and it is not easy create/manage new roles due to all the capability system.
BuddyPress member types are not for capability, the only purpose it serves is identifying different type of user. I hope you understand the difference between the two. Also, It is a very lightweight system. Another reason to introduce the member type instead of using roles can be thought as a way to support multisite. On Multisite, roles are site specific and will not suit the requirement of BuddyPress.
There are things that needs to be improved and the BuddyPress team have been generously improving it. We have to remember that BuddyPress is a non profit project and everyone donating time there are doing it for free. So, I respect it.
Hopefully, With the BP Development gaining more pace, you won’t have complains in future 🙂
I must say I have similar feeling about the direction of WordPress itself – I’m still on 3.7.14, as I don’t know of any essential new features they’ve added since then. Plus I prefer the interface of 3.7.14 (I HATE the current ‘flat’ UI trend), and it gets automatic security updates (now THAT was a useful feature).
Still, BP really seems absurd sometimes. I read how they added a rich text editor to the profile fields (which already had privacy controls), while AFAIK activity updates and comments still don’t have one (or privacy controls for that matter). What is with the BP development team’s obsession with profile fields? These are just a minor thing, but they lavish so much effort on them, while ignoring the obvious need for the same feature elsewhere. I just don’t get it.
Thank you for marking it as resolved. Change is coming, It does not matter whether we like it or not. I will advise installing a separate test site and once you get familiar with the new admin screen, you will love it(Believe me, I used to hate it when the new block one replaced the simple one).
You must be logged in to reply to this topic.