Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'buddypress'

Viewing 25 results - 901 through 925 (of 69,016 total)
  • Author
    Search Results
  • #332520
    fasirathore
    Participant

    I have better messages, bbpress and bbp style pack by robin w. These are plugins that have influence over buddypress

    #332516
    Mathieu Viet
    Moderator

    This last one is more helpful. Are you sure BP Classic is active? Because if active BuddyPress shouldn’t add this depreciation notice.

    What happens if you add this code to your wp-config.php?
    define( 'BP_IGNORE_DEPRECATED', true );

    #332511
    Mathieu Viet
    Moderator

    @fasirathore

    It was not logging you out with version 11.4.0 of BuddyPress?

    Can you rollback to 11.4.0 keeping BP Classic active to see if that solves the issue?

    Elementor’s reply is amazing, considering the price you pay for support & the fact we can’t test on our side because it’s a premium plugin and they can test on their side as BuddyPress is free. If it was out of their scope, Elementor wouldn’t conflict with BuddyPress…

    #332508
    fasirathore
    Participant

    For context, its not just created menu that has this error but also the admin panel profile system from buddypress. Even though, if I click notifications or messages from admin panel profile tab at top right, it will log me out.

    #332504
    rajibjoshi
    Participant

    Hi,
    I’ve built a custom user profile page using JetEngine. Is there a way to redirect visitors who click the “Profile” button on a BuddyPress profile page to my custom page, displaying their profile information?

    or please guide me as to how I can access buddypress all Meta_fields from Elementor ? Because i want to design my own profile page layout.

    Thanks in Advance

    Rajib

    #332501

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    @cheesy2k

    Slug constants were deprecated in version 1.5 of BuddyPress (more than 10 years ago). We decided to remove them from BuddyPress 12.0.0 as it’s now very easy to customize slugs.

    Your error is interesting, if you look at it, you’ll see the theme kleo now generates this error while it wasn’t when BP Classic wasn’t active. It means kleo is not ready for BuddyPress 12.0.0 because it wasn’t loading his specific code as it was trying to do so too early (BuddyPress objects are defined once the WP_Query is parsed in 12.0.0, while it was a bit after init previously).

    So, I advise you to contact kleo so that they update their outdated theme.
    In the meantime, you can get rid of this error adding this to your wp-config.php file:

    define( 'BP_NOTIFICATIONS_SLUG', 'notifications' );

    #332500

    In reply to: BuddyPress 12.0.0

    cheesy2k
    Participant

    I activated the plugin now I get this error on every page:

    Fatal error: Uncaught Error: Undefined constant "BP_NOTIFICATIONS_SLUG" in /../wp-content/themes/kleo/lib/plugin-buddypress/menu-notifications.php:61 Stack trace: #0 /../htdocs/csc-connect/wp-includes/class-wp-hook.php(324): kleo_menu_notifications
    
    .. thrown in /../wp-content/themes/kleo/lib/plugin-buddypress/menu-notifications.php on line 61
    #332497

    In reply to: BuddyPress 12.0.0

    cheesy2k
    Participant

    Hi Mathieu,

    I got a weird problem with version 12:

    When activating buddypress, all my content of every other page is not shown anymore to logged in users. I use paidmembershipspro plugin.
    Just see blank pages but the page titles are shown in the tab of my browser…

    What can be the problem here?

    #332494
    Mathieu Viet
    Moderator

    Ok, I understand you don’t want to take the time to fix the issue. It’s really difficult to understand each other. Sorry to read my help is so annoying. If the table is not called wp_posts, it’s probably due to the custom table prefix you defined into your wp_config.php file. The code I’ve shared is a filter, there’s no way for it to fail, but you managed to! I don’t know how you pasted it. You don’t seem to read what I’m advising you to do and you don’t reply in an understandable way. If you don’t want to fix the issue, I advise you to look into this support reply to see how to roll back to 11.4.0: https://buddypress.org/support/topic/buddypress-12-0-0/page/4/#post-332388

    I won’t annoy you anymore.

    #332492
    Mathieu Viet
    Moderator

    Here’s a way to disable BuddyPress signup feature:

    
    function disable_bp_signups() {
    	add_filter( 'bp_get_signup_allowed', '__return_false' );
    	remove_filter( 'register_url', 'bp_get_signup_page' );
    	remove_action( 'bp_init', 'bp_core_wpsignup_redirect' );
    	remove_filter( 'wp_signup_location', 'bp_blogs_creation_location' );
    	remove_filter( 'wpmu_signup_user_notification', 'bp_core_activation_signup_user_notification', 1 );
    }
    add_action( 'bp_include', 'disable_bp_signups' );
    #332491
    Mathieu Viet
    Moderator

    Here’s a way to disable BuddyPress signup feature:

    
    function disable_bp_signups() {
    	add_filter( 'bp_get_signup_allowed', '__return_false' );
    	remove_filter( 'register_url', 'bp_get_signup_page' );
    	remove_action( 'bp_init', 'bp_core_wpsignup_redirect' );
    	remove_filter( 'wp_signup_location', 'bp_blogs_creation_location' );
    	remove_filter( 'wpmu_signup_user_notification', 'bp_core_activation_signup_user_notification', 1 );
    }
    add_action( 'bp_include', 'disable_bp_signups' );
    ingenxcomputers
    Participant

    Have you had any luck

    My buddypress site invitations are going straight to people’s email SPAM folders

    Richard
    0794 332 1470

    #332489
    Mathieu Viet
    Moderator

    Have you tried to temporarily add this code to the functions.php of your active theme?

    remove_filter( 'wp_unique_post_slug', 'bp_core_set_unique_directory_page_slug', 10, 6 );

    And then did you go to the URLs tab of the BuddyPress settings and try to customize slugs again?

    If so, using your tool to administrate your site’s database (eg: PHPMyAdmin), can you run this query:

    SELECT id, post_type FROM wp_posts WHERE post_name LIKE "members%"

    #332488
    jaroslawistok
    Participant

    I did under Tools:

    Reset all BuddyPress slugs to default ones

    I saved permalinks, there are no standard pages with this names

    And still after saving slugs gets -2

    #332486
    Mathieu Viet
    Moderator

    So you’re using BP version 12.0 on a regular site (not a multisite config), you activated, then deactivated BP Classic because it was no more needed. And now when you go into the URLs tab of the BuddyPress settings and tries to customize slugs, it adds a -2 suffix.

    Is it happening when these slugs are default BuddyPress ones only (eg: activity, members) or is it happening even with these slugs: ‘activites’, ‘membres’ for example?

    If it’s only happening with BuddyPress default slugs: check there are no regular WordPress pages using the BP slugs.

    Then try to use the Reset Slugs BuddyPress tools from the WP Admin tools menu.

    If it didn’t fixed the issue, try to temporarily add this code to the functions.php of your active theme:
    remove_filter( 'wp_unique_post_slug', 'bp_core_set_unique_directory_page_slug', 10, 6 );

    Go to the URLs tab of the BuddyPress settings and try to customize slugs again.

    Then remove the custom code you added to the functions.php of your active theme.

    #332485
    jaroslawistok
    Participant

    Not multi, widely activated, BP is a root

    Do I have to have created standard empty pages? For now I haven’t

    After saving permalinks still is coming members-2 ans s on in buddypress after saving

    #332484
    Mathieu Viet
    Moderator

    Hi,

    I just tested and I wasn’t able to reproduce, sorry. I don’t think it’s a BuddyPress problem. Have you tried to temporarily deactivate all plugins except BuddyPress to see if the issue was still there?

    If so, maybe you can try to activate the BP Classic backwards compatibility plugin in case there’s a 3rd party BP plugin playing into this area.

    #332482

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    @perchenet

    Something similar was reported earlier about the deprecation notice. I believe it’s due to a custom code or a theme:

    See: https://buddypress.org/support/topic/buddypress-12-0-0/#post-332208
    Which seems to help the reporter to fix it: https://buddypress.org/support/topic/buddypress-12-0-0/#post-332211

    About the main site being very slow, that’s weird. But I’ll check BP Classic with your specific config. You can try to see if only activating BP Classic on the subsite is making main site faster.

    #332478

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    For your info, I’ve started your config tests and I found a bug with slug customization:
    https://buddypress.trac.wordpress.org/ticket/9048

    So I confirm there’s an issue. I’m working on it.

    #332470
    Mathieu Viet
    Moderator

    Hi @fasirathore

    Thanks for your feedback, are you using BP version 12.0.0?
    Can you check your error log file to see if something was traced in it?
    What’s your WordPress set up ? Multisite or not ? If Multisite is BuddyPress activated on the network ?

    #332469
    Mathieu Viet
    Moderator

    Hi @jaroslawistok

    Sorry to read about it. Can you tell me a bit more about your config?
    – regular or Multisite WordPress ?
    – if Multisite how BuddyPress is activated ? Network widely, on the main site or on a subsite ?
    – If activated network widely, are you using the constant to set the BP root site to be a subsite instead of main one?

    #332468

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Thanks a lot

    1. So there’s an issue with this specific config in BuddyPress. The repair tool, as run from the network admin where site ID is 1 is not checking the right BP root site. I’ll work on it asap. To be honest: we’ve tested a lot of configs, but I believe not the specific case where the BP root site is not the same than the network one. Sorry about it.

    2. It looks like the fatal error is generated by the « onecommunity » theme. Moreover this theme or some 3rd party plugin(s) is(are) not ready for BP 12.0.0. I believe you need to activate the BP Classic Add-on network widely – like BuddyPress. (but let’s keep on debugging doing step 3 before 🙏)

    3. Can you run this query:
    SELECT id, post_type FROM wp_posts WHERE post_name LIKE "activity%" I feel the migrate routine wasn’t checking for the right site ID.

    4. Once you activated BP Classic, go to the Permalink setting of site 4 and simply save the permalink structure without changing the selected structure.

    I need some time to fix this specific config for 12.0.0. I think it will be ok for the beginning of next year.

    #332463

    In reply to: BuddyPress 12.0.0

    perchenet
    Participant

    Thank you Mathieu

    Critical error:

    Notice: La fonction map_meta_cap a été appelée de façon incorrecte. Le type de publication buddypress n’est pas enregistré. Il n’est donc pas possible de vérifier de manière fiable que la permission « edit_post » correspond à ce type de publication. Veuillez lire Débogage dans WordPress (en) pour plus d’informations. (Ce message a été ajouté à la version 4.4.0.) in /var/alternc/html/d/davduf/www/auposte.fr/wp-includes/functions.php on line 6031
    
    Deprecated: La fonction bp_core_get_user_domain est obsolète depuis la version 12.0.0 ! Utilisez bp_members_get_user_url() à la place. in /var/alternc/html/d/davduf/www/auposte.fr/wp-includes/functions.php on line 6031
    
    Deprecated: La fonction bp_core_get_user_domain est obsolète depuis la version 12.0.0 ! Utilisez bp_members_get_user_url() à la place. in /var/alternc/html/d/davduf/www/auposte.fr/wp-includes/functions.php on line 6031
    
    Warning: require(/var/alternc/html/d/davduf/www/auposte.fr/wp-content/themes/onecommunity/inc/typography.php): failed to open stream: No such file or directory in /var/alternc/html/d/davduf/www/auposte.fr/wp-content/themes/newsblock/inc/filters.php on line 205
    
    Fatal error: require(): Failed opening required '/var/alternc/html/d/davduf/www/auposte.fr/wp-content/themes/onecommunity/inc/typography.php' (include_path='/var/alternc/html/d/davduf/www/auposte.fr/wp-content/plugins/kirki/:/var/alternc/html/d/davduf/www/auposte.fr/wp-content/plugins/kirki/core:.:/usr/share/php') in /var/alternc/html/d/davduf/www/auposte.fr/wp-content/themes/newsblock/inc/filters.php on line 205
    Il y a eu une erreur critique sur ce site.

    The Query:

    SELECT id, post_type FROM wp_4_posts WHERE post_name LIKE "activity%";
    +----+-----------+
    | id | post_type |
    +----+-----------+
    | 88 | page      |
    +----+-----------+
    fasirathore
    Participant

    When I added “bp-menu bp-logout-nav” to my menu items in BuddyPress, clicking on any other BuddyPress menu item such as notifications, messages, or profiles would log me out of WordPress unexpectedly. After removing the “bp-menu bp-logout-nav” from the menu, I no longer experienced logging out when clicking on any menu component.
    “bp-menu bp-logout-nav” is affecting other menu items of buddypress. How can I resolve it, I also have reinstalled buddypress plugin after deleting it but problem is still present.

    #332456
    Ceraus
    Participant

    Found that there is a conflict between Genealogical Tree Pro and buddypress when groups are enabled, still not sure what to do.

Viewing 25 results - 901 through 925 (of 69,016 total)
Skip to toolbar