With Step-Form 2.0 we are finally able to implement Amelia into several customer projects. During implementation, we encountered a lot of issues, inconsistencies, especially with translatability.
This list shows only the most prevalent so far:
Left sidebar, "Get in Touch"
Period selector default value not translatable in Recurrence, always shows "day":
Weekdays in recurrent slots are not translatable:
Wording structure here doesn't work, not even for English: Day, Week, Month should have a plural if the selector is >1.
Not a single one of our testers was able to intuitively understand the "Recurring on" section here. When translated, it gets even more weird. You should insert "week" by default, like "first week, second week, …"
In the same screenshot visible: You are also very inconsciese regarding punctuation. Sometimes a colon is part of the string/label, sometimes not. I'd prefer to have control over the punctuation as part of the label itself.
Date format in Recurrence is fixed at YYY-MM-DD.
Recurrence Warning, Wording structure not translatable: "# slots you selected …" is already bad in English when it is only one, but in many other languages this is messy at best. But the number of issues is not so relevant and I'd suggest leaving it out, something like: "Some of the selected slots are unavailable. Please change the highlighted dates below."
Dates for recurring slots are YYY-MM-DD only. Also: this is bad design. Can you please space this out a little better. The dot-menu on the right is redundant, a trashcan-icon would be much better. Also, the arrow that opens the calendar is out of context. It would be better to replace it with a text linke like "reschedule" or with a calendar icon.
The phone number in "your information" is too small in relation to the other input fields because of the completely unnecessary animation. Please remove the animation and stick to consistent design over non functional eye candy.
Also in "your information", custom fields' error messages can't be translated and there are no labels for the default value like in the other sections.
You should add the possibility to choose between these options everywhere a service is mentioned: %service_name% %category_name% %category_name% %service_name%
The reason is simple: With the long overdue implementation of categories, we can finally name a service by its name and not include the category. But this means, that the service name itself is not sufficient information or the wrong term in some cases. For example:
Please add an optional Text/HTML field to the every step, at the top and bottom would be best. Especially for payment summary. Most of our clients want/must give additional information regarding payment, like accepted payment types at the practice for example.
I'd also suggest you either shorten the release cycle or publish additional beta-releases here as long as the Step-Form 2.0 is actively develop in beta. In its current state it is not usable when translation is needed. But the necessary changes are very minor. It would be great if we wouldn't have to wait until the next major release or even longer.
Regarding the translation words can be changed using POEDIT or Loco Translate for example very easily. I suggest you install Loco Translate and then translate these strings.
If you want to use POEDIT then this is an instruction:
1. Download the Amelia plugin from CodeCanyon and save the .zip file on your computer.
4. After that open the program and open the file from the extracted folder on your computer ameliabooking/languages/fr_FR/wpamelia-fr_FR.po.
5. Translate all the strings that are not translated
6. Save the translation.
7. Go to ameliabooking/languages/fr_FR/ folder and copy these two files called wpamelia-fr_FR.po and wpamelia-fr_FR.mo back to your website in the location ../wp-content/plugins/ameliabooking/languages/fr_FR/.
This is an example of the French language, but you will choose yours.
As for your suggestions, we thank you and will forward them to the appropriate sections also if you wish you can add them as a suggestion on this page also.
We can't promise you anything right now and give you an eta, but the ticket will be forwarded along with your suggestions.
Hi
With Step-Form 2.0 we are finally able to implement Amelia into several customer projects. During implementation, we encountered a lot of issues, inconsistencies, especially with translatability.
This list shows only the most prevalent so far:
Left sidebar, "Get in Touch"
Period selector default value not translatable in Recurrence, always shows "day":
Weekdays in recurrent slots are not translatable:
Wording structure here doesn't work, not even for English:
Day, Week, Month should have a plural if the selector is >1.
Not a single one of our testers was able to intuitively understand the "Recurring on" section here. When translated, it gets even more weird. You should insert "week" by default, like "first week, second week, …"
In the same screenshot visible: You are also very inconsciese regarding punctuation. Sometimes a colon is part of the string/label, sometimes not. I'd prefer to have control over the punctuation as part of the label itself.
Date format in Recurrence is fixed at YYY-MM-DD.
Recurrence Warning, Wording structure not translatable: "# slots you selected …" is already bad in English when it is only one, but in many other languages this is messy at best. But the number of issues is not so relevant and I'd suggest leaving it out, something like:
"Some of the selected slots are unavailable. Please change the highlighted dates below."
Dates for recurring slots are YYY-MM-DD only. Also: this is bad design. Can you please space this out a little better. The dot-menu on the right is redundant, a trashcan-icon would be much better. Also, the arrow that opens the calendar is out of context. It would be better to replace it with a text linke like "reschedule" or with a calendar icon.
The phone number in "your information" is too small in relation to the other input fields because of the completely unnecessary animation. Please remove the animation and stick to consistent design over non functional eye candy.
Also in "your information", custom fields' error messages can't be translated and there are no labels for the default value like in the other sections.
You should add the possibility to choose between these options everywhere a service is mentioned:
%service_name%
%category_name%
%category_name% %service_name%
The reason is simple: With the long overdue implementation of categories, we can finally name a service by its name and not include the category. But this means, that the service name itself is not sufficient information or the wrong term in some cases. For example:
Physiotherapy (%category%)
--- Initial Consultation (%service%)
--- Treatment (45min)
--- Treatment (60min)
Osteopathy (%category%)
--- Initial Consultation (%service%)
--- Treatment (45min)
--- Treatment (60min)
Please add an optional Text/HTML field to the every step, at the top and bottom would be best. Especially for payment summary. Most of our clients want/must give additional information regarding payment, like accepted payment types at the practice for example.
I'd also suggest you either shorten the release cycle or publish additional beta-releases here as long as the Step-Form 2.0 is actively develop in beta. In its current state it is not usable when translation is needed. But the necessary changes are very minor. It would be great if we wouldn't have to wait until the next major release or even longer.
Hello Sebastian,
Thank you for reaching out to us.
Regarding the translation words can be changed using POEDIT or Loco Translate for example very easily. I suggest you install Loco Translate and then translate these strings.
If you want to use POEDIT then this is an instruction:
1. Download the Amelia plugin from CodeCanyon and save the .zip file on your computer.
2. Unzip the downloaded .zip file.
3. You need to download and install POEDIT.
4. After that open the program and open the file from the extracted folder on your computer ameliabooking/languages/fr_FR/wpamelia-fr_FR.po.
5. Translate all the strings that are not translated
6. Save the translation.
7. Go to ameliabooking/languages/fr_FR/ folder and copy these two files called wpamelia-fr_FR.po and wpamelia-fr_FR.mo back to your website in the location ../wp-content/plugins/ameliabooking/languages/fr_FR/.
This is an example of the French language, but you will choose yours.
As for your suggestions, we thank you and will forward them to the appropriate sections also if you wish you can add them as a suggestion on this page also.
We can't promise you anything right now and give you an eta, but the ticket will be forwarded along with your suggestions.
We wish you all the best.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables