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

BuddyDev

Search

Replies

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 21, 2024 at 12:05 pm #53049

    Thanks Ravi this is now resolved

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 16, 2024 at 11:58 am #53032

    Thanks for the updated code

    I am using the profile privacy plugin and while using your updated code I am receiving the 404 error correctly but the url is in this format https://site.com/members/mike/visibility-protected/.

    I dont think it’s cool to show the (visibility-protected) slug for admins since it reveals that the admin account is available but just hidden

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 12, 2024 at 9:37 am #53014

    maybe adding the POST FORM slug parameter or form ID to the shortcode would be an option see example below

    [bbl-create-by-post-type post_type=’post’ slug=’admin-post-form’]

    [bbl-create-by-post-type post_type=’post’ slug=’subscriber-post-form’]

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 9, 2024 at 2:27 pm #53008

    I also think having this in the admin stealth mode plugin would be awesome

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 8, 2024 at 2:12 pm #52996

    You are a GENIUS

    I just tested this and it works flawlessly

    Thanks a lot

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 6, 2024 at 11:35 am #52944

    Hi Ravi

    Any update yet

    Thanks

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 2, 2024 at 10:56 am #52916

    This issue is now fixed

    Thanks

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 2, 2024 at 9:55 am #52915

    Kindly ignore this as I found solution in member types pro plugin

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 1, 2024 at 1:29 pm #52912

    The main reason why I want the restricted profile fields in another profile field group is because of user experience with logged in users who are editing profile fields.

    1. conditional visibility feature does not work for users who are editing profile fields so all restricted profile fields are visible to users which is a poor user experience.

    2. Separating the restricted field into another field group would be a better experience since logged in users first need to save their chosen member type option in the primary field group before they can save the corresponding restricted profile field in the custom profile field group.

  • Participant
    Level: Guru
    Posts: 900
    Tosin on August 1, 2024 at 12:53 pm #52911

    The member type field is located in the primary field group while the restricted profile fields are located in another custom profile field group.