• Resolved agenciesFirst

    (@agenciesfirst)


    Hi, I found a bug today, upcoming with last WordPress update 5.8.2.
    I will using this nice plugin for all our customers and I’m intend to extend to the pro version. The issue is, when magic link is active than is the WordPress Version number hiding on all sites in backend. Showing normally in the right corner above. It exists maybe an css conflict that you should to fix. Thanks for attention. And by the way! For my impressions, the plugin takes sometimes longer as expected to long to react for customers interacting, so also it cost sometime more time to get a login link. Mostly if nobody try it to logging in for longer time. After the first login goes all others login tyings fast and normal like WP login. Why is the behaviour so? Can you verify my observing?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter agenciesFirst

    (@agenciesfirst)

    Hey! It’s not ok and not professional to ignore me for more than 2 days!
    That indicates for me – don’t buy this pro version from this guy.

    No way!

    Your plugin does make a issue in WordPress Version 5.8.2 and that is new. Fix it immediately and answering the forum quetsions quickly.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    I’m a forum moderator and I have nothing to do with this plugin, the developer or any plugin or theme on this site.

    Now that that’s out of the way:

    Hey! It’s not ok and not professional to ignore me for more than 2 days!
    That indicates for me – don’t buy this pro version from this guy.

    Yes, it is 100% OK. You left a post here on Friday, it’s Sunday. The developers are volunteers and they do not owe you a reply or anyone any reply at all.

    If that’s a problem for you then uninstall the plugin and walk away.

    You are not a customer on this site and never have been. You are not entitled to an answer, a “hello”, any reply or even the time of day. At best you are an opensource collaborator and your reply to your own topic shows that you are not that either.

    I have flagged your account for moderation. That means any posts, reviews or replies from your account will need to be approved before anyone else can see them. That also means none of your replies or posts will generate any email.

    I suggest you set your expectations appropriately when you post on this 100% staffed by volunteers community support site.

    Thread Starter agenciesFirst

    (@agenciesfirst)

    @jdembowski
    I am not a customer of this site? Where do you want to get that from?
    For example, I pay at least 10 licenses for Woocommerce extensions to Automattic every year and I occasionally answer questions here in the forum to help users quickly for plugins that I have nothing to do with. Just by the way. So your intermediate straddle is completely superfluous and unnecessary. I respect the forum rules here. But thanks for your hint. If a developer ultimately wants to sell a Pro version, then he should be able to respond quickly to questions in order to signal that he is interested. And that is reasonable because you will be informed immediately by email. I’m not asking too much, it’s just a good style.

    Moderator Yui

    (@fierevere)

    永子

    I am not a customer of this site?

    No, you are not, there are no www.ads-software.com customers at all.
    There are “users”, “contributors”, but no “customers”.

    I pay at least 10 licenses for Woocommerce extensions to Automattic

    This makes your customer of Automattic, but not WordPress and www.ads-software.com

    Automattic is not WordPress and WordPress is not Automattic.
    They are major contributing company ofc.

    I occasionally answer questions here in the forum to help users quickly for plugins

    This makes you somewhat a forum and support team contributor.

    If a developer ultimately wants to sell a Pro version, then he should be able to respond quickly to questions

    All PRO related questions, including pre-sales must be handled by developer elsewhere.
    For pro or commercial product support please contact the developer directly on their site.
    This includes any pre-sales topics as well.
    As the developer is aware, commercial products are not supported in these forums.
    I am sure they will have no problem supporting you there.

    PS: Its no fun to discuss such things in this topic, i think you shall wait for plugin support/dev to answer. If you need to contact forum moderators, we have a #forums channel on Slack

    • This reply was modified 3 years ago by Yui.
    Thread Starter agenciesFirst

    (@agenciesfirst)

    Issue when MagicLink is active than is the WordPress Version number hiding on all sites in backend. Showing normally in the right corner below.
    Below not above!
    Sorry for misunderstanding

    Plugin Author Mustafa Uysal

    (@m_uysl)

    Hi @agenciesfirst,

    Thank you for your patience. Regarding the issues here;

    1) You are right, the plugin causes CSS conflict that hides the WordPress footer, which includes the version number. It is about the UI library that we are using. This problem will be addressed in the next version. (WordPress version numbers will be hidden on the magic login settings page only)

    For my impressions, the plugin takes sometimes longer as expected to long to react for customers interacting, so also it cost sometime more time to get a login link. Mostly if nobody try it to logging in for longer time. After the first login goes all others login tyings fast and normal like WP login. Why is the behaviour so? Can you verify my observing?

    It might be related to your setup. The email functionality relies on the WordPress email function, and it might take some time if you are using 3rd party SMTP services.

    During the login process, Magic Login checks the expired tokens and removes them if any. (This process works quite fast) You can get more details by using something like query monitor to observe the reason for slow request.

    Your plugin does make a issue in WordPress Version 5.8.2 and that is new. Fix it immediately and answering the forum quetsions quickly.

    This attitude won’t help to get a response faster. Almost every plugin makes changes through WordPress hooks, some of them intentionally some of them non intentionally and we called them “bug” which is the nature of the software.

    Thanks for reporting the issue.

    @jdembowski @fierevere Thanks for the clarifications here.

    Regards,

    Plugin Author Mustafa Uysal

    (@m_uysl)

    @agenciesfirst The CSS conflict has been addressed in 1.2.1. Marking as resolved. Feel free to re-open the thread if the update doesn’t work for you.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘CSS conflict in backed, WP version hiding in all backend pages’ is closed to new replies.