Ambyomoron

An older version of this plugin allowed users to register for courses without having to login to a WP account. Why was the necessity to have a WP account introduced? I have no idea. But from my perspective it was a major error of judgement on the part of the plugin designers.

That fixes the problem. No more warning; the correct email confirmation is now sent. Thank you!

After installing the upgrade, the following error message appears in the page opened when the customer clicks on the link in the email to cancel the meeting:

Warning: Undefined variable $email_cancel_label in /blah/wp-content/plugins/webba-booking-lite/templates/frontend_v5/cancellation_form.php on line 17

I have modified the text and saved it, but the problem still exists. I checked the value as stored in the database. The backslash is already there, so the problem concerns how the code validates the input text and attempts to clean it, I suppose.

Requested screenshot has been sent.

That’s the ticket! Thank you.

At the very least, a response in this thread to explain the plugin developer’s intentions would be de rigueur.

Thank you for the reference on how to disable automatic updates. I hope that works.

For the precise reason that your plugin is at the nexus of customer satisfaction and financial gain, I have a test environment. I never update anything in the production environment until I have first deployed the change and tested in in the test environment. By performing an update without my permission you short circuit my operational processes, processes that most IT professionals would consider to be of critical importance.

I can understand why the publishers of WP might want to protect users lacking the technical knowledge needed to run a commercial web site. But do they also take responsibility if a critically urgent patch turns out to introduce new bugs???

I had the same problem: emails were sent saying that the plugin was updated automatically, even though automatic update was definitely NOT set. However, I did manually update the plugin. So, is the problem that the plugin has confused manual update with automatic update? Or is the problem that the plugin is doing an automatic update even when WP is not set to perform automatic updates?

Note, in addition, that I have manually updated multiple other plugins at the same time and none of those other plugins generated any email about being automatically updated. So the issue is specific to this plugin.

Many thanks for the rapid response. No more deprecation messages from your plugin. Bravo for being the only organization, among all the other I have notified, that has addressed this issue rapidly!

In my system, these errors were introduced with the upgrade to ver 2.4.3

WP 6.1
Elementor 3.8.1
PHP 7.4

The message appears on all pages (but note that the deprecated function appears in ELementor, too!).

• This reply was modified 2 years, 4 months ago by Ambyomoron.
• This reply was modified 2 years, 4 months ago by Ambyomoron.

Oh, OK. So what you mean is on the screen where you create a custom field, you set the value of the field “Field purpose” to “Events field”.

debug.log sent as requested