Forum Replies Created

Viewing 15 replies - 181 through 195 (of 409 total)
  • Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @judder : Thanks for the patch! I have it ready to go, but before I release it, what version(s) of BuddyPress have you used the plugin under? I just want to make note of the BP compatibility in the release notes.

    And with your patch, the plugin otherwise functions as anticipated for BP?

    Thanks!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @omegaphase : Hi Andy,

    Thanks for the suggestion. Check out v3.4 of the plugin, which now prevents email obfuscation from occurring in the admin area.

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @ebrois : Check out the newly released v3.0.2 of the plugin, which should fix the error you encountered. Let me know if you have any further problems with it.

    The bug only affected you because you were running an older version of WordPress. While the plugin claimed support for versions of WordPress back through 3.6 (and with this fix that should be correct), it is really recommended that you run the latest WordPress (for many reasons, including performance, security, and to minimize issues with plugin compatibility).

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    John,

    Thanks for checking into things and verifying that all looks fine with the plugin now.

    The form I was referring to was the front-end user registration form, e.g. /wp-login.php?action=register. I assume the Gravity Forms User Reg add-on is a front-end replacement of that.

    Is it possible you are intentionally getting two emails from the add-on (maybe 1 as the user, 1 as admin, or 1 to every admin (and you happen to have multiple admin accounts with same email))?

    Or maybe the add-on is emailing everyone with that email address. You said earlier if you registered with a unique email address (w/ AMA deactivated) you got one email, and this time (also w/ AMA deactivated) you got two. Could you be getting a registration email for each number of times that email address is being used?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Just beat my reply, John 🙂

    It’s seems very possible it’s an interaction between AMA and the Gravity Forms User Registration Addon you mentioned using. I assume it’s a commercial addon so I can’t see what it does.

    Something to test, if you can: Using the built-in WP user registration form, do 2 emails get sent? If so, if you deactivate the Gravity Forms addon and use WP’s user registration, do 2 emails get sent still?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @bhwebworks : Thanks for chiming in and providing helpful debugging info! You definitely pinpointed the problem area. Turns out I omitted some code at the start of count_multiple_accounts() to normalize the $user_id arg to an integer in situations where a user object is passed in.

    The fix was pushed out in v3.0.1 and should eliminate the warning you and michael were experiencing.

    I’m not sure yet what could be triggering two emails on registration. It’s possible it’s related to the issue I fixed (in conjunction with another plugin). Let me know if you still experience the double emails with this new version and I’lll investigate further.

    Thanks again!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @michael-walker : Thanks for the feedback! I’ve just released v3.0.1 which should eliminate the first error (the display of which likely being the cause for the second error). Let me know if you’re still experiencing any problems.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @dentopolis777 : Ah. Your description is different than I expected, but it does bring to light what I consider a bug with the plugin (and may be exactly what you are pointing out).

    So currently, as you have, if you tell the plugin to link “wirus HIV” with that checkbox unchecked, it would cause all case insensitive matches in your text to be replaced with the term you defined in the plugin.

    Examples:

    • “wirus HIV” becomes “wirus HIV” (good)
    • “Wirus HIV” becomes “wirus HIV” (bad)

    Thus, a sentence that is “xxx. Wirus HIV” becomes “xxx. wirus HIV”, which is undesirable.

    The plugin should preserve the original text and simply add the link to it, and it will do so in v1.8.

    If, however, your original text was “. wirus HIV”, then I don’t feel that the plugin should change the capitalization. It should honor what was originally there, which it doesn’t do yet.

    Does the change I proposed seem like it will fix your problem? Or did you really want for the plugin to change the capitalization of the original text?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @dentopolis777 : Just so I’m clear on your request, you’re saying you want to linkify a word such as “forums” and you have the “Case sensitive text matching” checkbox checked (so “forums” gets linked but “FORUMS” does not), you would still expect “Forums” at the start of a sentence to get linked.

    If so, that makes sense. I’ll consider the implications and implementation for the next release.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @michael-walker : Hmm, I’m not able to reproduce the error myself. When editing/updating a user profile, were you changing the email address, or does the error occur regardless of what fields you change?

    Are you able to test the plugin with all other plugins disabled? If not, could you list the plugins you have installed? It’s possible there’s an issue between the interaction of this plugin with another.

    And were you using the plugin before v3.0, or are you coming to it new? (Just want to check if things had worked for you before the v3.0 update if you were an existing user.)

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @madtownlems : Thanks, and nice use of the plugin!

    Behold v1.7 of the plugin, which incorporates your suggestion. Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @knutsp : Hi Knut, Allow Multiple Account was recently updated to v3.0 which is now compatible through WordPress 4.1. If you still use the plugin, or try it out again, let me know if you have any further issues with it. Thanks!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @mennobouma : I only did some preliminary testing with Multisite in the plugin’s v3.0 release. I plan to do more and include any fixes in the next release. Have you tested it separate from Woocommerce? That is, have you tested direct user registration and trying to re-use an existing email address? I just want to see if maybe Woocommerce is enforcing the uniqueness of emails itself (I haven’t looked at their code closely in this regard to know.)

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @kiwi3685 : See the note above for starflow, but the plugin should work better now (even though you hadn’t experienced any issues).

    I did take into your account your suggestion about the list of multiple accounts listing all accounts. Now it only lists email addresses that are associated with multiple accounts. Thanks for the suggestion!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @starflow : Not sure if you saw, but v3.0 of the plugin was recently released. If you are still interested and/or using the plugin, please check it out as it should be compatible through WordPress 4.1. Let me know how it goes!

Viewing 15 replies - 181 through 195 (of 409 total)