Hello,

Thank you for reaching out to us.

1. Notification templates are not included in the translations, so when you access Amelia/Notifications, all templates will be in English. However, if your site is set to German (for example), the de_DE locale will be applied, and Amelia will use the templates you see in Amelia/Notifications, so if you don't translate these, all email notifications will be sent in English.

   In cases like this, DO NOT add your language as a secondary language in Amelia. It is the primary language of your website, and Amelia will use it as a primary language.

   Since your site is configured to your language in WordPress General Settings (German in this example), you only need to translate the templates you see when you land in Amelia/Notifications. The language drop-down you see in the top right is used only for additional languages (so, if the site is in German, you will add English, Spanish, Dutch, etc) through this menu:

   

   So, if you have issues with emails coming in in English, instead of the language your WordPress site is set to, make sure you haven't added your language as the additional language, and translate the templates you see when you land in Amelia/Notifications.

2. For this purpose, you will have to set up a cronjob. 

   cron is a Linux utility that schedules a command or script on your server to run automatically at a specified time and date. A cron job is the scheduled task itself. Cron jobs can be very useful to automate repetitive tasks like in our plugin for notifications.

   Depending on the server, there are different configurations for it, which you can contact your hosting provider about, or you can check out one of the solutions for it on this link.

   Also, you can try this:

   */15 * * * * wget -q -O - "https://www.yourwebsite.com/wp-admin/admin-ajax.php?action=wpamelia_api&call=/notifications/scheduled/send"

   Or this:

   */15 * * * * /usr/local/bin/php ~/public_html/wp-cron.php --action='wpamelia_api' --call='/notifications/scheduled/send'

   Or this:

   GET 'https://yourdomain.com/wp-admin/admin-ajax.php?action=wpamelia_api&call=/notifications/scheduled/send' > /dev/null

   WP Crontrol plugin is the best option if you're not familiar with cron jobs. You can find more info about it, and detailed instructions on how to set it up in our FAQ section.

   So, if you already read that, and still need some clarification here's some further info.

   You copy only the URL from below a scheduled notification:

   

   Then, go to Tools/Cron Events, and click on the "Cron Schedules" tab. In it, add a 15-minute interval:

   

   Then go back to the "Cron Events" tab and click on "Add new":

   

   Below it, select the "PHP Cron event" radio button, and add the URL you copied from Amelia/Notifications in this form:

   file_get_contents("yourURL");

   

   Below it add the name and set it to run a few minutes in the future, using the provided time format. So, if you're adding the cron event at 12:45 (local, current time), set it to run at 12:50; and then select the schedule you previously selected:

   

   Click on Add Event, and that's it.

   The cron runs every 15 minutes and checks if there's an email to be sent. So, in Amelia Notifications, your scheduled notifications are set to run every day at a certain time. If you set that time to be 15:00 (for example), the emails will be sent when the cron runs after that time.

   For example, there's an appointment booked for tomorrow, and it's currently 14:44 - the cron runs, but since it's not yet 15:00, it doesn't send anything. It runs again after 15 minutes, so at 14:59, but there are still no emails flagged by Amelia, so it doesn't send anything. Then it runs again at 15:14 and it sees there's an email that should've been sent at 15:00, so it sends the email. It will only send emails when Amelia sees an appointment scheduled for the next day.

   I hope that helps.

Hello Kharisma,

Thank you for the update on this.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.