When I have Buddypress activated, then I cannot publish featured images to my blog posts. They upload to my site, but it will not save with the post. It’s done this for months – so I had just deactivated. But I need Buddypress back again.
Also, this isn’t unique to one theme. I’ve tried it on two separate sites with different themes. I’ve deactivated all other plugins, etc…
Buddypress is the issue.
As I have not managed to code something that works to identify my specific group, I did a bit of lateral thinking and my code looks to see whether or not a “group_mod” is present in a group and (if not) the Join/Hide button is hidden, like the case of group_admins, when only one is present. I can live with it for now, as I just have to make sure that all other groups have at least one Moderator set, then they work as normal.
It works fine for me, using BuddyPress Version 10.4.0, under WordPress 6.0.2 and a modified “Wellness Pro Version: 1.1.4” child theme under Genesis Framework Version: 3.3.5.
I hope it helps, unless and until some kind BuddyPress dev comes in with a proper solution!
Seems I wrote too much? I will post in two parts:
Hi @hcmendez, I am trying to do exactly the same thing myself and found the post your referenced, which was now made 10 years ago! I have developed a staging test site for a Radio Club, where registration is disabled and all user accounts will be set up for the users. There are 3 levels of membership: member, editor and admin – each with separate user roles. I have a group called “ROC Members” which all levels of membership are in and I do not want them to have the ability to leave (so want to remove the Join/Leave Button from this group (I can manage members from WP backend).
After some experimentation, I have found a rather poor “workaround”, by adding an extra ‘if’ statement to the code in plugins -> buddypress -> bp-groups -> bp-groups-template.php (where the extra code above is from), which is far from ideal as it can get overwritten on buddypress update.
I have WordPress 6.0.2
I received a message for BuddyPress that the plug in was not installed. But when I went to install it, the message was that BuddyPress cannot be installed because it already exists.
I deletedthe folder,for BuddyPress in the wp-contet/plugins folder on my server.
I reinstalled BuddyPress.
This is the error that I get when clicking on Activate for BuddyPress in thge Plugins page
PHP Warning: require(C:\visionroot\wwwroot\wp_inspiration\wp-content\plugins\buddypress/class-buddypress.php): failed to open stream: No such file or directory in C:\visionroot\wwwroot\wp_inspiration\wp-content\plugins\buddypress\bp-loader.php on line 76
PHP Fatal error: require(): Failed opening required ‘C:\visionroot\wwwroot\wp_inspiration\wp-content\plugins\buddypress/class-buddypress.php’ (include_path=’.;C:\php\pear’) in C:\visionroot\wwwroot\wp_inspiration\wp-content\plugins\buddypress\bp-loader.php on line 76
Anonymous User 18187419Inactive
Try a slightly earlier version of Buddypress.
Go to WordPress plugins repository, find Buddypress page, select Advanced View for earlier versions.
But now I wonder how it would be done on Buddypress.
Could you guide me on that?
Thank you!!
Ok, new question:
How could I display the Activity postform from Buddypress Nouveau as a shortcode using functions.php?
Do I post this on a new topic?
Thanks
BuddyBoss is a fork of BuddyPress, done several years ago. The codes bases have diverged.
Anonymous User 18187419Inactive
When you see that message …
“The following active BuddyPress components have no associated WordPress pages: Activate, Register. Repair”
…then click the Pages option.
You will see Members, Activity Streams, Register, Activate.
Make sure each of those is associated with correct option in drop-down menu alongside.
Members >> Members
Activity Streams >> Activity
Register >> Register
Activate >> Activate
Then Save Settings
Anonymous User 18187419Inactive
If however you were running latest version Buddypress without problems before the issue showed, then its likely something else causing conflict with BP.
Any other changes to your site?
Any new plugins installed or updated?
Any code snippets added?
I see you are also commenting on “Block user from accessing /wp-admin” topic. If you have made changes in that area, remove them.
Anonymous User 18187419Inactive
Sorry that link is misbehaving. Follow link and click Advanced View for earlier versions of Buddypress.
Anonymous User 18187419Inactive
If issue appeared after update to latest version of Buddypress then try installing an older version which didn’t cause problems.
Available here:
BuddyPress
Apologies for the repeat. I was told that the first topic was marked as spam, that’s the reason for this one, incase the first one is not seen.
I am running the current versions of WordPress and buddypress. I all of a sudden cannot see my admin tool bar or login to my WordPress backend. Activated the debug feature and found out its an issue with buddypress plugin. Please how Do I resolve this? I had to disable the entire plugins, to be able to login of give access to my backend. The web url is http://www.wokshop.com
https://mywokshop.com/wp-content/uploads/2022/09/Screenshot-2022-09-01-at-00.15.15.png
I meant buddypress please.
Hello!
Did you solve this problem?
I’m interest to resolve this problem too. In my studying process of this question I found old plugin which resolve this problem – https://github.com/wp-plugins/fb-like-notification-for-buddypress
Started testing and inspect if I find solution – will write it here.
Thank you!
Hi,
I’m using BuddyPress with the extendes profiles.
When a visitor tries to register, it may fail from time to time. After the submit, however, there is no error, but he lands directly back on the registration form – without error or anything else. But then the email address is already taken.
The question is what can be the reason that he lands again on the form after the submit and where is the email stored in the database if the registration is not completed/successful?
in wp_users I do not see anything about it
Thanks a lot!
Can we upload images to BuddyPress Topics or Replies For a Post.
This was the problem,
This is test script. One line of PHP code:
https://seeme.baby/test.php
503 error in result.
Because function ‘transliterator_transliterate’ failed to execute on your server.
Exactly the same PHP script on my own server working properly:
https://takereal.com/test.php
File ‘wp-content\plugins\buddypress\bp-core\classes\class-bp-attachment.php’ updated
to prevent ‘transliterator_transliterate’ execution.
old line #297:
if ( function_exists( ‘transliterator_transliterate’ ) && seems_utf8( $retval ) ) {
My version:
if ( 0 && function_exists( ‘transliterator_transliterate’ ) && seems_utf8( $retval ) ) {
Function ‘transliterator_transliterate’ used in the ‘class-bp-attachment.php’ only.
File name sanitized in another way, without ‘transliterator_transliterate’ function.
‘class-bp-attachment.php’ has code to sanitize file name
without ‘transliterator_transliterate’ function.
Hello! i have problem, from official tutorial i create folder and upload translation from your website to: /wp-content/languages/buddypress
Name of file wp-plugins-buddypress-stable-pl.po
But plugin is still in engllish why? where i can change now plugin to use PL?
> Buddypress plugin to use with my Buddyboss plugin
You cannot use them together.
Try deactivating all Buddypress and Buddyboss plugins.
And then try deleting Buddypress.
From logs gives this error
2022-08-26 10:06:27.739089 [NOTICE] [566017] [5.203.157.99:2859:HTTP2-1847#seeme.baby-443] oops! 503 Service Unavailable
in the console i dont see any java errors
from debug i get
Deprecated: Return type of BP_Core_BP_Nav_BackCompat::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/admin/domains/seeme.baby/public_html/wp-content/plugins/buddypress/bp-core/classes/class-bp-core-bp-nav-backcompat.php on line 122
Deprecated: Return type of BP_Core_BP_Nav_BackCompat::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/admin/domains/seeme.baby/public_html/wp-content/plugins/buddypress/bp-core/classes/class-bp-core-bp-nav-backcompat.php on line 97
Deprecated: Return type of BP_Core_BP_Nav_BackCompat::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/admin/domains/seeme.baby/public_html/wp-content/plugins/buddypress/bp-core/classes/class-bp-core-bp-nav-backcompat.php on line 63
Deprecated: Return type of BP_Core_BP_Nav_BackCompat::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/admin/domains/seeme.baby/public_html/wp-content/plugins/buddypress/bp-core/classes/class-bp-core-bp-nav-backcompat.php on line 148
Deprecated: Automatic conversion of false to array is deprecated in /home/admin/domains/seeme.baby/public_html/wp-content/plugins/buddypress/bp-core/bp-core-functions.php on line 3364
Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/admin/domains/seeme.baby/public_html/wp-content/plugins/buddypress/bp-core/bp-core-avatars.php on line 460
I downloaded the Buddypress plugin to use with my Buddyboss plugin but ended up not needing it. After trying to delete I kept getting a deletion failure message. I’m not sure what to do. I should also note that my site isn’t broken from this but I got an email that there was a critical error so I wanted to fix it. I’m on wordpress 5.2 and my site link is: https://your-introverted-space.com
Thanks
According to https://codex.buddypress.org/translations/ we should store the bbpress-de_DE.mo and bbpress-de_DE.po under /wp-content/languages/buddypress/, which we did. But these language files are being ignored.
We are using buddypress in de_DE and made some tweaks to the wording (we replaced the string “group” with “cluster” in German).
Buddypress uses the files stored under /wp-content/languages/plugins/ and ignores the aforementioned folder.
What we already tried:
- deleting the
buddypress-de_DE files in /wp-content/languages/plugins/: this partially works. Buddypress then uses our files stored in /wp-content/languages/buddypress/. But somehow wordpress (or buddypress?) regenerates the files in /wp-content/languages/plugins/ after some hours. And then these “new” translations are used again of course. (Our own translations in /wp-content/languages/buddypress/ stay untouched by wordpress/buddypress)
- Created a folder
/wp-content/languages/plugins/buddypress and copied our files over to this folder. But to no avail – these files are being ignored completely (even if we delete the buddypress files in /wp-content/languages/plugins/).
- Copied our files directly to
/wp-content/languages/plugins/: this works until these files get overwritten after a couple of hours
Specs:
- WordPress 6.0.1
- Buddypress 10.4.0
- Custom template, which we’ve written on our own
Multisite
Questions:
- What are we missing?
- Is there a way to stop wordpress/buddypress regenerating the files living directly in
/wp-content/languages/plugins/?
- What is the right place to store our translations?
That’s what I started with: disabling plugins one by one, but that didn’t show any issues. I noticed the code was only appearing on Buddypress pages, so then I kept Buddypress active and one-by-one activated, checked, and then deactivated each plugin until the code reappeared.
It takes a super long time, but it’s really the only way to really find issues like this (that I know of).
I also use the Health and Troubleshooting plugin to do this, so the site doesn’t appear any different to anyone non-admins. That means people can keep using the site (I have courses with Learndash, so this is a big one!) while troubleshooting
