Extended debugging e-mail/template dispatch
Many customers customize the email templates for their shop. It often happens that certain e-mail templates are no longer sent because, for example, variables are incorrect.
Troubleshooting the cause is then very difficult and time-consuming because:
- There are no errors in the log with indications of the cause.
- The e-mail test function still works with the e-mail template because variables are ignored.
As a result, the e-mail template and the variables have to be checked with a great deal of effort and there are a lot of support tickets for this, as customers quickly reach their limits.
In order to help customers and reduce the number of support tickets, it would therefore be useful to have extended debugging for sending emails. It should be possible to recognise from which line the e-mail dispatch fails.
This would allow the customer or the support team to name and recognise the line directly and, if necessary, find the error within seconds. This leads to less time for troubleshooting and frustration for customers.
AdminBenjamin Hummel
(Admin, shopware AG)
shared this idea
-
Kilian Domaratius
commented
It helps to change environment to dev instead of prod. This enables email send logging and shows errors at event logs in the settings.
-
Oliver Wagner
commented
EN
I consider this an urgent problem because you get ZERO feedback that something is wrong!
–
DE
Erachte ich als dringendes Problem, weil man NULL Feedback bekommt, dass etwas nicht stimmt!(Edited by admin) -
Time and again, customers have the problem with the mailer. It would be helpful and less time-consuming for customers and support if there were a test function for the access data in the mailer.
This means that it is not necessary to first look in the shopware logs or test mail templates.
Since the error message is available in the shopware log, it could be read out by the test function and reported to the customer.