We're Moving to a New Support Platform – Starting June 1st!

We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.

You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.

While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.

We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.

Thanks for your continued support and trust – we’re excited to bring you an even better support experience!

Okay
  Public Ticket #3095286
Custom Fields Issues
Closed

Comments

  •  3
    Sebastian started the conversation
    August 1, 2022 at 3:52pm

    It is increasingly frustrating how many features in Amelia are only superficially implemented and not thought through to the end.

    While trying to get custom fields working for my clients, I ran into multiple dead ends – of course translations, but also these:

    • Attachment: This is a MCA bound to happen. There is no way to limit the upload file size, type or number.
      How can we only allow i.e. PDF 2MB max?
    • Date Picker: As my clients are mostly healthcare providers, we need patients birth date. The Date Picker you implemented starts at the current year and has no means of quick selection for the year or manual entry. A manual text field is no alternative, as there is no validation method (ie. regex).
      How can we give our users born before 2010 a date input without the risk for severe tendonitis?
    • Lack of element identification: As you offer exactly nil control over the layout/formatting of custom fields, we need to target individual fields via CSS. But, there is no distinction between fields in the code. For example, two Text Content fields are only distinguished in the content of the inner DIV. This really should be addressed, for example through manual classes for each field.
      How can we target individual custom fields in CSS?
    • Layout: in addition to the previous one, there should be at least these options to create meaningful forms:
      • sections/groups
      • headlines
      • dividers
      • column count per field

    I'm tired of adding any of this to your roadmap. All of this above are very basic features that should've have been implemented right from the start of a custom fields feature and it shouldn't need a user request to implement those.

    Comparing the release logs to the list of feature requests, I grow more and more suspicious that https://features.wpamelia.com/ is nothing more but a way to silence users in here. Maybe if there was some visible management, my trust would grow again.

    Best,

    Sebastian

  •  1,726
    Marko replied
    August 2, 2022 at 9:13am

    Hello Sebastian,

    Thank you for reaching out to us.

    We will try to answer all your questions as best as possible.

    Attachment - The upload size depends on WordPress' upload size which can be seen if you go to Media/Add New - in the lower right corner, the maximum upload size is displayed, and it will be used for the "attachment" custom field size as well. This can be changed in the php.ini file, updating the following entries:

    upload_max_filesize
upload_max_size

    Date Picker - this has been reported, and our developers are working on it. It's coming from a 3rd party HTML5 library, so we'll need to find a replacement. Hopefully, that will be included in one of our upcoming updates. 

    Element identification - At the moment, you can't target individual custom fields in CSS, but we will forward your suggestion to our developers, so they can include it in one of our future updates 

    Layout - thank you for your suggestions, we'll forward them to our developers as well. 

    We're sorry to hear you gained that impression about our feature suggestion page, but the reality is quite on the contrary. 

    The page you're voting on now is relatively new. Previous feature suggestion page can be found here (https://wpamelia.cnflx.io/boards/feature-requests) and in there, you can filter the suggestions, and show "Implemented" suggestions. In there, you can find over 20 suggestions which were implemented over time. 

    While we appreciate every customer's suggestion, please note that we develop new features and improve existing ones based on the number of votes, their complexity, and according to our company's plan. 

    Also, some features that are crucial for your business may not be crucial for the majority of other users, so we thank you for your patience. I will do my best to prioritize your request with our development team, but I can't make any promises.

    If you have any more questions please open another ticket and we will gladly help you there.

    We wish you all the best.

    Kind Regards, 

    Marko Davidovic marko.davidovic@tms-outsource.com

    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