Mustafa Uysal

Hi @stefacchio,

Could you share the URL? AJAX requests shouldn’t cached by default.

Ok for the moment I’ll disable the feature, do you know when will be an update for fix the issue?

I can’t give an ETA for now, but I will try to update the dependency once it is fixed.

What exactly does disabling this option change?

That option determines whether HtmlDomParser is being used for HTML minification or not.

Generally, if your server supports compression methods like gzip or Brotli, the impact of HTML minification on performance is minimal, you can completely turn of that feature.

• This reply was modified 6 months ago by Mustafa Uysal.

hi @stefacchio,

Thanks for your report! It looks like there’s a compatibility issue with a package we’re using for HTML minification (https://github.com/voku/HtmlMin/issues/93). As a temporary workaround, you can either downgrade your PHP version to 8.2 or disable the HTML minification feature for now.

Alright, I’ve read through some posts and now understand what DAP is. Unfortunately, Magic Login doesn’t support DAP and doesn’t intend to in the future.

If you are newly starting your membership site, I strongly recommend a proper membership plugin that actually works with WordPress.

Feel free to ping me via support[at]handyplugins.co if you want to hear more details about DAP from me. (Public WordPress forums are not the best place to share such ideas on commercial products)

It’s always possible to have conflicts with third-party plugins. Magic Login sets the authentication process ‘almost’ identical to the standard method used when logging into WordPress.

Is there any public documentation about DAP? (I’m not sure what that is or how does it work.)

Where is the option to ensure they’re being logged in by email address?

We don’t have an option for that, since the plugin is designed to accept both. But you can add frontend enforcement for the form that acceps to email address only with this snippet (assuming you are using shortcode to add magic login form?)

function enqueue_magic_login_email_only_script() {
	?>
    <script type="text/javascript">
		document.addEventListener("DOMContentLoaded", function() {
			// Find the form by ID
			var form = document.getElementById("magicloginform");

			if (form) {
				// Find the input field by name within the form
				var userLoginInput = form.querySelector("input[name='log']");

				if (userLoginInput) {
					// Force the input field to accept only email addresses
					userLoginInput.setAttribute("type", "email");
					userLoginInput.setAttribute("placeholder", "Enter your email address");
				}
			}
		});
    </script>
	<?php
}

add_action('wp_footer', 'enqueue_magic_login_email_only_script');

And you will probably want to update info message like this:

[magic_login_form info_message="Please enter your email address. You will receive an email message to log in."]

(you can learn more about supported shortcode parameters here: https://handyplugins.co/docs/magic-login-shortcode/)

I’m not sure exactly how DAP works, but it says in the docs as long as they are logged in by email address into WP, it will sync with DAP. DAP has a separate log in system.

This makes more sense now ?? However, I was expecting that they wouldn’t alter the login behavior, especially since they can already retrieve email addresses using the username as well.

• This reply was modified 6 months, 3 weeks ago by Mustafa Uysal. Reason: added example shortcode with info message
• This reply was modified 6 months, 3 weeks ago by Mustafa Uysal.

Hi @ogia,

Thank you for using Magic Login!

Yes, it’s possible to log users in by their email address instead of their WP username. Magic Login supports both email addresses and usernames for logging in.

and it syncs WP users by email address, so if they log into WP with username, they aren’t getting logged in as a member.

This seems a bit weird to me, as the WordPress authentication cookie shouldn’t be affected by whether users log in with their username or email address. The same cookie should be used for authentication regardless of the method.

Hi @leodefaveri,

Glad to hear it’s working so well for you. Thanks for the review! ??

@kryoz507,

Yeah, but it looks like the given resource is not cached. ‘BYPASS’ indicates that Cloudflare doesn’t cache that resource.

I recommend checking static resources such as this one: https://www.asesoriafinancieralee.com/wp-content/themes/astra/assets/css/minified/frontend.min.css?ver=4.7.3

For insance: https://share.cleanshot.com/RXGdVkXy , after you purge the cache you can see either CF-Cache-Status changes or Age. Added some new information to documentation if it helps – https://docs.poweredcache.com/cloudflare/

I see the age appear 950 if the value change to 0 its working. Right?

Yes, but it doesn’t always have to be 0; it depends on the cache’s age. Typically, you’ll see just a few seconds after purging is done.

Hi @kryoz507,

You can check CF-Cache-Status and Age headers after purging the cache E.g: https://share.cleanshot.com/hx6HhqGK

Hi @munikho,

I couldn’t reproduce the issue you’re experiencing. It appears to be related to your specific setup, so I’m marking it as resolved for now.

Hi @munikho,

Magic Login sets the auth cookie with the remember flag set to true (using wp_set_auth_cookie). It’s possible that other plugins are modifying the cookie TTL using the auth_cookie_expiration filter.

Hi @baltazarmilanov,

I’m not entirely sure how MemberPress handles the login process, but there shouldn’t be any issues with plugins that utilize the standard WordPress authentication functionality. It should work fine, so just give it a quick try and see if it works.

You can use shortcode or magic login block to add it any page you want.

Regards,

Hi @doubleedesign,

Thank you for your review! I’m glad to hear the plugin meets your needs.

It’s a good idea to allow commenting for certain post types, so I’ve opened an issue to consider this for future versions.

Thanks!

Hi @mastababa,

I’m assuming you are talking about auto login links feature, right? You can find out the details here – https://handyplugins.co/docs/magic-login-auto-login-links/

As an alternative approach you can just use {{MAGIC_LINK}} placeholder for any outgoint email which works similarly with auto login links – https://handyplugins.co/docs/how-to-add-magic-login-to-any-of-outgoing-emails/

I hope this helps.