Hello there,

Thank you for reaching out to us.

When you have several questions or issues please open a new separate ticket, and we will help you there. In that way, issues and questions that are related to different subjects will be in separate tickets so other customers or our support agents can find them easily. 

Our policy is to have one issue or question per ticket because of the reasons that are described already.

Thank you for understanding. 

We will take a look at this now and we will reach out to you again on this ticket as soon as we have more information. 

Hello again,

1. My client uses single catalog view a lot  [ameliacatalog category=1]  on specific pages. 
   There is no suitable alternative in V2. ameliacatalogbooking has a lot of UI bloat, we just want a list with blocks. (as V1 has). The V1 version is also visually much more appealing for my client.
   Ideally we have some kind of shortcode that can replace V1, for instance
    [ameliacatalogbooking category=1 view=cleangrid] (or something) - All available shortcodes that we can offer you can find on this link https://wpamelia.com/amelia-shortcodes/
   These are available shortcodes for catalog form
   [ameliacatalogbooking ] if you want to show the basic Service Catalog view,
   
   [ameliacatalogbooking category=1] if you want to show only the services from a category with ID 1,
   [ameliacatalogbooking service=1] if you want to show this form for the service with ID 1,
   [ameliacatalogbooking employee=1] if you want to show the services of one specific employee with ID 1,
   [ameliacatalogbooking location=1] if you want to show the services of one specific location with ID 1,
   [ameliacatalogbooking category=1 employee=1] if you want to show only the services from a category with ID 1 that are assigned to the employee with ID 1,[ameliacatalogbooking category=1 location=1] if you want to show only the services from a category with ID 1 that are provided on the location with ID 1,[ameliacatalogbooking show=services] if you have Packages enabled, but only want to show services in the form,
   [ameliacatalogbooking show=packages] if you have Packages enabled, and you only want to show packages in the form,
   [ameliacatalogbooking package=1] if you want to show one package on the form, the package with ID 1.

2. For the ameliabooking: We do not want to enforce the client to select an employee,  We are missing the option "random employee" as we see it in V1, Because selecting an employee up front would drastically reduce the options (dates & times), we need to have this option in V2 too. - You have it but it looks in a different way. You just set field to not be mandatory and they then do not have to choose employee and it will be assigned at random. These are new looks and they will not be changed and they were created based on majority of votes in our large use case study groups. 

3. Styling issues:
- i cannot seem to style the blue color in the ameliacatalogbooking V2. There are no settings for it.
- Same is for Amelia events, i cannot adjust the blue left border. not even with CSS enforcement. - Evrtyhing that can be customized can be found in customize section and colors can be changed. Border are not built in so something can be changed via CSS some things can not.

In light of this, we encourage you to kindly consider submitting this valuable suggestion as a feature request through the following link: https://features.wpamelia.com/. The prioritization of feature development is greatly influenced by the number of customer requests received. By participating and expressing your support, you contribute significantly to the potential expedited implementation of this feature.

4. translation issues:
- You say you support dutch translation, but almost half of the fields are not translated. translating each label in each form independently is a lot of work.  - Please note that we do not have translators in our company, so all translated languages Amelia has have been translated by our customers. So we wait for ne strings to be sent. If you find any inconsistencies with the translation, please feel free to correct them using POEdit, or Loco Translate, open a ticket and send us the corrected translation, so we can add it to the plugin.

5. Unfortunately we have to conclude we can not migrate to V2 yet in these conditions. 
Please help us because we would love to use V2, but currently it's not good enough and we would go backwards. - We are sorry to hear that you do not like the new forms. However, over time, it will be necessary to transition to them, as the old forms will eventually be deprecated. New 2.0 will not be chnaged as they were recently redesigned. Additionally, old forms are no longer maintained, and new features are not available for them.

Regarding the requests in this ticket, most of the changes you are asking for are not possible. The design and functionality of the new forms have been adjusted, and we do not plan to revert to previous options or layouts. As mentioned during the redesign process, we conducted extensive case studies with large user groups, and the majority of users selected the current design and functionality. While we understand that this may not fully meet your specific needs, we are aware that it is not possible to satisfy 100% of market demands.

Should you have any further inquiries, we kindly request that you open separate tickets for each question, and we will gladly assist you there. Our policy is to have one issue or question per ticket.

We wish you all the best and hope you have a wonderful day ahead.