Since 2.1 update, Delete notifications for employees have no data for predefined fields.

For this employee delete notification config : 

Annulation de séance !
%customer_full_name% (1ère séance : %custom_field_3%)
%customer_phone% ; %customer_email%
%appointment_date% à %appointment_start_time%
%appointment_price%

Sujet de la séance :
%custom_field_6%

I recieve this mail :

Annulation de séance !
(1ère séance : Oui)
;
3 septembre 2019 à 15 h 00 min
60 €

Sujet de la séance :
le sujet de la séance 

Approved and reported mails are ok. But this mails with empty fields appeared with 2.1 Amelia Plugin.

Thanks and regards,
Greg

Hi Aleksandar,

Thank you for your reply.

I want to test on my preproduction platform before apply modifications on production.

I've just tried to install 2.1.1 on my preproduction platform but I've an issue with the Notifications params... When I click on "Save config", there is an error. All seems to be ok in general configuration: I can save modifications in global configuration (also in notification connection config) but not in the notifications text config.
I've tried to delete Amelia plugin and install 2.1 but the problem persists.

I need to change notifications config to include cancel url in notifications on my preproduction platform.

I think it will a good thing to clean the amelia database on preproduction to resolve the config problem. After that, I'll can change config to include cancel url in notifications to test.

Is there a way to clean amelia db or to activate logs or debug?

For security reasons, I don't give access to my production platform.

Best regards.

Greg

Hi guys,

+1 for empty fields (placeholders) in cancelation notifications since update. I haven't encountered an server error though.

Regards,
P. 

Hi Aleksandar,

currently I use custom field (Text Content), which is applied on multiple services. But I think that the issue, to which Gregory originally referred to, is not only related to custom fields placeholders. At least in my case, it is definitely related to placeholders like %customer_name%, %customer_phone% and %service_name%. For some reason, these 3 placeholders are empty in employees' cancellation notification emails, since last update. On the other hand every other type of email notifications work properly, so it seems to be related just to cancellation notifications. Strange is that date and time placeholders are not affected by this at all.

Regards,

P.

Hi,

First of all, to be precise, in production I only encounter the same problem as Pepo48: empty fields in the employee's cancellation email.

I did a lot of tests with log capture and debug tonight on my preproduction platform ...

When canceling the appointment with the cancellation link sent to the customer, no error appears at the Apache debug level and neither at the mysql debug level.

Just differences in the mysql debug.
Some due to the new features of versions 2.1 and 2.1.1 and others that did not exist in the debug of 2.0.1:
154 Prepare SELECT * FROM modXXX_amelia_extras
154 Close stmt
....
154 Prepare SELECT
                    cf cf cf_id,
                    cflabel AS cf _...
                    ....
FROM modXXX_amelia_custom_fields cf ....
154 Close stmt

A command is passed with the version 2.0.1 but does not exist in the debug mysql of the new versions:
206 Prepare SELECT * FROM modXXX_amelia_providers_to_locations WHERE modXXX_amelia_providers_to_locations.userId =?
206 Close stmt

With version 2.0.1, once the mysql connections are gone (205 Quit 206 Quit), there is no extra data in the seconds that follow in the debug.
With version 2.1.1, new connections are made that apparently do not connect to Amelia's tables. However with this version it is systematic whereas there was none with version 2.0.1.

I hope this will help solve the problem. I can provide logs and debug via an online file transfer site if needed.

For information, I also tested after disabling all other extensions and the problem is still present.

I am going to make a private answer for the problem concerning only the preproduction platform: the notification registration error.

Best regards.

Greg

Hi Aleksandar,

I use Chrome web browser just with native Chrome spell checker and none of the plugins that you've mentioned, were used during editting the templates. Actually since last update, I edit notifications templates rather directly via database than Amelia UI. I've noticed that every new line written in notification text editor is encapsulated into paragraph html mark (<p>). Morever even break line encapsulates into paragraph now (<p><br></p>) which causes a lot of redundant blank lines in e-mails. Since there is no possibility to set a line spacing via UI, I prefer the database, where I have html syntax more under control. 

Regards,

Peter.

Hi guys,

