denstl

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 26 total)
1 2
  • Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] There has been a critical error on this website.
    Thread Starter denstl

    (@denstl)

    11 months, 3 weeks ago

    Thanks. I don’t even see where that setting might be, if it exists (only see something like that on the Login form settings). But I think I narrowed down the problem to be an issue with sending email using our Google account. I either have to reset Google Authorization or switch to a different email option. Might be time to switch email settings. But thank you for the suggestion.

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Require email verification before creating a new user
    Thread Starter denstl

    (@denstl)

    5 years, 2 months ago

    My issue is that you pick one or the other. What I would like would be to set it to “Require Email Activation” and after the Requestor does that, it changes to “Require Admin Approval”, That would make sure they provided a valid email address and once validated, the Admin reviews and approves. All the UM generated emails would then work as well.

    I did change to use “Require Email Activation” and use a default Role that has no rights. I say that almost works since if someone authenticates their email they automatically get approved with no Admin update required. In our Use Case, the Admin really has to go in and review their request and if valid, change their role. Only at that point are they approved. The Admins are not doing that until the person authenticates their email. I think I will recommend that they review the request even before the person validates their email address and if valid, change their role. That way they do not have to continuously go back and look to see if they validated the email. Our issue is that the automatic emails are not matching up with the process.

    If we change back to “Require Admin Approval” someone like this pest who keeps trying to sign on using a long list of email addresses does not have to validate they have a valid email address. Not once with 100s of attempts did they validate one of the email addresses used. They obviously have a list of “hacked” email addresses. Surprised no one has replied asking why they got one of the activation emails.

    What would be nice is if we could use “Require Email Activation” and then once they validate the email address the system would then change status to “Require Admin Approval”. That would generate the automatic UM mails about Pending Review, Approved or Rejected. The way it is now is you have to pick one or the other.

    Or, maybe add reCaptcha to help fend of people like this. I do believe in this case it is a bot submitting these as I took away the Register link and they still were going direct to that page. I had to remove it altogether for now to stop them. No idea why they are so persistent. Nothing that interesting for them to get access to…

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Require email verification before creating a new user
    Thread Starter denstl

    (@denstl)

    5 years, 3 months ago

    That gets us back to where we started. Require email activation almost works. But when they validate they go right to approved. We change the default role to a role that provides no additional access. Once they validate using the generated email they are approved but the admin then has to change their role. No problem doing that but they need to keep checking to see if they have validated as they do not get notified when they do. Once they see they have in order to get the plug in to generate the Account Approved email they have to first change the status to “Put As Pending Review” (have turned off the email generated by plug-in for this stage), change the role to the one that gets access, and then change the status back to “Approve Membership”. That last change generates the email letting the requestor know they now have access.

    There is no way to go from “Awaiting E-mail Confirmation” to “Pending Review” or the Admin to be notified once the requestor validates their email. But our process will work it just requires the admin to keep checking to see if the new requestor has validated yet.

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Require email verification before creating a new user
    Thread Starter denstl

    (@denstl)

    5 years, 3 months ago

    I did change our site to use this feature. Only thing I don’t like is that when they click the activation link on their email they are automatically approved. Would prefer that the Admin still had to approve them. To get around that I have them get assigned to a role that has no access rights so they only see what the non-logged in user sees. The Admin now has to move them to the role that does get access rights. Not ideal and the Admin cannot use the generated email to know to approve them. But they will just leave that as an unread email until the person activates their account. Then they will change their role and delete the email they get. Could be many days before the person requesting access actually clicks on the activation link so the Admin has to keep going back in to see if they activated their account. Instead of approving them they now have to change their role. We’ll give it a go. Only been one person who has been really abusing the access request 10-20 times every day. Being an approved user does not really gain them all that much other than access to some preschool calendars and a few other pages of content for parents. But “James Smith” who has hundred of emails address just keeps on trying…

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Require email verification before creating a new user
    Thread Starter denstl

    (@denstl)

    5 years, 3 months ago

    Wow, never knew that was there and exactly what we need. Thank you so much for the quick reply and even more so for this great product!

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Visual Composer compatibility issue?
    Thread Starter denstl

    (@denstl)

    5 years, 8 months ago

    Strange. That release solved my issue immediately. Right now I am at Ultimate Member release Version 2.1.11 and Visual Composer release Version 30.1. It was the UM release that solved the issue for me.

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Visual Composer compatibility issue?
    Thread Starter denstl

    (@denstl)

    5 years, 8 months ago

    lifedsire – The fix was really with the Ultimate Member plugin. It is part of their latest release (Version 2.1.11)

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Visual Composer compatibility?
    Thread Starter denstl

    (@denstl)

    5 years, 9 months ago

    Issue identified and a fix has been tested. Will be included in a release that hopefully will be out soon.

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Visual Composer compatibility issue?
    Thread Starter denstl

    (@denstl)

    5 years, 9 months ago

    FYI, the UM team has figured out what the issue is and tested a fix on my test site. They plan on incorporating the fix in a new release soon.

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Visual Composer compatibility?
    Thread Starter denstl

    (@denstl)

    5 years, 9 months ago

    Same issue persists after updating all plug-ins. When UM plug-in active Chrome Dev Console shows the many errors below. When I deactivate UM, all errors go away. Be glad to provide credentials to sign on to this test WordPress instance if that would help. Good news is that after update I had no new errors or issues.

    wp.bundle.js?ver=30.0:2 failed to parse json RangeError: Maximum call stack size exceeded
    at String.toString (<anonymous>)
    at String.split (legacy.js?ver=2.1.9:83)
    at String.split (legacy.js?ver=2.1.9:84)
    at String.split (legacy.js?ver=2.1.9:84)
    at String.split (legacy.js?ver=2.1.9:84)
    at String.split (legacy.js?ver=2.1.9:84)
    at String.split (legacy.js?ver=2.1.9:84)
    at String.split (legacy.js?ver=2.1.9:84)
    at String.split (legacy.js?ver=2.1.9:84)
    at String.split (legacy.js?ver=2.1.9:84)
    (anonymous) @ wp.bundle.js?ver=30.0:2
    Promise.then (async)
    value @ wp.bundle.js?ver=30.0:2
    p @ vendor.bundle.js?ver=30.0:2
    v @ vendor.bundle.js?ver=30.0:2
    m @ vendor.bundle.js?ver=30.0:2
    setTimeout (async)
    jo @ vendor.bundle.js?ver=30.0:2
    C @ vendor.bundle.js?ver=30.0:2
    g @ vendor.bundle.js?ver=30.0:2
    value @ wp.bundle.js?ver=30.0:2
    oi @ vendor.bundle.js?ver=30.0:2
    fa @ vendor.bundle.js?ver=30.0:2
    t.unstable_runWithPriority @ vendor.bundle.js?ver=30.0:2
    KB @ vendor.bundle.js?ver=30.0:2
    da @ vendor.bundle.js?ver=30.0:2
    $i @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    t.unstable_runWithPriority @ vendor.bundle.js?ver=30.0:2
    KB @ vendor.bundle.js?ver=30.0:2
    zB @ vendor.bundle.js?ver=30.0:2
    UB @ vendor.bundle.js?ver=30.0:2
    Wi @ vendor.bundle.js?ver=30.0:2
    enqueueSetState @ vendor.bundle.js?ver=30.0:2
    j.setState @ vendor.bundle.js?ver=30.0:2
    value @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    d.trigger @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    Promise.then (async)
    value @ wp.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    d.trigger @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    setTimeout (async)
    jo @ vendor.bundle.js?ver=30.0:2
    qn @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    value @ wp.bundle.js?ver=30.0:2
    oi @ vendor.bundle.js?ver=30.0:2
    fa @ vendor.bundle.js?ver=30.0:2
    t.unstable_runWithPriority @ vendor.bundle.js?ver=30.0:2
    KB @ vendor.bundle.js?ver=30.0:2
    da @ vendor.bundle.js?ver=30.0:2
    $i @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    t.unstable_runWithPriority @ vendor.bundle.js?ver=30.0:2
    KB @ vendor.bundle.js?ver=30.0:2
    zB @ vendor.bundle.js?ver=30.0:2
    UB @ vendor.bundle.js?ver=30.0:2
    Wi @ vendor.bundle.js?ver=30.0:2
    enqueueSetState @ vendor.bundle.js?ver=30.0:2
    j.setState @ vendor.bundle.js?ver=30.0:2
    value @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    d.trigger @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    Promise.then (async)
    value @ wp.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    d.trigger @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    setTimeout (async)
    jo @ vendor.bundle.js?ver=30.0:2
    qn @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    value @ wp.bundle.js?ver=30.0:2
    oi @ vendor.bundle.js?ver=30.0:2
    fa @ vendor.bundle.js?ver=30.0:2
    t.unstable_runWithPriority @ vendor.bundle.js?ver=30.0:2
    KB @ vendor.bundle.js?ver=30.0:2
    da @ vendor.bundle.js?ver=30.0:2
    $i @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    t.unstable_runWithPriority @ vendor.bundle.js?ver=30.0:2
    KB @ vendor.bundle.js?ver=30.0:2
    zB @ vendor.bundle.js?ver=30.0:2
    UB @ vendor.bundle.js?ver=30.0:2
    Wi @ vendor.bundle.js?ver=30.0:2
    enqueueSetState @ vendor.bundle.js?ver=30.0:2
    j.setState @ vendor.bundle.js?ver=30.0:2
    value @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    d.trigger @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    Promise.then (async)
    value @ wp.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    d.trigger @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    setTimeout (async)
    jo @ vendor.bundle.js?ver=30.0:2
    qn @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    value @ wp.bundle.js?ver=30.0:2
    oi @ vendor.bundle.js?ver=30.0:2
    fa @ vendor.bundle.js?ver=30.0:2
    t.unstable_runWithPriority @ vendor.bundle.js?ver=30.0:2
    KB @ vendor.bundle.js?ver=30.0:2
    da @ vendor.bundle.js?ver=30.0:2
    $i @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    t.unstable_runWithPriority @ vendor.bundle.js?ver=30.0:2
    KB @ vendor.bundle.js?ver=30.0:2
    zB @ vendor.bundle.js?ver=30.0:2
    UB @ vendor.bundle.js?ver=30.0:2
    Wi @ vendor.bundle.js?ver=30.0:2
    enqueueSetState @ vendor.bundle.js?ver=30.0:2
    j.setState @ vendor.bundle.js?ver=30.0:2
    value @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    set @ vendor.bundle.js?ver=30.0:2
    s.set @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    d.trigger @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    set @ vendor.bundle.js?ver=30.0:2
    s.set @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    Promise.then (async)
    (anonymous) @ wp.bundle.js?ver=30.0:2
    Promise.then (async)
    value @ wp.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    d.trigger @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    i.emit @ vendor.bundle.js?ver=30.0:2
    publish @ vendor.bundle.js?ver=30.0:2
    (anonymous) @ vendor.bundle.js?ver=30.0:2
    rt @ vendor.bundle.js?ver=30.0:2
    B @ vendor.bundle.js?ver=30.0:2
    d.start @ vendor.bundle.js?ver=30.0:2
    s @ wp.bundle.js?ver=30.0:2
    r @ wp.bundle.js?ver=30.0:2
    e @ wp.bundle.js?ver=30.0:2
    (anonymous) @ wp.bundle.js?ver=30.0:2
    setTimeout (async)
    c @ wp.bundle.js?ver=30.0:2
    window.onload @ wp.bundle.js?ver=30.0:2
    load (async)
    (anonymous) @ wp.bundle.js?ver=30.0:2
    ./public/editor.js @ wp.bundle.js?ver=30.0:2
    l @ runtime.bundle.js?ver=30.0:1
    s @ runtime.bundle.js?ver=30.0:1
    o @ runtime.bundle.js?ver=30.0:1
    (anonymous) @ runtime.bundle.js?ver=30.0:1
    (anonymous) @ runtime.bundle.js?ver=30.0:1
    Show 44 more frames
    wp.bundle.js?ver=30.0:2 failed to parse json RangeError: Maximum call stack size exceeded
    at String.toSt

    Forum: Reviews
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] No help at all.
    denstl

    (@denstl)

    5 years, 9 months ago

    I’d be glad to. Here is the first one: https://ww.wp.xz.cn/support/topic/visual-composer-compatibility-8/. Champ Camba had marked it as resolved, but it was not. I opened a new topic at: https://ww.wp.xz.cn/support/topic/visual-composer-compatibility-issue-2/. In this one I provided the requested video of the issue. I can also proivde access to the test WordPress site where the Visual Composer folks debugged the issue and were nice enough to provide a license to aid in investigation. Appreciate any help and can provide any additional details desired.

    Forum: Reviews
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] No help at all.
    denstl

    (@denstl)

    5 years, 9 months ago

    jfloid – I feel your pain. Submitted an issue 5 weeks ago. Champ Camba replied asking for more info. Provided and never heard a word back. Love the plug-in but support, not so much.

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] RangeError: Maximum call stack size exceeded
    denstl

    (@denstl)

    5 years, 9 months ago

    Same problem here with Visual Composer. The Visual Composer support team actually helped and identified the issue as an Ultimate Member issue. Reported weeks ago here but have received no feedback. Too bad as UM is a great plug-in other than this issue and lack of support to address it.

    • This reply was modified 5 years, 9 months ago by denstl.
    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Oxygen Builder and UM
    denstl

    (@denstl)

    5 years, 9 months ago

    I did the same and the Visual Composer guys were nice enough to lend me a license so UM support could check it out themselves to see the issue. I’m paying for that extra site with the hope they can take me up on the offer…

    Forum: Plugins
    In reply to: [Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin] Oxygen Builder and UM
    denstl

    (@denstl)

    5 years, 9 months ago

    I get a similar error when using Visual Composer plug-in. The Visual Composer support group quickly isolated the issue as an Ultimate Member issue. I provided details on the error I see in the Chrome Dev Console as well as a video showing the issue with UM plug-in enabled and then disabled (see link below to my posting). Only get errors when UM plug-in is active. Still waiting for a response on my issue. Sorry I cannot help with your issue but hopefully if they resolve one, they resolve the other.

    Very long list of issues in the Dev Console. Here are but 2 issues I only see when UM plug-in is active (no errors if I inactivate the UM plug-in).

    load-scripts.php?c=0&load[chunk_0]=underscore,utils,jquery-core,jquery-migrate,moxiejs,plupload,wp-codemirror&ver=5.4.2:12 JQMIGRATE: Migrate is installed, version 1.4.1
    jquery-migrate.min.js,qver=1.4.1.pagespeed.jm.C2obERNcWh.js:1 JQMIGRATE: Migrate is installed, version 1.4.1
    wp.bundle.js?ver=29.0:2 failed to parse json RangeError: Maximum call stack size exceeded

    wp.bundle.js?ver=29.0:2 failed to parse json RangeError: Maximum call stack size exceeded

    Link to my post.

Viewing 15 replies - 1 through 15 (of 26 total)
1 2