Skip to:
Content
Pages
Categories
Search
Top
Bottom

BuddyPress 12.0.0

Viewing 25 replies - 26 through 50 (of 197 total)
  • @iputnik

    Participant

    Friends, I spent the whole night, but I couldn’t solve the problem.

    In the activity feed, you need to display only my posts, posts of my friends and groups in which I am a member. Can you send me a working code that will work in version 12.0?

    The options from the Internet did not suit me, I tried everything. The gpt chat didn’t help me either.

    @gyrus

    Participant

    Hi, I just woke up to find that one of our major client sites has auto-updated to BuddyPress 12 and this has completely broken groups functionality, which is a major part of the site. How can I quickly roll back to the previous version? It looks like more than just rolling back the plugin itself, it seems to have done loads of things to the data without my consent.

    @imath

    Moderator

    Hi @gyrus

    Sorry to read about this issue.

    We’ve built BP Classic a back compatibility Add-on, maybe you can try activating it to see if it solves the issue:

    BP Classic

    If not, I’ve explained into this reply how to rollback to 11.4.0 (you’ll need BP Classic anyway)

    BuddyPress 12.0.0

    > if you want to rollback, activate BP Classic (to get the regular directory pages back into your regular WordPress pages), then deactivate BuddyPress and BP Classic. You’ll need to manually reset the « DB Version » to the one of you version, see https://codex.buddypress.org/releases/. For instance for version 11.4.0, into the wp_options table the _bp_db_version option should be 13408. Only then download and activate a previous BuddyPress version (11.4.0).

    @priyam1234

    Participant

    In new version you remove all pages , how I can use ACF plugin option and I want to give option in redux field in which user can select pages but now I can’t . Please give me guidence.

    @priyam1234

    Participant

    About BP Classic, it give us pages but i can use ild functinlity how can i use new one with page.

    @claudiovillagra

    Participant

    Perfect name: no no install it

    It broke my page

    @imath

    Moderator

    Hi @priyam1234

    I guess you found how to get back to « classic » pages for BuddyPress directories (installing and activating BP Classic). That’s the way you will find also back your need to use ACF with it.

    About your second reply I’m not sure to understand what you mean about the functionality you’d like to use in BuddyPress Classic and that is only available in Modern BuddyPress. If it’s the community visibility feature, I confirm you need to « go Modern » with the BP Rewrites API to enjoy it.


    @claudiovillagra
    Thanks for your feedback, I’m sorry you experienced trouble during the upgrade of your specific configuration, it’s difficult to be more useful to you as your description of the problem is very limited. I must admit we’ve hesitated about this release name « Nonno » but we were sure our community members was so friendly, constructive & contributive we wouldn’t get this kind of ironic remarks.

    @westmdresearch

    Participant

    Thanks so much @imatt! I really appreciate learning more about BP development.

    Unfortunately, neither the deprecated functions, nor the return of these functions fixed our issues. I’ve reached out to the theme authors for fixes, and had some mixed results.

    I’ve manually cut out the affected custom functions from our most important themes until the authors get around to issuing fixes (hopefully).

    I would like to point out that our team tested our plugins (we’re researchers more than developers, so it was tricky but definitely possible to troubleshoot) when the notice first went out and the adjustment period was announced. Unfortunately, it appears that many of the premium theme authors, in particular, did not make the needed adjustments ahead of time.

    Thanks again for all of the work that went into this release, as well as the ongoing maintenance of this project. I really do appreciate not only the work, but the ongoing support as well. 🙂

    Thanks again, and have a great day/evening!

    @imath

    Moderator

    Hi @westmdresearch

    Thanks a lot for your feedback 😍. I’m happy to read you succeeded in troubleshooting issues on your side. We always try to imagine what could go wrong when we update our code but at the same time, we need to go forward. This release is very important as we’ve tried to explain as much as we could, it’s a starting point: fully complying with WordPress way of parsing requests will help us on various fields in the future. We know it’s a massive change and I feel sorry to read there are cases we were not able to anticipate: but we strongly believe it’s a needed change for the better of our next community features.

    @dangbird

    Participant

    Hello @imath – After 12.0 update if the “Notifications” Setting is set, it appears to take over/override my theme. (Reign Theme + Child Ultimate Buddy Press Theme) NON Admin users cannot see the site as some kind of code overrides the Theme.

    Let me know if I can provide any details.
    (Rollback to 11.4 is great, or DISABLE 12.0 “Notifications”)

    Thanks very much.

    @imath

    Moderator

    Hi @dangbird

    Thanks for your feedback, in version 11.4.0 we’ve (exceptionally) introduced a feature to display notifications only to admins to inform them about the massive change coming into 12.0.0. See https://buddypress.trac.wordpress.org/ticket/9007

    This feature we called “Admin notifications” is temporarily overriding the notifications for all admin users as long as one of the admin clicks on the exclamation mark to read the important message we want him to read. This message is about when to activate BP Classic to preserve backwards compatibility required by a specific config (BP Plugins not updated for the last 4 months, the deprecated BP Default standalone theme activated or the need to still use BP Legacy widgets).

    It may be the reason explaining what you saw with the Reign theme. It should disappear as soon as you read the Admin notification. Let me know if it helped you fix (or not) the issue with 12.0 for you.

    @erotmil

    Participant

    The BP 12 upgrade whacked out my buttons on a page that is custom code, Divi child theme coded in PHP/PDOCrud, there are widgets that have a require once script calling the child theme page, page loads but some buttons no longer work., I used wp-rollback to downgrade back to BP 11.40 and everything works. I tried the classic plugin mentioned here didn’t help, saved permalinks. I’m not clear about the suggestion to change the code bp_core_retain_legacy_widgets(), where is this code located? I can try that next.

    @claudiovillagra

    Participant

    Hi Mathieu, thanks for your reply, sorry that I sound harsh but we have been dealing with the site for long time, and now when we thought was good, the new BP update is breaking it again.
    We use Woffice as an Intranet, internal news. We used the Birthday and Anniversaries but now I need to have it disabled in order to have Woffice working. I’m open to suggestions.

    @imath

    Moderator

    Hi @erotmil Sorry to read about this issue, I’m not sure to understand what the custom code is doing. As you’re talking about widgets I guess it may contain some <?php dynamic_sidebar( 'name_widget_zone' ); ?>. Have you checked your error_log to see if there were some errors? About BP Classic, it contains the BP Legacy widgets, they are automatically loaded if you’re not using the Block Widgets editor, the function you mentioned was used to do this check, I believe you don’t need to care about it in your case. If your custom code is viewable from a Github Gist for example, I can look at it to see if I can find an explanation to your issue.


    @claudiovillagra
    I understand your frustration. If I often talk about BP Classic when replying to support requests about the 12.0.0 upgrade that’s because it’s the Add-on we’ve built to “neutralize” the 12.0.0 change BP Plugins might not be ready with (even if we’ve been working on 12.0.0 and communicating about it for almost a year…). I thought Woffice was a plugin but find out it was a premium theme. Unfortunately I can’t look at their code to understand the issue. If you haven’t try BP Classic, what I would do in your case would be to put up a staging site to replicate your production site and give 12.0.0 some other tests, try BP Classic and if issues are not solved with it, try to identify the issue checking the error_log file or using define( 'WP_DEBUG', true ).

    @dangbird

    Participant

    So I tried the BP Classic Plugin and no changes. Did a bunch of testing and IF a notification has NOT been read or dismissed for ANY user, they can see the normal front end of the Website fine/all works as before. HOWEVER if any user dismisses or deletes any notification then they get a blank web page with just our header and the BP Icons, with no console errors etc.

    So having a Notification or NOT having a notification is the trigger for the Theme failing.
    Installing BP Classic made not change.

    That said, I am likely not understanding the thread you provided or how the update worked. Rolled to 11.4 all well again. Appreciate the support, and a fantastic plugin.

    @erotmil

    Participant

    @priyam1234

    Participant

    Hello @imath , thank you for your replay . I appreciate BP new version, I just want to know that if I want to use latest version of BP and also want to use ACF so that is possible.if not so please find some solution for that. Because its key functionality in our theme.

    Note:- I do not want to use BP classic ,I want to go with new version of BP.
    Thank you

    @gbordormor22

    Participant

    I have a little bit of confusion.

    I uploaded a Cover Photo and it is showing on the Member Directory, as you can see here– https://prnt.sc/pmHvi8sO41nd

    and also on the Header of the user Profile, as you can see here– https://prnt.sc/px7evM6Ggj0K

    1.) Is that the expected behaviour of BuddyPress?

    2.) Is there a way to show the Cover Photo on the Single User/ Profile Page, but not show it on the Member Directory?

    2b.) Is there any Code Snippet that can be used to achieve that?

    Regards.

    @vapvarun

    Participant

    @dangbird The release of the Reign theme is in the queue and will be pushed today. Please continue using version 11.4 for the time being as we are currently in the final testing phase. Thank you.

    @imath

    Moderator

    Hi @erotmil thanks for sharing this code. I don’t see anything particular that would conflict on the server side. Since your issue is about button visibility I wonder if the fact we’re not including BuddyPress template pack styles and scripts everywhere on the site but only in BuddyPress generated pages could be the reason why you’re not seeing the buttons of this custom page. If you already rolled back to 11.4.0 a good way to figure it out is to temporarily add this code into the functions.php of your theme:
    remove_action( 'wp_enqueue_scripts', 'bp_enqueue_scripts', 10 );. Note that this code will remove all CSS and JS for BuddyPress, make sure to use it before refreshing your custom page from your browser, once refreshed if your buttons are gone, then we’ve found the issue. Remove immediately after the above code. If you still have BP 12.0 active, you can test adding the following code to see if it’s fixing the issue for your custom page:
    add_filter( 'bp_enqueue_assets_in_bp_pages_only', '__return_false' );. If it’s the case you can leave this code, otherwise remove it.

    @imath

    Moderator

    Hi @priyam1234 about ACF, the thing is we don’t use a UI to edit BP directory pages. As anyway we never used the content of the page post type for BuddyPress content, now we’ve migrated to a buddypress post type we’re not generating the corresponding UI in WP Admin. I’m going to look at it to see how we can integrate ACF with our new way of dealing with the buddypress post type. I just need 2 or 3 days to figure it out.

    @imath

    Moderator

    Hi @dangbird

    Many thanks to @vapvarun for working on it from the Reign theme 😍. I’m confident it should fix your issue with 12.0 in a near future.

    Hi @gbordormor22

    1) we only add this cover image on the member’s profile page or into an activity when a member has changed their avatar or cover image
    2 & 2b) I believe it’s something your active theme is adding, there are ways to override it using the BP Template hierarchy if you are using a child theme, but maybe your theme has an option or a more straightforward way of disabling it, have you tried to contact the theme author?

    @gbordormor22

    Participant

    @Mathieu Viet

    You are correct. It’s my Theme that added it. I’ve reached out to them and they’ve fixed it.

    GOING FORWARD
    I think BuddyPress 12.0 is quite different.

    Things no longer work as we used to know them.

    The first culprit is Pages. We don’t know how to get our Pages again. I need to show my Activity Page on my website, but I’ve spent 2 days on it, and still can’t figure it out.

    What I think should happen, is that we should have a SubMenu on this BuddyPress website, and call it “BuddyPress 12.0 Guides“.

    You can copy everything in BuddyPress Documentation, and paste them inside the BuddyPress 12.0 Docs.

    Then your content creator can start modifying the information of these Docs to reflect the BuddyPress 12.0 reality.

    Regards.

    @priyam1234

    Participant

    Okky , please inform me.
    One more question, I want function by using it I. Get archive page url such activity, members, group etc..

    @shahriar83

    Participant

    sorry to say, that during the update to BP 12.0.0, I Made a mistake. Before updating BP; I MAKE ACTIVATE B CLASSIC. FOR THIS REGION MY SITE SHOWS A CRITICAL ERROR. TODY I DEACTIVATED B CLASSIC AND THEN UPDATED BP 12.0.0. AFTER UPDATING BP 12.0.0 I MAKE ACTIVATE B CLASSIC PLUGINS. IT WORKS, WITH NO ERRORS.

Viewing 25 replies - 26 through 50 (of 197 total)
  • The topic ‘BuddyPress 12.0.0’ is closed to new replies.
Skip to toolbar