Marcus (aka @msykes)

Hello, I’m sorry you had such a bad experience with the update. Obiously not our intention.

We have written about this in our blog posts, unfortunately there was such a big change between our templates which were 10+ years old with practically no styling and our new UI that required large changes. This particularly affected those with highly customized templates, which sounds like maybe that’s the case for you, although we did our best to mitigate these with minimal structural changes, more CSS rules.

Please refer to this blog post which explains it more along with workarounds, because you can still keep your previous templates and styling by either keeping your old formats or templates and disabling some of our styling;
https://wp-events-plugin.com/blog/2022/08/11/about-those-new-updates/

It’s a shame that also so many users that claim to have used our plugin for so many years also only feel the need to come and leave reviews when something goes wrong. Whilst the update did go wrong for many people it also went right for many more that updated and just moved on with things.

From a security standpoint, there’s nothing wrong with having the wp-login.php there, but you have a few options here.

One is override our login form and change the links as needed. That’s located in templates/forms/bookingform/login.php and see our docs on overriding.

Another option is add filters to make sure your login URLs are switching properly.

We use home_url('wp-login.php', 'login_post'); and site_url('wp-login.php?action=lostpassword', 'login') variations to get that URL, something I’d argue a plugin that moves login pages should do.

Not sure if this will help because it doesn’t have an actual move logins page (yet) but our plugin Login With AJAX offers a lot of login options!

Hello, that’s most definitely a caching issue. Something on your site, your hosting package or firewall service is caching that first page and serving an older version.

For example, a random querystring is enough to serve a non-cached version of page 1:
https://www.ouchtraining.co.uk/events/?random-querystring=1

Hello,

Translations are managed by WordPress – https://translate.www.ads-software.com/projects/wp-plugins/events-manager/

We don’t supply a pot file anymore, but you can get it from that translation site above. For example from here, the ‘export’ part at the bottom:
https://translate.www.ads-software.com/projects/wp-plugins/events-manager/stable/sr/default/

Hello,

I highly doubt this is 6.1.3 specific, because we haven’t changed that offending line, nor the missing class which is supposedly included further up What version did you upgrade from?

Also, are you able to access your site? If you’re seeing one error in your logs, then it’s likely to have been a temporary issue.

Hello, I’m sorry you had such a bad experience with the update. Obiously not our intention.

We have written about this in our blog posts, unfortunately there was such a big change between our templates which were 10+ years old with practically no styling and our new UI that required large changes. This particularly affected those with highly customized templates, which sounds like maybe that’s the case for you, although we did our best to mitigate these with minimal structural changes, more CSS rules.

Please refer to this blog post which explains it more along with workarounds;
https://wp-events-plugin.com/blog/2022/08/11/about-those-new-updates/

It’s a shame that also so many users that claim to have used our plugin for so many years also only feel the need to come and leave reviews when something goes wrong. Whilst the update did go wrong for many people it also went right for many more that updated and just moved on with things.

Hi @raoulg, thanks for the supportive review, much appreciated!

Yes, I understand that it was a big update but like you say I hope it’ll be a very good long-term investment for anyone tweaking for v6, and that the major changes that can cause potential breakages will now hopefully be behind us!

Hi Steven, thanks for the supportive review and comments, much appreciated!

Regarding the !important usage, there’s a good logic behind this, because we simply can’t style certain things strongly enough without it, because many themes use id selector rules to override styling that in turn breaks ours, for example:

#theme p { margin:10px; }

would override anything we try like

.some .unique.selector .rule p { margin:5px; }

The usage of !important is not ideal if you have full control of your site, but we don’t have that luxury since we don’t know what you’ll install on yours, therefore our best option for maximum consistency was !important. At the end of the day, you can always override those rules by being a little more specific in your selectors and using !important as well. We also are making more and more use of CSS vars which you can also modify.

Hello, I’m sorry you’re experiencing issues. The PHP error we fixed days ago and we’re still trying to help you on our pro forums, but your issue is related to your host blocking outgoing connections, as I personally looked into your issue earlier today (before even reading this review).

We do care, and we are responding to your replies in a timely manner and will continue to do so.

Hello, my apologies, this is a PHP 8.1 specific error we caused whilst trying to fix some 8.1.-specific warnings in the last update, could you please try updating to 6.1.2.1?

If anyone still has issues with styles etc., I’d appreciate you opening a new thread. We can’t help you here with individual style problems as the thread has too much noise.

@thisbit

First reason:

#somethemeid .wp-content div { margin-bottom: 10px; }

is not good coding practice but its more legitimate then

#someplugin .somelement div { margin-bottom: 10px !important; }

Yes, you’re right but you’re forgetting something…. if you post the same content twice, e.g. two event lists, you can’t use the same ID. So, therefore we can’t write a CSS rule for dynamic IDs e.g. with a random number at the end to ensure valid HTML. Themes have that luxury to add a wrapper ID, we don’t due to flexibility.

That’s the reason. We’ve deliberated this a lot and !important really was the only option. At the end of the day, !important can still always be overridden, it’s just a way of being more specific.

Coding practices are not really targeted for developers making plugins, because we have to account for scenarios on website HTML structures for which we have no control over.

@thisbit (again) not sure what you mean about the overriding, please post a new thread and we can address it separately.

@crossroast I’m aware you have a few issues with a couple of layout/structure issues, I’ll get to your tickets ASAP, we’re going through them ASAP. Note though that in every situation you have full control to override anything we’ve made, so we’re as flexible as ever, we’ve just added styling which can be disabled. We overlooked disabling pixelbones in the 6.0 update, and fixed that within a couple of days, forcing it on ppl was never the intention.

Hello, as of 6.0 we’re enabling ajax by default, you can disable it now the same way as before to enable it, like so by adding the following line in your wp-config.php file below the <?php :

define('EM_AJAX',false);

Hi everyone, just released 6.1.1 which includes the fix. This update is pretty much an exclusive fix the mariaDB related error.

Hi everyone, just released 6.1.1 which includes the fix. This update is pretty much an exclusive fix the mariaDB related error.