Mustafa Uysal

Hi @pvengel,

I just released version 2.0.2 which should fix this issue, please give it a try and let me know if the problem persists.

Hi @pvengel,

Thanks for reporting the problem. Yandex used to provide auth code in numbers before, and it looks like it changed recently and started using letters. I will update the plugin ASAP to address this problem.

Hi @lufuchs,

The functionality you’re referring to requires the manage_options capability, so it cannot be provided to other users.

Typically, when a new post is published, the post archive page should be automatically purged. However, if your blog-page relies on a shortcode rather than a standard post archive, you can manually add its URL using the powered_cache_post_related_urls filter.

For example:

add_filter( 'powered_cache_post_related_urls', function ( $related_urls ) {
    $related_urls[] = home_url('blog-archive');

    return $related_urls;
} );

Alternatively, you can specify the blog archive URL under the “Purge Additional Pages” option in the Advanced Options.

Please give it a try and let me know if the issue persists.

Hi @deargeek,

Is there a way (or could there be) to disable loading login-block-style.css when the block isn’t being used?

It’s already working that way! (I just tested with the default theme, and login-block-style.css is not loaded when the Magic Login block isn’t present on the page.)

However, if you are using a classic theme WP enqueues block style globally (AFAIK). You can try something like this:

function magic_login_maybe_dequeue_block_style() {
	if ( is_admin() ) {
		return;
	}

	// Get the current post content
	global $post;

	// If the post content doesn't contain the block, dequeue the CSS.
	if ( $post && ! has_block( 'magic-login/login-block', $post ) ) {
		wp_dequeue_style( 'magic-login-login-block' );
	}
}
add_action( 'wp_enqueue_scripts', 'magic_login_maybe_dequeue_block_style', 20 );

I hope this helps!

Hi @xroox,

That feature is available in the PRO version of Magic Login. You can learn more about it here: https://handyplugins.co/docs/magic-login-registration/

Feel free to contact us through our website if you have any specific questions about the PRO features.

Cheers,

Hi @bermilma,

API feature is not part of the free plugin, it comes with Magic Login PRO. Please contact us here – https://handyplugins.co/contact/ – if you have a support request regarding the PRO version of the plugin.

You’re welcome, I just opened an issue in regards this feature btw – https://github.com/poweredcache/powered-cache/issues/150

While I don’t have an ETA yet, but it can be a good feature.

Hi @yworld,

We don’t have a filter for that because the plugin’s API (actions/filters) is utilized at a later stage in WordPress’s execution process.

As a workaround, you may want to set a specific cookie based on $_SERVER['HTTP_REFERER'] and configure Powered Cache to skip serving cached pages for that cookie.

I hope this helps.

Marking this thread as resolved. Please don’t hesitate to reach out if the issue persists.

Hi @jesus-1,

That’s unusual, as the “Log In” text is already wrapped in the localization function with the correct text domain. Custom translations should work seamlessly.

Could you try using the gettext filter to override the string translation? Here’s a guide that explains how to customize default messages: https://handyplugins.co/docs/magic-login-customize-default-messages/

Let me know if that helps!

@nadworks update the latest version of the plugin (added a new filter in this version)

and you can use something like this: (update the xyz with the actual slug that you are using for login url)

add_filter( 'magic_login_get_wp_login_url', function ( $login_url ) {
    $login_url = site_url( '/wp-login.php?xyz&redirect=false&action=magic_login' );
    return $login_url;
} );

I hope this helps!

Hi @nadworks,

I’m marking this thread as resolved. If the issue persists, don’t hesitate to let me know.

Hi @nadworks,

Which plugin do you use to customize login URLs? For example if your need login url is custom-login.php, you can customize something like this:

add_filter('site_url', function ($url, $path, $scheme) {
    // Check if the path starts with wp-login.php
    if (strpos($path, 'wp-login.php') === 0) {
        // Replace wp-login.php with custom-login.php in the URL
        $url = str_replace('wp-login.php', 'custom-login.php', $url);
    }
    return $url;
}, 10, 3);

Could you give it a try to this snippet and let me know if it works for you?

Thanks for the details!

It looks like {{MAGIC_LOGIN}} is being escaped when processed by WooCommerce. Reverting the string using this snippet should resolve the issue: https://gist.github.com/mustafauysal/cb59963f9afa5b7592b829e4b44aca45

Hi @builtbygo,

{{MAGIC_LINK}} works very similar to the auto login link, what do you see when using it? (eg: just empty string or placeholder text?) Could you check the limitations here?

Regards,