I just made a wordpress installation any fresh and I only installed on the plugin amelia 2.1.1. Result: same problem in the cancellation notifications. I am very surprised that you are not succeeding in reproducing the problem on your side.

I will work to make this platform accessible from the internet, which will require me a little more time. I will communicate access by private message.

Regarding the problem of saving the notification configuration, I found the cause of the problem and solved it. Some php modules were missing on my test platform. After installing all those installed automatically by the hosts as o2switch, no problem at this level.

Best regards.
Greg

Gregory, kudos to you, thank you for the testing and dealing with this problem.

Aleksandar, I can't provide you my credentials. I think that I've already suggested in another ticket that there are a lot of alternatives how to approach such a situation. Sharing personal credentials without any surveillance is not the right one. Even if I fully trust you. For example sandboxes would be more than appropriate.

Please, don't get me wrong, I really appreciate all the hard work that all you guys do. We, as customers, just try to address some relevant issues to make your product even better. Our effort sometimes seems to be effortless just because of the "sharing credentials". This happened at least two times to me. Moreover I can't open tickets anymore, because my support  service expired. Ability to file relevant issues should be separated from basic end-user support. Especially more skillful customers (for example like Gregory who actually helps you, not the other way round) have a disadvantage, because they don't typically bother you just with basic questions mentioned in FAQ.

Regards,

Peter.

Hi guys,

I tested on your demo server a few days ago but it does not test the "provider mail notifications" ... so impossible to test that.

Moreover, the problem seems to arise only for the customer's name placeholders, phone number and mails. So if your other customers have not added this in employee notification emails, they are not likely to encounter the problem.

I have just made accessible a brand new test platform which I communicate to you access in private message.

Regards.

Greg

Hi guys,

I saw that you did tests and emails confirm what Peter and I have described.

Do you still need to access my platform?
Being a virtual machine, it forces me to leave my PC on permanently. So I would like to know if you have the elements that you need or if not, for how much longer do you need to access them?

Regards,

Gregory

Hi Aleksandar.

Thanks for these informations.

So, do you still need my platform or can I turn it off?

Best regards.

Gregory

Hi Aleksandar,

First of all thanks for the fix. I've just tested it and it seems that %customer_phone% placeholder still does not work. The other two affected placeholders (%customer_full_name%,%customer_email%) are working properly though.

Have a nice rest of the day.

Regards,

Peter.

Hi guys,

Thank you a lot for this fix.

On my side it works perfectly but ONLY when the customer cancels with its cancellation url. Firstname, lastname, fullname, email and phone are all in the mail. If the administrator makes the appointment canceled, then the problem persists: no name, no email, no phone ...

It's better and thank you for your work. If you also solve the problem when the administrator (employee too? Not tested ..) cancels an appointment, it will be perfect :)

If you need to use my preprod platform to test, let me know here and I'll turn it on.

Best regards.

Gregory

Hello again,

I can only confirm what's Gregory just mentioned - when an appointment is canceled from backend by administrator, the problem still persists. Moreover, it is also affecting rejection notifications right now, which definitely has not been issue before.

And as I mentioned in the previous reply, I still have problem with the %customer_phone% placeholder.

P.

Hi Aleksandar,

exactly in the same way as cancellation notification was affected - customer_full_name, customer_phone and customer_email are empty.

Regards,

P.

Hello Aleksandar.

The first time I tested after installing version 2.2, I had the same result as with the fix you sent us: ok when the customer cancels by itself but still the lack of placeholders when the admin cancels.

I then restart my preproduction platform and it works in both cases.

So for me it's solved. To see in production because I hope it will not require a reboot ... being hosted I do not have the hand and it will produce a break in service ...

Regards.

Gregory

I haven't tested the new version of Amelia yet, but I have similar experience like Gregory - phone_number placeholder, which hadn't been working for me after you provided the fix (unlike for Gregory), suddenly has started working. So my cancellation notifications seems to be fully functional right now - out of the blue (I didn't restart anything).

Problem with rejection notifications still persists though, so I will definitely check the new version and let you know.

Aleksandar, thank you and your team for your effort!

Regards,

P.