Deleyna

Just a follow on, we have had to switch to competitor’s plugin. This new process will not work for us. I’m sad to leave, and wish you well.

I just saw this on Google:
Get your event on Google
On March 17, 2020, we added several optional properties: eventStatus, eventAttendanceMode, and previousStartDate. Due to COVID-19, we encourage you to add these new properties so people can understand the status of your event and how they can attend. For more information about this change, check out our blog post.

So this is a new field that Google added on March 17. I can see why we need to fill it in.

Modern Tribe: I’m guessing you’re working hard to add this feature? Isn’t it great when Google drops something new onto us? Because dealing with a global pandemic wasn’t enough stress in our lives. Thanks for all you folks do!!!

AHA — I found it. And you were right — it absolutely WAS a plugin conflict with Oxygen.

There is a patch here: https://github.com/soflyy/oxygen-bugs-and-features/issues/516

Everything is working well again.

Server move completed. I did the check, didn’t immediately find any other conflicting plugins. I did see this error:
SyntaxError: invalid regular expression flag s — yoast-compatibility.js:8:94

Not sure if that helps any.

I will report to my client that he may need to purchase support if he wants this to work, or we may need to try something else.

Thanks for pointing me in the right direction.

Yes. Yoast 13.2, WordPress 5.3.2

I need to test more, but coincidentally our hosting company is currently migrating the site to a new server. I’ll test after the migration and update this ticket.

Thanks for the help. This may point me to the problem.

Ah! Thanks. That’s what I’d missed. So that explains the wrong user being enrolled.

So there is a way to NOT require user to click a link, right?

Great! That’s exciting to me. I will test this ASAP. I will be so happy if we can still use your plugin. It has been working well for us until this.

Thank you!

• This reply was modified 5 years ago by Deleyna.

First: that’s not what 2.1 did on our site. It auto enrolled the wrong students.

Second: if that is the way you are going, we can’t use it. Our students emails wind up in spam too often and even when they don’t, you can’t expect 100% to click any link. That’s not how users work…

Excellent! I look forward to trying it! I’m still seeing 2.1 as the latest version. When I see the update to 2.2, I’ll try it!

• This reply was modified 5 years ago by Deleyna.

Something weird I noticed when changing to Monster Insights. These two plugins are visually virtually identical except for some color changes. Even the upgrade pages appear to be the same with just a CSS change.

The 6.0.1 update to Exact Metrics put the 30 day graph back on the dashboard…it is better, but unfortunately went into a loop on the two sites I decided to test it on to see if we could live with it.

I’m wondering if this plugin changed hands and got bought out by the other plugin…

FYI – our site is busy enough that I was able to trace this back to the 2.0 update on WooMoodle. Anyone enrolled before that was fine, anyone after it was wrong.

I restored back to an older version and it is working again. We don’t get the emails…but the correct students get into class.

What caused me to miss this for so long is that our classes start on the first of the month — or in this month’s case…today. Each enrollment WAS enrolling a student into a class. I did have 1 that got into the wrong class…which confuses me completely. But the others were all in the right class, just the wrong students.

Hope this helps on your end.

Thanks, but ignoring updates won’t solve the underlying issue. I appreciate the spirit of the advice, though. I’m not panicking about updates, but I do find that keeping things updated increases security.

Yes, SiteGround has the additional caching — one of the great things about working with them. I mentioned their cache because I wanted to point out that I was already clearing cache on the server…but I take your point. There may be other caches…in which case working with SG would probably not solve the problem since their cache is already cleared. I did disable their caching plugin and test, and the problem did not resolve.

I’m going to investigate the other caches you mention.

So am I the only one having this problem? Or just the only one who noticed?

That’s good info, although understanding how annoying these messages are would be better.

Have you ever had one pop up during updates? Did you know clicking on them during updates can be a disaster? Ever had one interfere with another message? Ever had a user miss a critical message because they are so used to dismissing these? I know plugin authors need to make a living, but these are becoming a problem.

I’m sorry to rant. I’m just really tired of these messages. At least you have the constant maybe we can figure out how to lower the frequency.

I work hard to teach my clients to update their sites. They were just forced to do two updates — one to ADD the banner and one to REMOVE the banner. Thanks yoast for making my clients much less likely to take their updates seriously.

And yes, using a different plugin is becoming a necessity. So frustrating!

@pmastromarchi can you log into the file manager on your server? If so, go to wp-content/plugins/ocean-extra and rename it. You’ll be able to get in and install the updated version of the plugin. The current version does not have the error.

And it looks like the latest update fixes it. Thanks folks!!!