Membership Plugin

WordPress Membership Plugin

Ajax 200 Parsererror on Username entry in backend Add Member page

Simple Membership Plugin › Forums › Simple Membership Plugin › Ajax 200 Parsererror on Username entry in backend Add Member page

Tagged: , ,

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • August 8, 2015 at 11:47 am #2609
    swisspenelope
    Participant

    Hi

    As far as I know this does not cause any problems, but I have noticed the above behaviour recently on the site I am putting together. As I wanted to be sure it was not something to do with my tweaks in SWPM, I made a copy of my site on local, deactivated SWPM, then installed 3.03 as is without my tweaks, then went to the backend to add a new member … and the same thing happens.

    Either way, the member still gets added and there appears to be no issue arising from this, but I just wondered …

    Thanks if you can clarify,
    SP

    August 8, 2015 at 12:27 pm #2610
    mbrsolution
    Moderator

    Hi, do you have a plugin or theme that uses Ajax?

    August 8, 2015 at 12:48 pm #2611
    swisspenelope
    Participant

    apart from SWPM, you mean?

    At the bottom of the ADD view you have:`
    $.validationEngineLanguage.allRules[‘ajaxUserCall’][‘url’] = ‘<?php echo admin_url(‘admin-ajax.php’); ?>’;
    $.validationEngineLanguage.allRules[‘ajaxEmailCall’][‘url’] = ‘<?php echo admin_url(‘admin-ajax.php’); ?>’;
    $.validationEngineLanguage.allRules[‘ajaxEmailCall’][‘extraData’] = ‘&action=swpm_validate_email&member_id=<?php echo filter_input(INPUT_GET, ‘member_id’); ?>’;

    $(“#swpm-registration-form”).validationEngine(‘attach’);`

    i haven’t checked – were you going to suggest disabling it?

    August 8, 2015 at 10:33 pm #2616
    mbrsolution
    Moderator

    What I meant was to check to see if you have any other plugin that also uses Ajax or your theme. If you disable all your other plugins except this one do you still see that error?

    August 9, 2015 at 8:52 am #2618
    swisspenelope
    Participant

    Right! Very interesting. De-activating the other 6 plugins changed nothing, but choosing a different theme (I use a child theme of Attitude, a very good theme for tweaks), this behaviour goes away.

    Thanks for the learning experience. I will ignore the parsererror for now.

    August 10, 2015 at 3:41 pm #2628
    swisspenelope
    Participant

    Just for information:

    I diffed my Attitude theme files against the Attitude child theme files my site uses, because I suspected that a problem I was having with inserting media in WordPress also came from my child theme. I isolated the guilty file – it had code in it I had written to created new menus, and by first removing it all then putting it back almost line by line, I finally solved the Media Insert problem AND the Parsererror message has gone away! Still not sure what exactly was upsetting everything, as my custom menus are back in that file, and working, but the problems have not come back with them.

    Live and learn …

    Thanks for pointing me in the right direction.
    SP

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.