Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 151 through 175 (of 212 total)
  • @emaralive

    Moderator

    Hmmm… is this a production or development or staging site? We know the constant is being set. Would someone actually use a base64_decode hack to hide the fact?

    @emaralive

    Moderator

    Well that’s odd unless someone has used the const keyword to define it. Search for just BP_GROUPS_DEFAULT_EXTENSION and see what that finds.

    The Bottom line is that this constant is being set to the value of “forum”, just need to find how and where.

    @emaralive

    Moderator

    Thanks,

    BP_GROUPS_SLUG (deprecated), as indicated is deprecated and shouldn’t be defined/used. However, BP_GROUPS_DEFAULT_EXTENSION is defined as “forum” which is what is causing the initial 404 redirect (page not found). Apparently, there was a “forum” nav item for any given group and now there is not therefore, that page can’t be found.

    Somewhere, perhaps wp-config.php, there is a line that contains define( 'BP_GROUPS_DEFAULT_EXTENSION', 'forum' );, find it and either remove it or comment it out and then you won’t need the redirect plugin. Perhaps, the bbPress plugin was previously activated and all groups had “Group Forum” enabled and thus the constant being defined as it was.

    @emaralive

    Moderator

    @asmaajaved – out of curiosity, I’m interested in knowing the value that is set for the BP_GROUPS_DEFAULT_EXTENSION constant. This information can be found within the Site Health Info tab, e.g., wp-admin/site-health.php?tab=debug, scroll down to the last panel (BuddyPress Constants) then open the panel and find the aforementioned constant.

    This might provide an additional clue as to what may be occurring.

    @emaralive

    Moderator

    Let’s not do that, I would prefer not to get involved in that way.

    It looks like after group creation, there should be a 302 redirect to the newly created group page. Since you are able to delete groups, I assume you are doing so from wp-admin > groups page.

    Notwithstanding the 302 redirect after group creation. Since the groups appear to be created, you should be able to access any of the created groups directly, e.g.:

    https:example.com/groups/new-group

    I’m not sure if this is actually a BuddyPress issue.

    I’ll ask around and see if anyone else on the team has heard of this.

    @emaralive

    Moderator

    Unfortunately, I’ve not seen this before, so it may take a while to figure what is going on. Until I can duplicate this anomaly, it is hard to say what a fix would be.

    @emaralive

    Moderator

    For some reason you are getting a 404 page (Page not found”). Does this happen immediately after you create a group? Meaning, after creating a group you should be taken to the newly created group page but you are redirected to a 404 page, is this correct?

    Also, this anomaly happens with all group types (public, private & hidden)?

    @emaralive

    Moderator

    Hi @davesumpter,

    It would depend on the theme in use on how you would edit the Site Title link, assuming the Site Logo has the same link as the Site Title, you would use a URL similar to:

    https://example.com/members/me

    The “me” is the default shortlink redirector member slug. IOW, this will redirect to the profile area of the logged in user, typically, their activity stream/feed

    @emaralive

    Moderator

    Hi @jrpmedia,

    Were you able to resolve this issue?

    @emaralive

    Moderator

    Hi @asmaajaved,

    I’m not sure if this an edge case, so more information is required, e.g.:

    1. WordPress version
    2. WordPress permalink setting(plain or pretty URLs)
    3. WordPress theme in use
    4. BuddyPress version
    5. BuddyPress template pack in use
    6. What does your error log reveal?

    It would also help to have a screenshot of:

    the single groups pages show up empty

    @emaralive

    Moderator

    Hi,

    The BuddyPress Featured Members plugin appears to be authored by BuddyDev. Have you tried their support forum?

    BuddyDev Support – BuddyDev site

    Or

    [BuddyPress Featured Members] Support – WordPress Forum

    @emaralive

    Moderator

    @cactuscat

    What is your permalink structure set to, e.g., plain or pretty URLs?

    @emaralive

    Moderator

    Unfortunately, you’ve applied a band-aid at the Theme level. The next Theme update will remove your band-aid and you will have to apply it again, given the approach you’ve taken.

    The bp_loggedin_user_domain( ) function should have returned a URL with a trailing slash, for example:

    http://www.url.com/members/username/

    Which is why the Theme has it written as:

    bp_loggedin_user_domain() . $bp->notifications->slug

    Something is causing the trailing slash to be missing, solving for this will be the fix. Maybe a plugin or some custom code is filtering the return value, such that is stripping the trailing slash.

    Assuming you are using BuddyPress 14.3.3, see the following URL for the source code:

    bp_loggedin_user_domain()

    @emaralive

    Moderator

    OK, sounds good, I’m glad you were able to figure out the cause. May I consider this topic resolved?

    @emaralive

    Moderator

    Hmmm… that seems odd. What does your error log reveal and does Site Heath Status reveal any critical issues?

    @emaralive

    Moderator

    Hi @antipole,

    It is difficult to say but, normally, there would be a redirect to the wp-login.php, given your example:

    https://mysite.org.uk/members/myusername/messages/view/572/

    The above would, normally, redirect to:

    https://mysite.org.uk/wp-login.php?redirect_to=https%3A%2F%2Fmysite.org.uk%2Fmembers%2Fmyusername%2Fmessages%2Fview%2F572%2F&bp-auth=1&action=bpnoaccess

    The redirect is due to a page that requires authentication and if not authenticated, there is an attempt to redirect to wp-login.php. Since this does not happen, it may be that your Redirect plugin is bypassing wp-login.php and redirecting to your 404 page, instead. I’m not sure if this is configuration issue with the Redirect plugin or just the way it works or if there is another cause.

    In a nutshell the flow is:

    1. bp_core_no_access()
    2. bp_core_redirect()
    3. wp_safe_redirect()

    @emaralive

    Moderator

    OK, sounds good, I was just checking to see if you needed further assistance.

    @emaralive

    Moderator

    Hi @richardrcook2,

    Is this still an issue for you?

    @emaralive

    Moderator

    Hi,

    I”m not sure if it is Wordfence interfering with the upgrade process or some other plugin that might be causing the issue. What does your error log reveal?

    @emaralive

    Moderator

    Hi @mike80222

    This is an issue with bbPress and there is an open ticket Deprecated Warning ##3589 in bbPress Trac.

    You will have to ask the folks over in bbPress as to the status of this ticket.

    @emaralive

    Moderator

    Hi @dreampixel,

    Thanks for bringing this to my attention. It looks like some of the notifications are not being deleted when in actuality all should be deleted that are related to the deleted user.

    For example:

    • new_membership_request <- this is what you initially indicated
    • bbp_new_reply <- this what you indicated next
    • new_message <- notification for Private Messages

    The issue is that the function that deletes notifications in the event of a deleted user does not take into account that some notifications have the user_id of deleted user placed in the secondary_item_id column in the bp_notifications`database table.

    Long story shorter, I have a tentative patch that I am testing that will provide a remedy for this bug. I’ll create a ticket for a fix once I’m satisfied with the patch. I’ll keep you updated as to the progress and I’ll try to fit this into the next available release.

    @emaralive

    Moderator

    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

    Moderator

    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

    Moderator

    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

    Moderator

    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?

Viewing 25 replies - 151 through 175 (of 212 total)
Skip to toolbar