Security Alert: 26 BuddyDev accounts compromized in brute force attack.

BuddyDev

Search

Replies

  • Participant
    Level: Initiated
    Posts: 6
    Filip Alexander on January 14, 2025 at 10:54 am #54656

    1. Totally, I love playing inside the plugins, so I very appreciate your open mindset to it!
    2. Thank you so much for that! I really don’t mind customizing the code myself, I do some work myself on almost every plugin I get, I just need a little nudge in the right direction and I hope i could do the rest, I know you must be insanely busy so Im really happy you even take your time to reply to me.
    3. Please don’t be, it’s just a typo, nothing big haha, don’t worry about it!:)

  • Participant
    Level: Initiated
    Posts: 6
    Filip Alexander on January 14, 2025 at 10:40 am #54652

    Hi,

    1) thanks for your reply, i will definitely look into it!

    2) I did try that but sadly it didn’t work :/ Could I have a different question regarding this? Currently, you can only do Logged-in user LIKE potential match, which means currenty it works such as “If logged-in single value field match anything in potential’s match longer text, it will match” – I tested this by switching the profile fields, as in the matching was done that potential match field was multi select while logged in user was single value (dropdown or just a word in text field) and it worked. Could you please point me to a possibility that I could internally “Switch” the logged-in and potential match in the query? So that i would check potential match single value LIKE logged-in multi select?

    3) I already found the issue haha, it was a typo. In a template file for the buddyboss widget, you specified a path theme/buddypress/members/friends-suggestions-pro/default/widgets/, but it is actually theme/buddypress/members/***bp-***friends-suggestions-pro/default/widgets/, i realized when i looked into the original file path, so all good there.

    Thank you again for your time and effort, i really appreciate it very much!

  • Participant
    Level: Initiated
    Posts: 6
    Filip Alexander on January 13, 2025 at 10:36 am #54639

    Hi,

    Thanks for the reply.

    1) thats a shame :/ do you think it would be possible to do at all?

    2) well the thing is i need to compare two fields that are different kind, for example a multiselect checkbox and a dropdown, any way to do this please? Or in case it doesn’t work in current setup maybe you could point me in the direction of how it could be achieved by modifying the code?

    I saw in and not in inside the code commented out, maybe i could use that?

    3) i used exactly this path and it didn’t override the plug-in template :/

    Thanks in advanfe for your reply.

  • Participant
    Level: Initiated
    Posts: 6
    Filip Alexander on January 11, 2025 at 2:04 pm #54581

    Hi,

    sorry me again. One last question (so you can answer them all at once). In your template for the widget, you have a comment like this:

    * You can override it in your theme/buddypress/members/friends-suggestions-pro/default/widgets/

    But when i actually put the file in this path in my child theme it doesn’t work :/

  • Participant
    Level: Initiated
    Posts: 6
    Filip Alexander on January 11, 2025 at 9:55 am #54562

    Hi,

    sorry for the double post, but I just found out something – when I use like, it doesnt work with arrays, meaning if I use LIKE and the logged in users profile field is a string, it won’t match users at all.

    Like for example we have two field groups – About Me and Looking for. They share profile fields – in About me, you insert data about you and in Looking for you insert data your ideal match should have.
    Lets say we have a field Body Type, the logged in user picks “Regular” from the dropdown and picks “Regular, Slim, Fit” from multiple choices in “Looking for”, i then set the rule that when logged in users “Looking for Body type” matches with “About me Body type” of a different user, its match, but it doesn’t work, because the logged in users data is array while the matched users is a string and currently there’s no way to set it up in the opposite way (matched user body type LIKE logged in user looking for body type).
    Any help pls?

  • Participant
    Level: Initiated
    Posts: 6
    Filip Alexander on January 11, 2025 at 8:54 am #54561

    Hi, no problems at all haha, happens to the best of us.
    Regarding my question – I already found out how “like” and “not like” works – its a query based argument, works kinda like “contains”, right?
    So i would only love to know if there’s any chance to modify the plugin so that certain percentage/amount of conditions is met.

    I tried to look through the code and saw that its working based on AND or OR, so maybe let’s say we have 5 conditions, if first 2 match, then check if any of the remaining 3 match and if yes, match?

    Thank you very much for your time and answer!