Okay
  Public Ticket #2417678
Frontend Form customization
Closed

Comments

  •  6
    Emmanuel started the conversation

    Hi, 

    I need to customize the frontend user's form, could you please tell me if it's possible and how to do?

    1 - Appointment Time

    Only the start time shows up in the form, i need to also display the end time, like 08:30 - 10:00 instead of just 08:30

    2 - Location's Address

    How could i display it in the form?

    3 - Default fields position

    How could i reverse the "Name" and "Family Name" fields in the form?
    I need to set "Family Names" first then "Name".

    4 - Default fields Labels

    How could i change the "Phone" label for "Mobile Phone"?


    Thanks for your help

    Emmanuel Soyer

  • [deleted] replied

    Hello Emmanuel, 

    Thank you for your purchase. 

    1, 2 and 3 - Unfortunately, this is not possible in Amelia with its current built-in features. It can be maybe achieved with some customization, but please note such customization isn't covered by our support. We will work on a new Customized booking form but for now we can't say when it will be implemented and released. 

    4 - You can change strings in the plugin by using the translation method, but in your case you would change strings in the same language, you wouldn't translate them to another one. 

    Strings can be changed using POEDIT or Loco Translate for example. If you want to use POEDIT then this is the instruction:

    1. Download Amelia from TMS Store

    2. Unzip the downloaded file.

    3. Download and install POEDIT

    4. Open the program and open the file from the extracted folder on your computer ameliabooking/languages/en_US/wpamelia-en_US.po.

    5. Change the strings you want.

    6. Save the translation.

    7. Go to ameliabooking/languages/en_US/ folder and copy these two files - wpamelia-en_US.po and wpamelia-en_US.mo back to your website to the location ../wp-content/plugins/ameliabooking/languages/en_US/.

    Please note that this change will be deleted when you update Amelia, so you will need to change this after each update of Amelia. 

    If you have any further questions feel free to ask.

  •  6
    Emmanuel replied

    Hi Marija, 

    Thanks for your details. 

    1, 2 and 3 - Ok, i'll live without these options. 

    4 - Ok, i managed in the .po/.mo files allright but now that you mention it, it's a pity they'll be removed at next update. Isn't there a way to store them in the child theme (the usual way assuming it's handled by the plugin)?

    Or should i rather use a gettext filter in function.php maybe? 

    Best regards
    Emmanuel

  • [deleted] replied

    Hello Emmanuel, 

    You are welcome. 

    There isn't a possibility to change them elsewhere and if you change it in the code of the plugin, it would be still overridden with the update. I think with some of the translation tools there is the option to save the changes and then when you update the plugin apply the changes again, but you would still need to do this after each update of Amelia, unfortunately. 

    If you have any other questions or concerns feel free to open a new ticket and we will gladly help.

  •  6
    Emmanuel replied

    Hi Marija, 

    Thanks for confirming. 

    I guess you'll agree that the procedure described is not really sustainable? 

    Do we really need to manually replace the custom language file after EACH Amelia's update? 
    Would you consider adding support of custom files located in the child theme?
    It would allow Amelia's users to safely store their customizations and avoid them useless extra work.

    Thanks.

    Emmanuel

  • [deleted] replied

    You are welcome, Emmanuel.

    At the moment, this is how strings changes can be achieved in Amelia. Unfortunately, there isn't any other way. We will add this as a feature request and check if this behavior can be modified somehow in the future. 

    If you have any other questions or concerns feel free to open a new ticket and we will gladly help.

  •  6
    Emmanuel replied

    Managing custom text in the lang file is ok, but having to replace the .mo after each Amelia's update is a pain and really unsafe.

    I just suggested to add support for this customized file in the theme child. ;-)

    Emmanuel 

  • [deleted] replied

    Yes, I get your point. Thank you for the suggestion, I will add it as a feature request, so it can be considered for modification in the future. 

    If you have any other questions or concerns feel free to open a new ticket and we will gladly help.

  •  6
    Emmanuel replied

    Nice, thanks!

  • [deleted] replied

    You are welcome!

    If you have any other questions or concerns feel free to open a new ticket and we will gladly help.