[@emaralive Participant 2 weeks, 2 days ago]

Hi,

The CSS file that gets loaded depends on which template pack is in use, e.g. Legacy vs Nouveau. Additionally, styles (CSS) can be customized via a Child theme and, if a Classic theme is in use, via the Appearance > Customize > Additional CSS menu path within the wp-admin area. Thus, which CSS file gets loaded is irrelevant/moot.

Specific to Avatars, How to Customize BuddyPress Avatars With CSS has some info (Note: might be a tad outdated). There are other sources on wordpress.org that contain general info regarding custom CSS, e.g. from the Advanced Administration Handbook – Custom CSS in WordPress

Hopefully, this is enough information to get you started.

[@emaralive Participant 2 weeks, 5 days ago]

Hi @glenphillips33,

Anything is possible, what’s unknown is the probability. IIRC, I had a similar experience, but it involved the wordpress.org site and drop-down menu items that affected Chromium on a AlmaLinux distro. Google Chrome worked fine as well as Firefox. On a Ubuntu and Debian distros (Linux), Chromium work just fine, as was with Windows 10. Long story shorter, eventually, the AlmaLinux distro received an update with a new Chromium build that fixed the issue with Drop-down menus.

That said, it doesn’t seem likely for a Windows platform since Google Chrome should be automatically updated and is usually ahead (stable release) of Edge, Opera and other browsers that share the Chromium engine or, maybe you are using cutting edge/beta releases/builds but, as previously mentioned, anything is possible.

If you want to supply the Web URL, I suggest you add that to your BuddyPress Profile, there is a field specific for this purpose (Web URL). That way, you can remove it later, if you don’t want the URL to remain public. I can then either confirm or deny whether I see something unusual while visiting a profile area with Google Chrome.

Next up are a couple of housekeeping items, that you require your attention, of which should not be related to the issue you reported in this thread.

(1) BuddyPress 12.4.1 is not compatible with WordPress 6.7.x. The effect is that your server error log(s) are filling up with an error notice, e.g.:

Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>.
Translation loading for the <code>buddypress</code> domain was triggered too early. This is
usually an indicator for some code in the plugin or theme running too early. Translations
should be loaded at the <code>init</code> action or later. Please see <a
href="https://developer.wordpress.org/advanced-administration/debug/debug
-wordpress/">Debugging in WordPress</a> for more information. (This message was added in
version 6.7.0.) in /var/www/html/wp_test/wp-includes/functions.php on line 6114

The solution is to either to roll back WordPress to version 6.6.2 or upgrade BuddyPress to version 14.3.3.

(2) BuddyPress 12.4.1 is missing 2 security patches, if you are going to continue to use the BuddyPress 12.x branch, it is recommended that you upgrade to BuddyPress 12.5.2, see If you are using BP 12.x and can’t upgrade to 14.2.1, and apply (1), accordingly.

[@emaralive Participant 2 weeks, 6 days ago]

Hi @stephunique,

Long story short, the “screenshot” file is added to the wp cache, e.g., $this->cache_add( 'screenshot', 'screenshot.' . $ext );.

Additionally, it appears that the extensions for the “screenshot” file can be any of the following 'png', 'gif', 'jpg', 'jpeg', 'webp', 'avif'.

Last but not least, in the future, it would, most likely, be best to ask WordPress related questions in one the WordPress related forums.

[@emaralive Participant 2 weeks, 6 days ago]

Hi @ph59,

I am unable to duplicate the issue that you are reporting. The following conditions were checked and the behavior is as expected:

• sites that are configured with SSL will load https when https is used in the xprofile URL field.
• sites that are configured with SSL will load https when http is used in the xprofile URL field.
• sites that are not configured with SSL will load http when http is used in the xprofile URL field.
• sites that are not configured with SSL will show security warning when https is used in the xprofile URL field.

IOW, I’m not finding any evidence that https is being changed to http or http is being changed to https.

Are you using any plugin(s) that may be modifying how the xprofile fields would normally work?

[@emaralive Participant 2 weeks, 6 days ago]

Hi,

BuddyDev has a commercial plugin, BuddyPress Profile Data Moderator, that may serve your purpose. If you are looking for something free then you should search the WordPress Plugins Directory, if you’ve not done so.

[@emaralive Participant 2 weeks, 6 days ago]

Hi @glenphillips33,

My apologies for a belated response but, my default browser is Chromium (just a preference thing) on a Linux platform and all looks as expected. Although, Chromium, Google Chrome, Microsoft Edge, and others share the same basic engine, there may be differences in builds across the various OS platforms. Without knowing more information, it is difficult to assess the issue. For example, we currently don’t know, at a minimum, which may or may not prove to make a difference:

