Mustafa Uysal

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.

kodu su sekilde duzenleyebilirsiniz:

add_filter( 'powered_cache_page_cache_enable', function ( $status ) {
	if ( is_single() && 'post' == get_post_type() ) {
		return false;
	}

	return $status;
} );

Merhaba @bakimeral,

Sadece belirli sayfalar icin kapatmak istiyorsaniz https://docs.poweredcache.com/disable-page-caching-for-specific-posts/ buradaki anlatildigi sekilde sayfalarin onbellege alinmasini engelleyebilirsiniz.

WP_CACHE page cache’in calisip calismayacagini kontrol eder, onu false yaparak kullanabilirsiniz eger tum site icin page cache’i kapatmak istiyorsaniz.

Veya alternatif olarak

define( 'DONOTCACHEPAGE', true); ekleyebilirsiniz wp-config dosyaniza. Veya

add_filter( 'powered_cache_page_cache_enable', '__return_false' ); (snippet olarak) seklinde de kapatabilirsiniz.

okunma say?lar? ve baz? kodlar?n ?al??mas?na engel oluyor.

Okunma sayisi gibi bilgileri WP tarafinda tutmamak saglikli bir durum degil aslinda performans acisindan. (her ziyaret icin update sorgusu calismasi veritabanina ek yuk getirecektir)

Hi @momo-fr,

Glad to hear that! Thanks for your review and for using Powered Cache!

You’re welcome. Glad to hear it worked ??

@makerhacks marking this as resolved, feel free to update if the solution above doesn’t do the trick.

I will check out the increase token validation link you shared.

Yes, please give it a try and let me know if it works. I’m happy to look into the issue further if it persists.

Hi @meganvwalker,

Thanks for using Magic Login.

It’s for a German company with the de at the end. Is there any reason why an email structured like that wouldn’t work?

Is she receiving login emails, or is there an issue with email deliverability? The plugin does not have specific rules for particular email addresses. However, some corporate email providers may have their own security measures. For example, Outlook (or some virus scanners for email client) can simulate email clicking behavior to verify the safety of a target URL. If this happens with a magic login email, it can invalidate the link, causing the token to expire before the actual user clicks on it.

I suggest you to increase token validation and see if it works – you can learn more here: https://handyplugins.co/docs/magic-login-token-validity/

I hope this helps.

• This reply was modified 10 months ago by Mustafa Uysal. Reason: blockquote instead >

Hi @makerhacks,

how will users know what that does?

Magic login form comes with related information. (https://share.cleanshot.com/rHWzjWTH – on wp-login.php page, and https://share.cleanshot.com/nzb2LQgZ when using the shortcode, please check your CSS if it hides these messages)

If you are using shortcode, you can use the button_text attribute. You can learn more about supported attributes here – https://handyplugins.co/docs/magic-login-shortcode/ and if you’re using the Magic Login block, you can customize almost everything within the block editor.

If these don’t work, you can customize any message with gettext filter: https://handyplugins.co/docs/magic-login-customize-default-messages/

I hope this helps, please give it a try and let me know.

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

Hi @jumbo,

Could you try the version 3.4.5?

> I did a fresh WordPress install, installed Powered Cache, then enabled “Minify HTML,” then saved settings. That was the only change. Afterward, no page content is minified.

When dom optimization is not enabled, the difference is relatively small. With the new update, the blank spaces will be removed regardless of the setting when HTML minification is enabled.

Also, omitted tags will not removed when the optimization with the dom parser is enabled, so you can see the cache fingerprint even if you enable that option.

I hope this helps.

marking as resolved since couldn’t hear from you @skeeterseatery

Hi @jumbo,

When optimizing the output with dom parser, it removes omitted tags – https://html.spec.whatwg.org/multipage/syntax.html#syntax-tag-omission

BTW, whichever minify method is used, could you please append the HTML powered by comment at the end so that it’s possible to tell if Powered Cache’s caching is active on that page. Maybe a more concise one-liner, like the following:

I might consider adding that for further versions or disabling the removal of omitted tags, however you can check the header of the request to understand whether it is cached or not cached.

Hi @rhettfinck,

We don’t have REST API support yet, it’s integrated to the wp_mail.

You may want to use pre_wp_mail hook to intercept email sending behavior and allow sending push messages. Or you can use \MagicLogin\Utils\create_login_link() for creating email login URLs to utilize for custom endpoints.

I hope this helps.

I’m glad to hear that all issues have been resolved. Once again thanks for the detailed report.

Cheers,

Hi @jumbo,

I’ve just released version 3.4.4, which addresses the issues you mentioned. Please update the plugin and test it out.

Let me know if the problem persists.