BuddyDev

Search

Replies

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 25, 2019 at 6:01 pm #22606

    FYI, Brajesh. It’s my post to WordPress support (BuddyPress Registration Options):

    https://wordpress.org/support/topic/2-member-typed-different-registration-permission/page/2/#post-11467697

    Regards,
    Sam

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 25, 2019 at 2:54 pm #22596

    Oh yeah, almost forgot…would you mind if I posted your snippet on his support page?

    Thanks,
    Sam

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 25, 2019 at 2:11 pm #22595

    Brajesh – You are right! It does work (on your end, and with your snippet – Michael’s snippet does not). I’m not sure what I did wrong yesterday, but regardless, thank you, and it works.

    The BP Registration plugin is actually having issues where it’s properly suppressing the approvals process to the user, but still requiring approval on the backend. I’ll reach out the the author.

    And lastly, one small observation about your recent update to BuddyPress Member Types Pro. When a user forgets to fill in a conditionally displayed required field (based on member type), the screen isn’t highlighting where the error is (message and/or box highlight) like it does for the regular BP fields. Not the end of the world, but on forms with a bunch of fields, it can be difficult to locate the missing required field.

    Thank you so much for your help, and I’m still making my notes on Approvals (I haven’t forgotten).

    Thanks,
    Sam

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 24, 2019 at 1:59 am #22543

    Hi Brajesh – Yes, the BP Approvals plugin is active (as well as your plugin too, of course – even the conditionals one). The approvals is working, but it’s just that the snippet is supposed to “suppress” the approval process for one member type (“individual”, in my case, while passing all other member types through the approval process). However, the original snippet from the BP Approvals guy isn’t suppressing anything (all member types are going through the approval process), while your snippet is giving off a server 500 error (this didn’t happen before).

    Thanks,
    Sam

    P.S. And FYI, the Conditionals plugin isn’t working properly (in my observation) under a certain condition. I haven’t much played with it before, so perhaps this is the way it has always been. Don’t know. But for example, if a field X is to be shown only if selection Y is chosen, it’s being shown before selection Y is chosen, and subsequently hidden after selection Z is chosen instead (not Y). I have noticed that this conditional issue can be solved if I unselect all member type choices. However, then the field that’s now properly being shown conditionally is no longer appearing in the member’s BP profile and can’t therefore be edited (kinda defeating the purpose of having the field filled out in the first place). Hopefully you followed my logic!

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 22, 2019 at 8:34 pm #22519

    Hi Brajesh – I’ve updated to 1.3.3, and oddly (to me) now both your snippet (https://buddydev.com/support/forums/topic/possible-bug-exposed-via-bp-member-types-pro-bp-registrations-options-plugin/#post-22316) and the original BP Approvals plugin snippet doesn’t work. I’ve tried each separately, and his just isn’t doing anything, but yours is causing a Server 500 error. Would you mind offering me another look at your modified snippet?

    But for what it’s worth at this point, the submit button has not been an issue!

    Thank you!
    Sam

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 18, 2019 at 1:51 pm #22411

    I will begin making some notes!

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 18, 2019 at 1:42 pm #22408

    Hi Brajesh – This is why I made the hint about you taking over that Approvals plugin (I didn’t mean forking it, btw, but just doing a better BuddyDev version of it)…because you’re always updating and adding features, where the other guy really has not (the wonders of capitalism!). Thank you very much for keeping up on this conditionally hidden xrofile fields issue. I’m really impressed. And I will take a stab at your solutions this afternoon when I get a chance, and look forward to your plugin’s permanent fix/update some time next week (if I’m understanding correctly).

    Thanks again,
    Sam

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 18, 2019 at 1:10 pm #22400

    Hi Brajesh – I’ve got a few responses on Buddypress support from @Ventutius (moderator). He has posted a solution that I can’t get to work yet. Maybe you want to jump in, as it’s likely a workaround solution you can add to your documentation. Like I said, I can’t get it to work yet, but he seems to think it should. Hope you can take a look! Please let me know if you see any errors in proposed snippet.

    https://buddypress.org/support/topic/bypass-email-requirement-2/#post-305046

    Thank you!
    Sam

    P.S. Here’s my original post: https://buddypress.org/support/topic/ability-to-conditionally-hide-required-xprofile-fields/

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 18, 2019 at 1:04 pm #22395

    Thank you, Brajesh!

  • Participant
    Level: Enlightened
    Posts: 25
    Sam Morris on April 16, 2019 at 7:27 pm #22343

    Hi Brajesh – Ugggh!

    That really sucks, as it invalidates my whole registration process. I need to conditionally hide required fields. Absolutely need to. And seems pretty normal to me. So I am thinking of posting a bug report on BuddyPress support. It seems like a bug to me. The idea that the BP registration process doesn’t account for conditionally hiding required fields must be an oversight (or else that it doesn’t allow plugins to override this). Do you agree about this being a Buddypress oversight/bug? Just curious.

    Thanks,
    Sam