Support » Plugin: WP-Members Membership Plugin » Chrome plus this plugin disabled site…

  • In Firefox, all is well.
    In Chrome, however, (both on laptop and phone browser), all menu links led to just one page, and a second-level page, at that.

    It also blew apart the formatting of the Contact 7 Form on that page.

    I disabled all plugins, changed themes, and this plugin was the culprit.

    Cheers!

    —-8/23/19 Follow-Up—-
    Point taken, Chad…!

    As said initially, despite changing themes for troubleshooting, and by this I mean using the plain vanilla WP “Twenty Sixteen” theme, your plugin was not playing well with my site when viewed with Chrome.

    As I found another plugin to suit me for those needs, and as I did not have the time or interest to experiment to see if one of my 16 other activated plugins was the cause of making your plugin not work in Chrome, I wrote the above review from a sense of frustration.

    I did not intend to nuke your stats! So, adjustment made, and hopefully I am the only one that this issue ever happens to.

    Cheers,
    Ralph

    • This topic was modified 2 months, 3 weeks ago by ralphw.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Chad Butler

    (@cbutlerjr)

    Considering that I use Chrome everyday as my primary browser while further developing the plugin, I would respectfully disagree.

    Generally, it’s more helpful to start with a support issue – either here or at the plugin’s support site – and give the developer an opportunity to determine the actual problem before posting a negative review. Perhaps then we could have determined the true culprit.

    I would add that if the plugin truly did not work in Chrome, it would be unlikely to have 80,000 active installs since Chrome dominates current browser market share.

    • This reply was modified 3 months, 1 week ago by Chad Butler.
    Plugin Author Chad Butler

    (@cbutlerjr)

    Just an update to this for anyone reading later.

    I did further testing and confirmed that there are no Chrome issues. That’s not surprising since all of the primary development process is using Chrome to begin with, as I mentioned above. But I still wanted to confirm that was the case.

    So the problem was either a case of mistaken identity (a different plugin reviewed in the wrong forum – something that does happen from time-to-time), or it was more related to the theme and other plugins. Regardless of the reason, since the reviewer never worked it out as a support issue, we’ll never know.

    As is often the case with this type of review, the user should have started this as support and not a review. I mentioned that in the original response hoping the user would have at least reached out to provide additional information regarding their experience. I’m not surprised, however, that they didn’t. I’ve seen this for this plugin and many others where it’s more of a “hit-and-run.”

    Unfortunately, that kind of misuse of the review system makes reviews on wp.org less valuable overall. Usually these kinds of “reviews” are made by someone who doesn’t generally use the forums or reviews, making them a troll of sorts. That doesn’t seem to be the case here as this user has other reviews and forum posts over the years. That actually makes it more disappointing because they should know better.

    Sorry if this sounds like too much of a rant as it’s not intended to be. It’s intended to be more explanatory and hopefully lead to a better wp.org community over time.

    Plugin Author Chad Butler

    (@cbutlerjr)

    As I found another plugin to suit me for those needs, and as I did not have the time or interest to experiment to see if one of my 16 other activated plugins was the cause of making your plugin not work in Chrome, I wrote the above review from a sense of frustration.

    Totally understandable. As I said, it seems strange since all that is pretty much the standard development environment. But I’m glad that you were able to find something that suits you.

    I did not intend to nuke your stats!

    No problem – My primary concern was really to get to the core of the issue if possible. Looking at your profile, you’ve been around awhile and are someone who does make good use of the .org forums as an all-around positive member of the WP community, so I appreciate the response!

    hopefully I am the only one that this issue ever happens to.

    I hope that as well 😉 But if you do end up giving it another whirl and are able to reproduce the problem, let me know and I’ll look at it.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this review.