Marcus

As edited, we quickly fixed that a few hours after 6.4 with the 6.4.1 update ??

Thanks for confirming!

Hello, 6.4.1 just released, will fix the issue even with cached JS files.

Hello, we’ve reproduced it, a fix will be out shortly.

Hello, do you have a url where we can see this?

Hi! This is already possible, in widget blocks you can enable the reset password form or remember=”2″ in a shortcode.

https://docs.loginwithajax.com/login-form/

Actually, this is the right place to ask. Please try the latest version of the Zoom plugin, 1.6 which should fix various connection issues.

Hello, could you confirm if the review popup continues to stay?

If so, apologie, that’s not the intention to nag repeatedly!

In theory it should go away if you dismiss it, but we’ve found that unfortunately in some occasions the popup doesn’t get dismissed due to plugin conflicts.

One temporary solution is to use the WP Safe Mode so only EM is running,turn off the notification and then resume as usual.

That’s an interesting point, and something we’d need to look into at a later date (task added to our internal tracker), due to current things we’re working on. The quick solution for you would be to override templates and add rel=”nofollow” attributes to the links in our templates:

events-mangaer/templates/calendar/section-header-navigation.php
events-mangaer/templates/calendar/section-dates.php

As for the pagination urls (middle link) that’s a little trickier, if you want to completly prevent pagination from being indexed, this would do the trick:

function my_em_add_pagination_nofollow( $pagination ){
	return str_replace('<a ', '<a rel="nofollow"', $pagination);
}
add_filter('em_paginate', 'my_em_add_pagination_nofollow', 10, 1);

Note that this would prevent google indexing some legit pagination pages too though, you could expand on this snippet more to exclude certain pages e.g. the events page.

Hello, sorry for the delay on this. We were in the middle of big feature updates and this got lost in the mix. We’ve just updated to 1.6 which fixes connection issues and other things, please update and try again.

Hello, I’m sorry for the delayed reply (see the first post on this support forum , we monitor the EM forum).

We’ve just updated to 1.6 which fixes connection issues and the last_name bug, please update and try again.

And no, we don’t want to force you to use the Pro version, although if you can, FYI the proceeds do go to developing and maintaining free features like this ??

Hello, we’ve just updated to 1.6 which fixes connection issues, please update and try again.

Hello, we’ve just updated to 1.6 which fixes connection issues, please update and try again.

@janmiddelkoop reported this to me, here’s my reply:

I think the issue here is less the class adding and more the fact that the resizeobserver is going back/forth between large/small. We use a resizeobserver rather than CSS media queries because we cannot guess your calendar size based on screen size, given you can use it on sidebars or your main site page width could be anything despite screen-size. This responds, in theory, to a page load and then any screen or page content resizing.

My guess is that something in your theme or maybe another plugin is triggering the resizeobeserver, and maybe by coincidence there’s a breakpoint in the size that’s causing that trigger between large/small.

As it’s in the sidebar, do you have any animation going on there, that may be affecting the size of the calendar?

As for the issue of it not disappearing, for now; try adding these lines of code to your site, such as your theme functions.php, load your page once, and then delete it.

get_site_option('dbem_data');
if( !empty($data['admin-modals']) ){
	unset($data['admin-modals']);
	is_multisite() ? update_site_option('dbem_data', $data);
}

In an ideal world, yes (in 10+ years we haven’t)… but… if we don’t ask people to review a plugin, they more often don’t unless there’s a problem! Small trade-off for a free plugin which we’re regularly updating and maintaining IMO.

What we will do though is make sure there’s a count-down so even if you can’t dismiss it due to plugin clashes etc, after x displays it’ll just stop.