Forum Replies Created

Viewing 15 replies - 1 through 15 (of 19 total)
  • beekoff

    (@beekoff)

    Hi Nikki – No solution for me (I’ve had to disable the plugin & functionality – though have been recommended Profile Builder plugin that I haven’t tested yet). Really annoying bug, as I’m stuck with it as I don’t code. And if i remember correctly, Profile Builder provides similar approval functionality with the addition of evaluating users’ xprofile fields while making approval/rejection decision (and giving the user rejection/modification feedback/retry option). If I’m right about that functionality, you might want to check it out.

    Regards,
    Sam

    Hi Michael – I have tentatively resolved this issue of suppressing the approval process for certain BP member types (again, I use BP Member Types Pro plugin by BuddyDev for member types) in conjunction with a modified version of your snippet (per Brajesh @ BuddyDev). He has updated the plugin (and snippet) to support yours.

    Here’s a link to that snippet.

    But only tentatively because there’s a weird new plugin behavior, and I want to see if you have any suggestions on resolving this.

    The issue is that although the approval process is properly suppressing the specified member type during his/her registration/login process (no pending approval warnings anymore), the plugin is oddly (1) still sending out the “pending membership approval” email to both the user and (2) the admin. And on the admin side, it’s (3) still requesting the actual approval decision, even though the user is fine.

    Thoughts?

    Thanks,
    Sam

    Forum: Plugins
    In reply to: [Glance That] Setup issue
    Thread Starter beekoff

    (@beekoff)

    Hi @uamv – I’ve just updated, and my life has instantly become easier! Thank you so much for continuing to maintain and improve this great plugin.

    Sam

    Forum: Plugins
    In reply to: [Glance That] Setup issue
    Thread Starter beekoff

    (@beekoff)

    Very cool. thank you!

    No, it’s really simple. Basic info required, and there’s a radio button with 2 selections. Individual (default) or Service. If you switch radio button to Service, you’ll see 7 additional xprofile fields that will be required. If you switch back to Individual, they get hidden. That’s it. Pretty simple.

    Go take a peek!

    https://saint-truce.staging.wpmudev.host/register/

    I sent the .htpasswd login info to your email.

    Thanks,
    Sam

    Then it sounds like BuddyPress submit button may be the issue: https://stackoverflow.com/a/28340579

    The error in question may also arise due to a premature validation. Premature validation can occur when you have a <button> input without a set type attribute. Without the type attribute of a button being set to button, Chrome (or any other browser for that matter) performs a validation each time the button is clicked because submit is the default type of buttons. To solve the problem, if you have a button on your page that does something else other than submit or reset, always remember to do this: <button type=”button”>

    Not sure where to find this code, but you buy this at all? Or have any last suggestions/direction?

    Thanks for your help,
    Sam

    I’m not much at coding, but I’m pretty sure the issue is coming from the fact that the approved member type (the one that’s working fine) gets conditional xprofile fields to fill out (which are required, so they’re getting filled in). The member profile not working, which is the basic member type (without those extra xprofile fields), I’m going to guess is somehow expecting those fields based on your code.

    Just my guess. Would it make a difference if you tweaked the code to say, if not member-type-X, use member-type-Y. Maybe forcing it in the helps?

    Thanks

    jquery-migrate.min.js?ver=1.4.1:2 JQMIGRATE: Migrate is installed, version 1.4.1
    (index):1 An invalid form control with name=’field_2′ is not focusable.
    (index):1 An invalid form control with name=’field_15′ is not focusable.
    (index):1 An invalid form control with name=’field_4′ is not focusable.
    (index):1 An invalid form control with name=’field_6′ is not focusable.
    (index):1 An invalid form control with name=’field_13′ is not focusable.
    (index):1 An invalid form control with name=’field_7′ is not focusable.
    (index):1 An invalid form control with name=’field_14′ is not focusable.
    (index):1 Unchecked runtime.lastError: The message port closed before a response was received.

    I am. I’ll post the functions.php here. Also I’ll email you at the address above a link to my staging site with creds to get past the security screen (so you can see for your self.

    Sam

    Hi Michael – I also need this solution, and have just tried it with partial success. The member type that requires approval is passing through perfectly, but the member type that does not require approval is acting up. The submit button is not processing on the form for the member type that does not require approval.

    I’m using Buddy Press Member Types Pro by BuddyDev.
    My 2 member types are: Individual (individual) & Service (service). Only Services require approval. So, individuals that do not aren’t able to submit their registration form.

    I’ve used your code above, replacing “type_value” with “service”, and placed it in my Child’s function.php.

    Thanks in advance,
    Sam

    PLEASE keep support for Classic editor (in addition to Gutenberg), as I have to use this for the important plugins I rely on; Metabox.io and custom plugins. Thank you!

    Thread Starter beekoff

    (@beekoff)

    The following was from support via WPMU, which resolved the issue:

    The above error seems to be part of the Anti Splog plugin. Please do note that Anti Splog plugin hasn’t been tested, nor is compatible with WP Multi networks plugin. That might be the reason for the anomalies.

    Could you please deactivate the Anti Splog plugin temporarily, and create a new Network, and see whether you still get the same issue, or not, with the new network?

    Thread Starter beekoff

    (@beekoff)

    Oops…Sorry about the ALL CAPS title! My bad

    Hi Jim – I’m hopefully missing something obvious, but I can’t seem to get the Pods address field to display text output through Beaver Builder. Not even attempting maps output – stuck at step 1. And no problem adding any other Pod fields btw.

    Much thanks,

    Sam

    Pods – Custom Content Types and Fields Version 2.7.9
    Pods Address Field Version 1.0
    Pods Maps Version 1.0
    Pods Beaver Themer Add-On Version 1.3.1
    Beaver Builder Plugin (Agency Version) Version 2.2.0.1
    Beaver Themer Version 1.2.1.1

    • This reply was modified 7 years, 5 months ago by beekoff.
    beekoff

    (@beekoff)

    Got it. Need to ftp instead.

Viewing 15 replies - 1 through 15 (of 19 total)