Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'theme'

Viewing 25 results - 351 through 375 (of 32,562 total)
  • Author
    Search Results
  • #332569
    siriusblack14
    Participant

    Within your BuddyBoss custom theme, navigate to the templates related to the BuddyPress activity feed. You’ll likely find relevant files in the buddyboss-child-theme/buddypress/activity directory.

    Look for the file responsible for rendering the activity feed and its items. You’ll want to customize this file to include a “Reply” button for each discussion.

    2. Customizing the Activity Feed:

    a. Locate the template file (e.g., activity/entry.php or similar) where the activity feed items are displayed.

    b. Identify the section responsible for displaying BuddyPress activities related to discussions or forum posts.

    c. Within this section, add a “Reply” button for each discussion using HTML and BuddyPress functions. Use the BuddyPress functions to generate a reply form or link.

    https://schoenhalde.de/

    #332562
    webmasterfreya
    Participant

    Wordpress 6.4.2
    BBPress 2.6.9
    Buddypress 12.0.0

    Hi,

    Pagination in buddypress fora (private group forum) is not working anymore. Only de first page is shown, whatever pagenumber one clicks on.

    e.g
    forum /groepen/icsi/forum/page/2/ shows page /groepen/icsi/forum/
    topic /groepen/icsi/forum/topic/icsi-2023/page/3/ shows /groepen/icsi/forum/topic/icsi-2023/

    This renders these fora unusable if sorted on datetime ascending.

    There are no errors or warnings in the php logfile.

    Deactivating all plugins (except bbpress, buddypress) does not make any difference. Changing theme does not make any difference.

    Pagination under BBpress fora works fine.

    So it seems that buddypress does not react on the last part of the url’s (e.g. /page/3/ )

    Temporary workaround :

    Up the amount of topics and replies per page under bbpress settings so that pagination does not show up.

    viviandsena11
    Participant

    WordPress Default Registration Settings:
    Go to your WordPress admin dashboard and navigate to Settings » General. Look for the “Membership” option or “Anyone can register” checkbox. Ensure that the checkbox is checked/enabled. This setting allows users to register via the default WordPress registration system.

    Disable BuddyPress Registration:
    In the BuddyPress settings, there might be an option related to registration. Look for the BuddyPress settings either in the WordPress dashboard or under the BuddyPress plugin settings. Disable or turn off any registration-related settings within BuddyPress to revert to the default WordPress registration.

    Check Theme and Plugin Compatibility:
    Sometimes, themes or plugins might override default registration settings. Ensure that your current theme or any other plugins installed do not enforce their custom registration processes that conflict with the default WordPress registration.

    Review Custom Code or Functions:
    If you’ve added any custom code or functions related to registration, review them to ensure they’re not redirecting or modifying the registration flow to use BuddyPress.
    Best Regards:

    Home

    #332525
    fasirathore
    Participant

    /home/u604108565/domains/forextradingcommunity.com/public_html/wp-content/themes/hello-elementor/functions.php on line 229

    [23-Dec-2023 07:58:30 UTC] PHP Warning: Attempt to read property “title” on null in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/class-wp-customize-widgets.php on line 905

    [23-Dec-2023 07:59:01 UTC] PHP Deprecated: The PSR-0 Requests_... class names in the Requests library are deprecated. Switch to the PSR-4 WpOrg\Requests\... class names at your earliest convenience. in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/class-requests.php on line 24

    [23-Dec-2023 08:08:45 UTC] Cron reschedule event error for hook: better_messages_cleaner_job, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”better_messages_cleaner_job”,”args”:[],”interval”:300}

    [23-Dec-2023 08:11:04 UTC] PHP Deprecated: Function print_emoji_styles is deprecated since version 6.4.0! Use wp_enqueue_emoji_styles instead. in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/functions.php on line 6031

    [23-Dec-2023 08:32:43 UTC] PHP Warning: Attempt to read property “title” on null in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/class-wp-customize-widgets.php on line 905

    [23-Dec-2023 08:32:54 UTC] PHP Deprecated: File Theme without header.php is deprecated since version 3.0.0 with no alternative available. Please include a header.php template in your theme. in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/functions.php on line 6031

    [23-Dec-2023 08:42:41 UTC] PHP Deprecated: Function get_page_by_title is deprecated since version 6.2.0! Use WP_Query instead. in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/functions.php on line 6031

    [23-Dec-2023 08:43:00 UTC] PHP Deprecated: The PSR-0 Requests_... class names in the Requests library are deprecated. Switch to the PSR-4 WpOrg\Requests\... class names at your earliest convenience. in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/class-requests.php on line 24

    [23-Dec-2023 08:44:10 UTC] PHP Deprecated: Function get_page_by_title is deprecated since version 6.2.0! Use WP_Query instead. in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/functions.php on line 6031

    [23-Dec-2023 11:32:30 UTC] PHP Deprecated: urldecode(): Passing null to parameter #1 ($string) of type string is deprecated in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-content/plugins/litespeed-cache/src/control.cls.php on line 547

    [23-Dec-2023 11:55:40 UTC] PHP Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-content/plugins/bbp-style-pack/includes/settings_import.php on line 16

    [23-Dec-2023 12:55:50 UTC] PHP Deprecated: urldecode(): Passing null to parameter #1 ($string) of type string is deprecated in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-content/plugins/litespeed-cache/src/control.cls.php on line 547

    [23-Dec-2023 14:04:20 UTC] PHP Warning: file_put_contents(): Exclusive locks may only be set for regular files in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-content/plugins/bbp-style-pack/includes/generate_css.php on line 165

    [23-Dec-2023 14:34:05 UTC] PHP Deprecated: Automatic conversion of false to array is deprecated in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-content/plugins/google-analytics-for-wordpress/includes/admin/notification-event-runner.php on line 94

    [24-Dec-2023 11:48:54 UTC] PHP Warning: Attempt to read property “name” on bool in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-admin/nav-menus.php on line 1215

    [24-Dec-2023 11:48:54 UTC] Cron reschedule event error for hook: action_scheduler_run_queue, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”every_minute”,”args”:[“WP Cron”],”interval”:60}

    [24-Dec-2023 11:49:58 UTC] Cron reschedule event error for hook: better_messages_cleaner_job, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”better_messages_cleaner_job”,”args”:[],”interval”:300}

    [24-Dec-2023 11:51:55 UTC] PHP Deprecated: Function get_page_by_title is deprecated since version 6.2.0! Use WP_Query instead. in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/functions.php on line 6031

    [24-Dec-2023 13:03:21 UTC] PHP Warning: mysqli_real_connect(): (HY000/1130): Host ‘127.0.0.1’ is not allowed to connect to this MariaDB server in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/class-wpdb.php on line 1987

    [24-Dec-2023 13:05:23 UTC] PHP Warning: Attempt to read property “name” on bool in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-admin/nav-menus.php on line 1215

    [24-Dec-2023 13:05:29 UTC] PHP Warning: Attempt to read property “name” on bool in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-admin/nav-menus.php on line 1215

    [24-Dec-2023 13:05:31 UTC] PHP Warning: Attempt to read property “name” on bool in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-admin/nav-menus.php on line 1215

    [24-Dec-2023 13:42:33 UTC] PHP Deprecated: Function bp_core_get_user_domain is deprecated since version 12.0.0! Use bp_members_get_user_url() instead. in /home/u604108565/domains/forextradingcommunity.com/public_html/wp-includes/functions.php on line 6031

    #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
    #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%"

    #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.

    #332483

    In reply to: BuddyPress 12.0.0

    perchenet
    Participant

    Thnak you again!
    I wrote to the Theme creator giving him your solution. I hope he could update his theme.

    BP Classic is only activated on the network (at the top level, not on the sub-site level).

    I’am afraid that my main site being very slow is due to… the multisite option.
    Thank you again!

    #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.

    #332474
    fasirathore
    Participant

    I even have changed the theme as well but it also haven’t resolved it.

    #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      |
    +----+-----------+
    #332449

    In reply to: Viewing other profiles

    alexhales123
    Participant

    To enable users to view other profiles on BuddyPress:

    1. **Install and Activate BuddyPress:**
    Make sure you have installed and activated the BuddyPress plugin on your WordPress site.

    2. **Check Privacy Settings:**
    Ensure that users’ profile privacy settings allow their profiles to be viewed by others. Users can control this setting in their profile settings.

    3. **Activate Extended Profiles:**
    Enable the “Extended Profiles” component in the BuddyPress settings to allow additional fields and information on user profiles.

    4. **Verify Theme Compatibility:**
    Confirm that your WordPress theme is compatible with BuddyPress to ensure proper display of profile information.

    5. **Check User Roles:**
    Verify that users attempting to view profiles have the necessary capabilities. By default, registered users should be able to view other registered users’ profiles.

    6. **Use BuddyPress Widgets/Shortcodes:**
    Utilize BuddyPress widgets and shortcodes to display member directories and user lists. Refer to the BuddyPress documentation for guidance on implementing these features.

    7. **Review BuddyPress Documentation:**
    Consult the official BuddyPress documentation for any specific settings or features related to profile viewing.

    By following these steps, you should enable users to view other profiles seamlessly on your BuddyPress-enabled WordPress site.

    #332443

    In reply to: BuddyPress 12.0.0

    priyam1234
    Participant

    Hello, I’m facing another issue. I am unable to set the location of “Better Messages” to “Show in BuddyPress profile.” I encountered a severe error. I’ve also tested it on the default theme, where I only activated BuddyPress and the Better Messages plugin. I’ve successfully set the Better Messages location to work with other pages. Please assist as soon as possible; it’s urgent.

    #332441
    Mathieu Viet
    Moderator

    Maybe it’s due to this bug we’ll be fixing in 12.1.0

    Can you test adding the following code to see if it’s fixing the issue into the functions.php file of your active theme for example:

    add_filter( 'bp_enqueue_assets_in_bp_pages_only', '__return_false' );

    #332435

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Hi @awol

    Thanks for your initiative, a possible way to find it is to download your /wp-content directory and use a code/text editor like vscode and use their “Search in directory” feature.

    Hi @priyam1234

    Really happy you found the way to fixing your issues 👍.

    Hi @cristan17

    Sorry to read about the issues you’re facing.

    The first thing I would do if I were you would be to make sure errors are not logged on front-end but only into your error log file: you can define WP_DEBUG_DISPLAY to false into your wp-config.php to do so, see: https://wordpress.org/documentation/article/debugging-in-wordpress/#wp_debug_display

    Then, there’s a good chance these errors are deprecated notices which means the 3rd party BuddyPress plugins or theme have not updated their code to be ready for 12.0.0. We anticipated this case building the BP Classic backwards compatibility Add-on. If you haven’t activated this Add-on with BuddyPress 12.0.0, you can try to do so to see if it fixes your issues.

    If you want to roll back once you updated BuddyPress, you’ll need the BP Classic Add-on to first find back your BuddyPress pages. Then deactivate BuddyPress and all other BuddyPress plugins except BP Classic. BP Classic will make sure you have your BuddyPress pages will stay in place. Then only deactivate BP Classic. Remove the wp-content/plugins/buddypress folder of your site. Before installing version 11.4.0, make sure to edit manually the BuddyPress db version option for the one of version 11.4.0. Into the wp_options table the _bp_db_version option value needs to be 13408.

    Here’s the download link for 11.4.0:
    https://downloads.wordpress.org/plugin/buddypress.11.4.0.zip

    #332383

    In reply to: BuddyPress 12.0.0

    jaymzwayne
    Participant

    if it also helps to know the work around is i have youzify when i deactivate that then some of the problem goes away that is a plugin i paid for and it works great gives me alot of features that i dont want to loose when i have to mess with the themes side of things or buddypress i have to turn off youzify when done turn it back on is there a way i can go back to the 11 release of budddy press

    #332364
    alexhales123
    Participant

    If you’re looking to add a background image and personalize the ‘Sign Up’ page further, you can use custom CSS. Here’s a simple example to get you started:

    css
    Copy code
    #signup-form {
    background-image: url(‘your-image.jpg’);
    background-size: cover;
    background-position: center;
    background-repeat: no-repeat;
    padding: 24px;
    }
    Replace ‘your-image.jpg’ with the URL of the image you’d like to use. You can customize the padding, background size, position, and other properties to suit your preferences.

    To implement this:

    Access your platform’s customization or theme settings.
    Look for an option to add custom CSS.
    Paste the provided code snippet.
    Save your changes.
    This should apply the background image to the ‘Sign Up’ page as per your specifications. If you have any questions or need further assistance, feel free to reach out.

    #332362

    In reply to: BuddyPress 12.0.0

    cdb44
    Participant

    Well, I had BP Classic activated event before updating to BP 12…

    About the BP_IGNORE_DEPRECATED, I’m not quite sure, it’s not in my wp_config.php, at the oposite, I added BP_LOAD_DEPRECATED as mentioned earlier in this post. I’ll have a closer look as it may come with our WAF or our theme.

    How long do you plan to maintain BP Classic ?

    #332358
    Guddu Kumar
    Participant

    Yes, it is possible to create a cricket scoring web application using WordPress. While WordPress is traditionally used for content management and blogging, it can be extended to build various types of web applications, including a cricket scoring application.

    Here are the steps you can take to create a basic cricket scoring web application on WordPress:

    1. Choose a WordPress Theme:
    – Select a WordPress theme that suits your requirements or use a sports-oriented theme. There are many themes available that can be customized to fit the design and functionality you need.

    2. Install and Configure WordPress:
    – Set up WordPress on your server and configure it according to your needs. You can use popular hosting providers like Bluehost, SiteGround, or others to host your WordPress site.

    3. Install Relevant Plugins:
    – Use WordPress plugins to add specific functionality to your site. For a cricket scoring application, you might need plugins that handle sports scoring or booking systems. Some popular WordPress plugins for sports include SportsPress, Team Rosters, and Booking Calendar.

    4. Customize and Design:
    – Customize the appearance of your site using the WordPress Customizer or a page builder plugin. Ensure that the design aligns with the branding and requirements of the cricket ground owner.

    5. Implement Cricket Scoring Features:
    – Depending on the complexity of the scoring system you want, you may need to customize or extend existing plugins or develop custom features. This may involve custom post types, taxonomies, and fields to handle match details, scores, and other relevant information.

    6. Ground Availability:
    – Implement a booking or reservation system to display the availability of the cricket ground. You can use booking plugins or customize them based on your specific needs.

    7. Real-time Score Updates:
    – For real-time score updates, consider integrating a live scoring API or implement a solution that allows the input of scores during a live match.

    8. User Management:
    – Implement user roles and permissions to manage who can update scores, edit content, and perform other administrative tasks.

    9. Responsive Design:
    – Ensure that your web application has a responsive design so that users can access and interact with it on various devices, including smartphones and tablets.

    10. Testing and Security:
    – Test your application thoroughly to identify and fix any bugs or issues. Also, prioritize the security of the application, especially if it involves user data or sensitive information.

    Keep in mind that while WordPress can be a powerful tool for web development, more complex functionalities may require a combination of existing plugins and custom development. If the requirements become highly specialized, you might also consider consulting with a web developer or agency to ensure the successful implementation of your cricket scoring web application. Also you can see this cricket schedule website for reference.

    #332356

    In reply to: BuddyPress 12.0.0

    cdb44
    Participant

    Hello Mathieu,

    we are using BuddyPress in conjonction with BBPress.

    We get this error :

    Fatal error: Uncaught Error: Call to undefined function bp_core_get_user_domain() in /path/wp-content/plugins/bbpress/includes/extend/buddypress/members.php:229 Stack trace:
    #0 /path/wp-content/plugins/bbpress/includes/extend/buddypress/members.php(100): BBP_BuddyPress_Members->get_profile_url(1)
    #1 /path/wp-includes/class-wp-hook.php(324): BBP_BuddyPress_Members->get_user_profile_url(1)
    #2 /path/wp-includes/plugin.php(205): WP_Hook->apply_filters(1, Array)
    #3 /path/wp-content/plugins/bbpress/includes/core/abstraction.php(471): apply_filters(‘bbp_pre_get_use…’, 1)
    #4 /path/wp-content/plugins/bbpress/includes/users/template.php(560): bbp_maybe_intercept(‘bbp_pre_get_use…’, Array)
    #5 /path/wp-content/plugins/bbpress/includes/replies/template.php(1280): bbp_get_user_profile_url(1)
    #6 /path/wp-content/plugins/bbpress/includes/replies/template.php(1189): bbp_get_reply_author_url(775)
    #7 /path/wp-content/plugins/bbpress/includes/users/template.php(2019): bbp_get_reply_author_link(Array)
    #8 /path/wp-content/plugins/bbpress/includes/users/template.php(1990): bbp_get_author_link(Array)
    #9 /path/wp-content/plugins/bbpress/templates/default/bbpress/loop-single-forum.php(70): bbp_author_link(Array)
    #10 /path/wp-includes/template.php(792): require(‘/path…’)
    #11 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(103): load_template(‘/path…’, false)
    #12 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(41): bbp_locate_template(Array, true, false)
    #13 /path/wp-content/plugins/bbpress/templates/default/bbpress/loop-forums.php(35): bbp_get_template_part(‘loop’, ‘single-forum’)
    #14 /path/wp-includes/template.php(792): require(‘/path…’)
    #15 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(103): load_template(‘/path…’, false)
    #16 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(41): bbp_locate_template(Array, true, false)
    #17 /path/wp-content/plugins/bbpress/templates/default/bbpress/content-archive-forum.php(27): bbp_get_template_part(‘loop’, ‘forums’)
    #18 /path/wp-includes/template.php(792): require(‘/path…’)
    #19 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(103): load_template(‘/path…’, false)
    #20 /path/wp-content/plugins/bbpress/includes/core/template-functions.php(41): bbp_locate_template(Array, true, false)
    #21 /path/wp-content/plugins/bbpress/includes/common/shortcodes.php(197): bbp_get_template_part(‘content’, ‘archive-forum’)
    #22 /path/wp-content/plugins/bbpress/includes/core/theme-compat.php(549): BBP_Shortcodes->display_forum_index()
    #23 /path/wp-includes/class-wp-hook.php(324): bbp_template_include_theme_compat(‘/path…’)
    #24 /path/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘/path…’, Array)
    #25 /path/wp-content/plugins/bbpress/includes/core/sub-actions.php(477): apply_filters(‘bbp_template_in…’, ‘/path…’)
    #26 /path/wp-includes/class-wp-hook.php(324): bbp_template_include(‘/path…’)
    #27 /path/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘/path…’, Array)
    #28 /path/wp-includes/template-loader.php(104): apply_filters(‘template_includ…’, ‘/path…’)
    #29 /path/wp-blog-header.php(19): require_once(‘/path…’)
    #30 /path/index.php(17): require(‘/path…’)
    #31 {main} thrown in /path/wp-content/plugins/bbpress/includes/extend/buddypress/members.php on line 229

    Any advice to get our site back to life ?

    #332354

    In reply to: BuddyPress 12.0.0

    hengstigal
    Participant

    Hello, i get the following error after Updating to 12.0. Could you please help me? 🙂

    WordPress-Version 6.4.2
    Aktives Theme: Cera (Version 1.2.0)
    Aktuelles Plugin: BuddyPress (Version 12.0.0)
    PHP-Version 8.1.26

    Ein Fehler vom Typ E_ERROR wurde in der Zeile 350 der Datei /homepages/10/d383743307/htdocs/######/wp-content/plugins/buddypress/bp-core/deprecated/12.0.php verursacht. Fehlermeldung: Uncaught Error: Call to undefined function bp_get_groups_directory_url() in /homepages/10/d383743307/htdocs/######/wp-content/plugins/buddypress/bp-core/deprecated/12.0.php:350
    Stack trace:
    #0 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock-buddypress/inc/widget/fields/class-grimlock-buddypress-groups-section-widget-fields.php(155): bp_get_groups_directory_permalink()
    #1 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(324): Grimlock_BuddyPress_Groups_Section_Widget_Fields->change_defaults()
    #2 /homepages/10/d383743307/htdocs/######/wp-includes/plugin.php(205): WP_Hook->apply_filters()
    #3 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock/inc/widget/class-grimlock-base-widget.php(21): apply_filters()
    #4 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock-buddypress/inc/widget/class-grimlock-buddypress-groups-section-widget.php(29): Grimlock_Base_Widget->__construct()
    #5 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-widget-factory.php(62): Grimlock_BuddyPress_Groups_Section_Widget->__construct()
    #6 /homepages/10/d383743307/htdocs/######/wp-includes/widgets.php(115): WP_Widget_Factory->register()
    #7 /homepages/10/d383743307/htdocs/######/wp-content/plugins/grimlock-buddypress/inc/class-grimlock-buddypress.php(202): register_widget()
    #8 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(324): Grimlock_BuddyPress->widgets_init()
    #9 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #10 /homepages/10/d383743307/htdocs/######/wp-includes/plugin.php(517): WP_Hook->do_action()
    #11 /homepages/10/d383743307/htdocs/######/wp-includes/widgets.php(1858): do_action()
    #12 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(324): wp_widgets_init()
    #13 /homepages/10/d383743307/htdocs/######/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #14 /homepages/10/d383743307/htdocs/######/wp-includes/plugin.php(517): WP_Hook->do_action()
    #15 /homepages/10/d383743307/htdocs/######/wp-settings.php(643): do_action()
    #16 /homepages/10/d383743307/htdocs/######/wp-config.php(116): require_once(‘/homepages/10/d…’)
    #17 /homepages/10/d383743307/htdocs/######/wp-load.php(50): require_once(‘/homepages/10/d…’)
    #18 /homepages/10/d383743307/htdocs/######/wp-login.php(12): require(‘/homepages/10/d…’)
    #19 {main}

    #332341

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Hi @yatesa01

    About this:
    > The option in customizer to use round profile images is no longer present after updating to 12.0.

    It’s not an issue, we’re removed it on purpose, to avoid messing with the active Theme’s way of displaying an avatar.
    https://buddypress.trac.wordpress.org/ticket/8273

    You can easily get it back using this CSS rule:

    
    .buddypress-wrap .avatar {
    	border-radius: 50%;
    }
    
    #332340

    In reply to: BuddyPress 12.0.0

    Mathieu Viet
    Moderator

    Hi @bmoreau92

    Thanks for your feedback.

    I agree it’s weird.

    BP Classic also brings back the BP Legacy widgets. The Latest Activities is one of them. But this widget is only available if the BP Nouveau Template pack is active. It looks like although it’s the case this template pack is not loaded which is causing the error because one of its functions is used by the Latest Activities widget.

    I’ve tried to reproduce an issue but wasn’t able. As it’s a premium theme, I cannot see what’s wrong.

    If you do not need this BP Legacy widget, you can simply unhook it and it should fix the issue. You can add the following code into a bp-custom.php file for example.

    
    function flatsome_weird_option_bug() {
    	remove_action( 'bp_widgets_init', array( 'BP_Classic_Templates_Nouveau_Latest_Activities', 'register_widget' ) );
    }
    add_action( 'bp_after_setup_theme', 'flatsome_weird_option_bug', 6 );
    
Viewing 25 results - 351 through 375 (of 32,562 total)
Skip to toolbar