Marcus (aka @msykes)
Forum Replies Created
-
Thanks for pointing that out @richieboo that can be confusing 🙂
That error message should have gone away, but the id used to identify that error message changed with the dev update. We’ll update that before we release, but you can just click the X on the right and it’ll disappear and not reappear, same result.
We’ll update in a few hours.
Hello, we’re aware of this issue and have already updated it in a dev version yesterday which you can update to with just a few clicks as per my comments here:
https://wordpress.org/support/topic/random_bytes-does-not-exist/
It’s specific to MariaDB users, we’ll be releasing a ‘stable’ update later today, although this fix is confirmed by many users.
I hope you can resolve the issue and maybe re-evaluate the plugin review. Thanks!
Hi Guys, I thank you both for the feedback @josklever and @guidodr 🙂
Also, thanks for confirming.
We had quite a few posts with the same issue so once we reproduced the bug we just fixed it. .org forums don’t show the first post order.
Actually, I had initially thought RANDOM_BYTES may have caused issues in mySQL too so just made a complete workaround using MD5(RAND()), the important thing is that it’s unique which we’ve accounted for too.
hi, it is happening because you have an empty location permalink slug in your settings under Pages > Permalink Slugs. If you add something there it’ll go away. You do need a slug anyway for locations to work, if you have locations disabled it won’t have any effect even if you have a value there.
We’ll fix the error in the next update.
Forum: Plugins
In reply to: [Events Manager - Calendar, Bookings, Tickets, and more!] Enable Dark ModeJust checked your site, looks like you did it another smart way, just copying the css and changing the svg fill color 🙂
Forum: Plugins
In reply to: [Events Manager - Calendar, Bookings, Tickets, and more!] Enable Dark ModeHello, there might be an easy way to do this, we’re experimenting with the concept. You could add the below code to your Customizer > Additional CSS, then modify the first line to have the color you want:
.em .em-icon { background : red; } .em .em-icon.em-icon-logo-office365 { -webkit-mask-image: var(--icon-logo-office365); mask-image: var(--icon-logo-office365); } .em .em-icon.em-icon-logo-google-calendar { -webkit-mask-image: var(--icon-logo-google-calendar); mask-image: var(--icon-logo-google-calendar); } .em .em-icon.em-icon-logo-apple { -webkit-mask-image: var(--icon-logo-apple); mask-image: var(--icon-logo-apple); } .em .em-icon.em-icon-logo-outlook { -webkit-mask-image: var(--icon-logo-outlook); mask-image: var(--icon-logo-outlook); } .em .em-icon.em-icon-download { -webkit-mask-image: var(--icon-download); mask-image: var(--icon-download); } .em .em-icon.em-icon-spinner { -webkit-mask-image: var(--icon-spinner); mask-image: var(--icon-spinner); } .em .em-icon.em-icon-calendar { -webkit-mask-image: var(--icon-calendar); mask-image: var(--icon-calendar); } .em .em-icon.em-icon-calendar-empty { -webkit-mask-image: var(--icon-calendar-empty); mask-image: var(--icon-calendar-empty); } .em .em-icon.em-icon-list-grouped { -webkit-mask-image: var(--icon-list-grouped); mask-image: var(--icon-list-grouped); } .em .em-icon.em-icon-filter { -webkit-mask-image: var(--icon-filter); mask-image: var(--icon-filter); } .em .em-icon.em-icon-list { -webkit-mask-image: var(--icon-list); mask-image: var(--icon-list); } .em .em-icon.em-icon-map { -webkit-mask-image: var(--icon-map); mask-image: var(--icon-map); } .em .em-icon.em-icon-location { -webkit-mask-image: var(--icon-location); mask-image: var(--icon-location); } .em .em-icon.em-icon-settings { -webkit-mask-image: var(--icon-settings); mask-image: var(--icon-settings); } .em .em-icon.em-icon-clock { -webkit-mask-image: var(--icon-clock); mask-image: var(--icon-clock); } .em .em-icon.em-icon-folder { -webkit-mask-image: var(--icon-folder); mask-image: var(--icon-folder); } .em .em-icon.em-icon-category { -webkit-mask-image: var(--icon-folder); mask-image: var(--icon-folder); } .em .em-icon.em-icon-tag { -webkit-mask-image: var(--icon-tag); mask-image: var(--icon-tag); } .em .em-icon.em-icon-ticket { -webkit-mask-image: var(--icon-ticket); mask-image: var(--icon-ticket); } .em .em-icon.em-icon-at { -webkit-mask-image: var(--icon-at); mask-image: var(--icon-at); } .em .em-icon.em-icon-next-circle { -webkit-mask-image: var(--icon-next-circle); mask-image: var(--icon-next-circle); } .em .em-icon.em-icon-prev-circle { -webkit-mask-image: var(--icon-prev-circle); mask-image: var(--icon-prev-circle); } .em .em-icon.em-icon-first-circle { -webkit-mask-image: var(--icon-first-circle); mask-image: var(--icon-first-circle); } .em .em-icon.em-icon-last-circle { -webkit-mask-image: var(--icon-last-circle); mask-image: var(--icon-last-circle); } .em .em-icon.em-icon-cross-circle { -webkit-mask-image: var(--icon-cross-circle); mask-image: var(--icon-cross-circle); } .em .em-icon.em-icon-checkmark-circle { -webkit-mask-image: var(--icon-checkmark-circle); mask-image: var(--icon-checkmark-circle); } .em .em-icon.em-icon-close { -webkit-mask-image: var(--icon-close); mask-image: var(--icon-close); } .em .em-icon.em-icon-chevron-down { -webkit-mask-image: var(--icon-chevron-down); mask-image: var(--icon-chevron-down); } .em .em-icon.em-icon-chevron-up { -webkit-mask-image: var(--icon-chevron-up); mask-image: var(--icon-chevron-up); } .em .em-icon.em-icon-magnifying-glass { -webkit-mask-image: var(--icon-magnifying-glass); mask-image: var(--icon-magnifying-glass); } .em .em-icon.em-icon-location-on { -webkit-mask-image: var(--icon-location-on); mask-image: var(--icon-location-on); } .em .em-icon.em-icon-location-off { -webkit-mask-image: var(--icon-location-off); mask-image: var(--icon-location-off); } .em .em-icon.em-icon-checkmark { -webkit-mask-image: var(--icon-checkmark); mask-image: var(--icon-checkmark); } .em .em-icon.em-icon-plus { -webkit-mask-image: var(--icon-plus); mask-image: var(--icon-plus); } .em .em-icon.em-icon-minus { -webkit-mask-image: var(--icon-minus); mask-image: var(--icon-minus); } .em .em-icon.em-icon-compass { -webkit-mask-image: var(--icon-compass); mask-image: var(--icon-compass); } .em .em-icon.em-icon-options-v { -webkit-mask-image: var(--icon-options-v); mask-image: var(--icon-options-v); } .em .em-icon.em-icon-point-down { -webkit-mask-image: var(--icon-point-down); mask-image: var(--icon-point-down); }Hi everyone, sorry about that, 6.1 fixes that xxx issue (unfortunate combo of keystrokes added during testing!) and if you disable advanced mode or set that overriding setting to ‘no’ you’ll get our default template without the xxx
Forum: Plugins
In reply to: [Events Manager - Calendar, Bookings, Tickets, and more!] 6.1 update errorHi everyone, sorry for the bug which is now fixed in a dev version you can already get. Here’s my reply on the issue, reposted from this thread:
For anyone with this issue, we’ve updated a dev version 6.1.0.1 which fixes this specific issue (tested and confirmed). We’ll release a regular update within the next day or sooner.
To upgrade to a dev version, visit Dashboard > Events > Settings > Admin Tools and click the Check Dev Updates button. You’ll see the update appear on your plugins/updates page. You can also manually update by downloading the dev versions from our downloads page. For more detailed instructions, see our documentation for upgrading to dev versions.
The issue was mainly related to the adding of UUID for old bookings and ticket bookings, in theory this shouldn’t have affected your installation as the main use of UUIDs are currently for the recent Pro features like QR tickets and checkins.
It looks like the error is limited to those using MariaDB (correctly identified by @guidodr) instead of mySQL, that RANDOM_BYTES function in the SQL statement is available in MariaDB 10.10 and I believe we misread the min WP version with 10.1 (the trailing 0 made all the difference!). Whilst we usually keep relatively straightforward SQL statements, we’ll be more mindful of our MariaDB users moving forward, should we ever need to add with more complex queries.
- This reply was modified 2 years, 1 month ago by Marcus (aka @msykes).
Hi everyone, sorry for the bug which is now fixed in a dev version you can already get. Here’s my reply on the issue, reposted from this thread:
For anyone with this issue, we’ve updated a dev version 6.1.0.1 which fixes this specific issue (tested and confirmed). We’ll release a regular update within the next day or sooner.
To upgrade to a dev version, visit Dashboard > Events > Settings > Admin Tools and click the Check Dev Updates button. You’ll see the update appear on your plugins/updates page. You can also manually update by downloading the dev versions from our downloads page. For more detailed instructions, see our documentation for upgrading to dev versions.
The issue was mainly related to the adding of UUID for old bookings and ticket bookings, in theory this shouldn’t have affected your installation as the main use of UUIDs are currently for the recent Pro features like QR tickets and checkins.
It looks like the error is limited to those using MariaDB (correctly identified by @guidodr) instead of mySQL, that RANDOM_BYTES function in the SQL statement is available in MariaDB 10.10 and I believe we misread the min WP version with 10.1 (the trailing 0 made all the difference!). Whilst we usually keep relatively straightforward SQL statements, we’ll be more mindful of our MariaDB users moving forward, should we ever need to add with more complex queries.`
- This reply was modified 2 years, 1 month ago by Marcus (aka @msykes).
- This reply was modified 2 years, 1 month ago by Marcus (aka @msykes).
For anyone with this issue, we’ve updated a dev version 6.1.0.1 which fixes this specific issue (tested and confirmed). We’ll release a regular update within the next day or sooner.
To upgrade to a dev version, visit Dashboard > Events > Settings > Admin Tools and click the Check Dev Updates button. You’ll see the update appear on your plugins/updates page. You can also manually update by downloading the dev versions from our downloads page. For more detailed instructions, see our documentation for upgrading to dev versions.
The issue was mainly related to the adding of UUID for old bookings and ticket bookings, in theory this shouldn’t have affected your installation as the main use of UUIDs are currently for the recent Pro features like QR tickets and checkins.
It looks like the error is limited to those using MariaDB (correctly identified by @guidodr) instead of mySQL, that RANDOM_BYTES function in the SQL statement is available in MariaDB 10.10 and I believe we misread the min WP version with 10.1 (the trailing 0 made all the difference!). Whilst we usually keep relatively straightforward SQL statements, we’ll be more mindful of our MariaDB users moving forward, should we ever need to add with more complex queries.
Hi Henning,
Firstly, thanks for the 5* regardless of your issues 🙂
I appreciate that the update came as a shock. It’s a big update and makes huge changes to our UI, which made it quite trickly to make into a seamless update.
I’ve written a post about the update (and why the perception of lack of testing, whilst understandable, is untrue) that covers all of this plus some more insight, and a link to a migration guide here – https://wp-events-plugin.com/blog/2022/08/11/about-those-new-updates/
I hope you can get up and running with 6.0 soon and enjoy all the benefits of the new features that are already starting to roll out.
Now with 6.1 we’re doubling back to help as many people as possible with the transition. If you’re still one of those do get in touch via the support forums.
Forum: Reviews
In reply to: [Events Manager - Calendar, Bookings, Tickets, and more!] It’s a shameHi! Your review was accurate… whilst you can easily override our templates even in earlier versions to tweak any design issues, it should have been responsive out the box by now. We’ve been working on an update for some time that addresses the responsive issues which is now 6.0!
The reservations via admin is a Pro feature, we’ve had that for a long time now.
Hope you’ll try the plugin again if you’re not already, and if so, hope you enjoy 6.0!
Hi Henning,
I appreciate that the update came as a shock. It’s a big update and makes huge changes to our UI, which made it quite trickly to make into a seamless update.
That said, new users shouldn’t experience any of this, and for those updating from custom styling we have tons of styling options that lets you disable/enable pretty much everything, including the changing of fonts and you can always re-vert back to the templates of 5.0 via our template overriding system.
Regarding maps API usage, that hasn’t changed so if you’re having issues there get in touch with our support forums.
I’ve written a post about the update that covers all of this plus some more insight, and a link to a migration guide here – https://wp-events-plugin.com/blog/2022/08/11/about-those-new-updates/
I hope you can get up and running with 6.0 soon and enjoy all the benefits of the new features that are already starting to roll out.
I appreciate that the update came as a shock. It’s a big update and makes huge changes to our UI, which made it quite trickly to make into a seamless update.
The ‘xxx’ you’re totally right about, it was an oversight which we left there whilst testing all our template overriding features. We have so many ways to override things we didn’t see that lingering test text.
That said, new users shouldn’t experience any of this, and for those updating from custom styling we have tons of styling options that lets you disable/enable pretty much everything, and you can always re-vert back to the templates of 5.0 via our template overriding system.
I’ve written a post about the update that covers all of this plus some more insight, and a link to a migration guide here – https://wp-events-plugin.com/blog/2022/08/11/about-those-new-updates/
I hope you can get up and running with 6.0 soon and enjoy all the benefits of the new features that are already starting to roll out.
Forum: Reviews
In reply to: [Events Manager - Calendar, Bookings, Tickets, and more!] Unreliable pluginHi Henning,
I appreciate that the update came as a shock. It’s a big update and makes huge changes to our UI, which made it quite trickly to make into a seamless update.
That said, new users shouldn’t experience any of this, and for those updating from custom styling we have tons of styling options that lets you disable/enable pretty much everything, and you can always re-vert back to the templates of 5.0 via our template overriding system.
I’ve written a post about the update that covers all of this plus some more insight, and a link to a migration guide here – https://wp-events-plugin.com/blog/2022/08/11/about-those-new-updates/
I hope you can get up and running with 6.0 soon and enjoy all the benefits of the new features that are already starting to roll out.
- This reply was modified 2 years, 1 month ago by Marcus (aka @msykes).
- This reply was modified 2 years, 1 month ago by Marcus (aka @msykes).