• WordPress version
• BuddyPress version
• PHP version
• BuddyPress template pack in use
• If you have tried using a WordPress default classic theme (non block theme or non FSE)

The layout appears broken, with profile sections overlapping or not displaying at all.

This is a generalization, meaning there isn’t enough specificity to truly understand the situation. Perhaps, a screenshot would suffice without having to visit your site.

Here is my setup as it relates to the following screenshot of an arbitrary Profile page with Google Chrome:

• WordPress: 6.7.1
• Active Theme: twentyeleven child theme (twentyeleven-child)
• PHP: 8.2.25
• OS: AlmaLinux 9.5 (Teal Serval)
• Browser: Google Chrome – 131.0.6778.85 (Official Build) (64-bit)
• Page caching: No
• Object caching: No
• BuddyPress: 14.3.3
• BuddyPress URL Parser: BP Rewrites API
• BuddyPress Active template pack: BP Nouveau

For me, the profile area renders as expected with Goggle Chrome based on the given setup. I also looked at the same page with Windows 10 and Google Chrome (131.0.6778.86 (Official Build) (64-bit), logged-in and logged-out and it looks the same. I don’t have a Mac, so I can’t provide a verification. Also, I’m serving up the profile page from a development site on my LAN.

[@emaralive Participant 3 weeks, 1 day ago]

Hi,

BuddyPress 14.3.3 Maintenance Release fixes the issue with “deprecated class” error messages.

Please upgrade at your convenience.

[@emaralive Participant 3 weeks, 3 days ago]

Hi,

Thanks for reporting this issue, I can confirm the error messages for the BP REST API when using the BP Nouveau template pack. Unfortunately, something went wrong with the build and these errors didn’t get caught when testing the build. 14.3.1 was released to fix an issue with WordPress 6.7 (_load_textdomain_just_in_time issue) and another issue (heartbeat) with the BP Legacy template pack.

Looks like we need another build to get this fixed. At the moment, the only recourse is to roll back to 14.2.1 and continue to use WordPress 6.6.2.

My apologies for the inconvenience.

[@emaralive Participant 3 weeks, 4 days ago]

Hi @dreampixel,

BP 15 was taking too long to get in motion, so the BP team decided to incorporate the fix for this within the BP 14.3.1 maintenance release.

Thank you for your patience!

[@emaralive Participant 3 weeks, 4 days ago]

BuddyPress 14.3.1 is available which resolves this topic.

[@emaralive Participant 3 weeks, 4 days ago]

BuddyPress 14.3.1 is available which resolves this topic.

[@emaralive Participant 3 weeks, 6 days ago]

Hi,

It is difficult tell since the error message is missing backtrace info. Furthermore, I’m not getting that error with:

• WP 6.7
• BP 14.2.1
• PHP 8.3

Just for GP and long story short, I placed the function bp_get_the_profile_field_id(); in functions.php of a child theme in an attempt to replicate the error. Query Monitor revealed the error was caused by the aforementioned function, see the following screenshot:

[@emaralive Participant 4 weeks ago]

My apologies for the inconvenience, the BP Team is aware of this issue (see Trac ticket #9247) and the tentative plan is to deploy a minor release (14.3.0) for a fix. Unfortunately, at this moment, I don’t have an ETA.

[@emaralive Participant 4 weeks ago]

Hi,

My apologies for the inconvenience, the BP Team is aware of this issue (see Trac ticket #9247) and the tentative plan is to deploy a minor release (14.3.0) for a fix. Unfortunately, at this moment, I don’t have an ETA.

[@emaralive Participant 1 month ago]

Hi @miednr,

I’m not sure why you are having difficulties with a BuddyPress installation on a multisite whereby blog posts are not showing up in the Activity stream when configured to do such.

At the moment, I’m not able to duplicate your situation because blog posts are showing up in my Activity stream in a multisite installation. As can be seen in the following screenshot:

Since blog posts work for me and not for you, we need to figure out the difference(s) in our installations and what I have as the basics are (running on a LAN):

• WordPress 6.7 – multisite with subdirectories
• BuddyPress 14.2.1 – network activated on secondary site
• All BuddyPress components activated
• Default BuddyPress options plus “Post Comments” enabled
• TwentyEleven theme used on secondary site
• Pretty permalinks used on secondary site

Additionally, the installation guide I used is “Case 2” from the following document:

BuddyPress Activation Guide for WordPress Multisite

Maybe if we start on some common ground, we should eventually figure out what may be going astray with your installation, well at least that would be the theory.

[@emaralive Participant 1 month, 1 week ago]

Hi @impartialintel

This question should be asked in the previous topic you created -> Allowing only $content with urls to be posted(Error.

The reason is to provide continuity and context to your original request since this topic is directly related. As it stands, this topic is without context and someone would have to connect the dots between this topic and your previous indicated topic in order to understand with specificity and provide some reasonable response.

So, if I can get you to post what you posted above in the indicated topic, we can continue the conversation and get you closer to your desired goal.

[@emaralive Participant 1 month, 1 week ago]

Hi @impartialintel,

You seem to be confused between Actions vs Filters. Additionally, bp_activity_before_save is clearly an Action as can be seen by the following:

do_action_ref_array( 'bp_activity_before_save', array( &$this ) );

The reason you are receiving the error message is because the aforementioned action is only passing 1 (one) argument $this (object) while your callback is expecting 9 (nine) arguments thus, there are “Too few arguments to function bp_require_link_in_activity(), 1 passed” as the error message has indicated.

[@emaralive Participant 1 month, 1 week ago]

Hi @dreampixel,

So as not to leave you in the dark, the ticket that @imath had referenced was incorporated in the release for BP 15.0. The 1st beta release was previously scheduled for release during the week starting with the 4th of November but, there was a decision to push the 1st beta release by 2 weeks (approx. the 19th of November). The final release will depend on the number of beta and release candidate (RC) are involved.

Since this release schedule (BP 15) is in flux, I’ll try to keep you abreast of dates for this release cycle as they solidify or change.

[@emaralive Participant 2 months ago]

This topic has been resolved by BuddyPress 14.2.1 Maintenance & Security release.

[@emaralive Participant 2 months ago]

Trac ticket #9245 was created to resolve the reported issue.

[@emaralive Participant 2 months, 2 weeks ago]

Hi @usercba, thanks for reporting this issue,

I can duplicate this issue by:

• Disabling the Extended Profiles component.
• Visit the Site Health Info tab.

PHP 7.4 provides error warning, i.e., Use of undefined constant, for 2 Constants – BP_XPROFILE_BASE_GROUP_NAME and BP_XPROFILE_FULLNAME_FIELD_NAME. With PHP 8.x, operation halts with a fatal error for BP_XPROFILE_BASE_GROUP_NAME.

A Trac ticket will be opened to resolve this issue ASAP.

[@emaralive Participant 4 months ago]

@mike80222, when composing a message, the “@” applies to the BuddyPress Nouveau template pack, i.e, the label reads “Send @Username” as opposed to the BuddyPress Legacy template pack that reads “Send To (Username or Friend’s Name)” and I’m not sure why it is not the same for both but, that is current behavior. As to the inconsistency for when suggestions appear or not appear is a puzzle, at the moment.

@stephunique, it is possible to filter the suggested usernames by utilizing the bp_core_get_suggestions filter. If you only want to apply this filtering to messages (compose) then your callback needs to be location aware (what/which page/screen is active/loaded), as well.

[@emaralive Participant 4 months ago]

Ugh, @venutius, I didn’t realize that you had already responded.

[@emaralive Participant 4 months ago]

The create_function() was deprecated as of PHP 7.2.0 and was removed in 8.0.0 (see create_function). Since you are using PHP 8.x then, it would be best to not use this plugin until it has had all compatibility issues resolved. On another note, there seems to be some interest by individuals other than the original developers to provide some sort of future support for this plugin (see Would like to take over this plugin, or help – Support forum for BuddyPress Follow).

[@emaralive Participant 4 months, 3 weeks ago]

@whyknott I would have posted this sooner, but I was looking into the relationship between the BP_AVATAR_ORIGINAL_MAX_WIDTH CONSTANT and cropping preview area, which requires a deeper dig into this process. Neither here nor there, as previously mentioned, I don’t recognize any of the filters that end in ‘_resize_args’ and AFAIK, there are technically 2 (two) but the one I used has the hook name of:

bp_after_attachment_avatar_edit_image_parse_args

To elaborate further, there is a bp_before_..._parse_args and a bp_after_..._parse_args, FWIW. Moving along, your custom_bp_avatar_quality callback function should work with this hook, IOW use the following to set the resize quality for Avatar:

add_filter( 'bp_after_attachment_avatar_edit_image_parse_args', 'custom_bp_avatar_quality' );

This should remove any questions or concerns about the jpg/jpeg compression level, i.e., “quality”. assuming that a value of 100 is used for resize and crop. If the Avatar is still “horribly blurry” or utilizing your new term “lousy” then the issue resides elsewhere, e.g., scaling/zooming the Avatar to something greater than 100%. Since I don’t know your scenario/situation, I’ll stop at this point.