So to cut a veeeeery long support story short, Lithium support had a hard time to understand our requirement.   Finally in the platform, the following format was enabled for us and can be chosen now from admin:   dd-MMM-yyyy , resulting in 18-Nov-2016    It is not quite what we asked for, but better than a purely US or EU format that can be easily misunderstood.   Strange enough though, if you enter dd MMM, yyyy" (resulting in eg. "6 Jul, 2016")   in the field  Time display format, the platform produced exactly what we wanted, however on the wrong position, so I still do not understand why our requirement is too complex for Lithium to deal with.  ... View more

I bring up a question from our devs.:   We tried to make the search request on a different domain as the community.  Lithium Community page does not contain any "Access-Control-Allow-Origin" header parameter in their response and because of that, it is not possible to make a proper AJAX request ( from JavaScript ). If AJAX response does not contain configured "Access-Control-Allow-Origin" header parameter, then it is not possible to make cross domain requests.   Is it possible to configure this for the Community page?    Or is there some kind of specific "public Lithium API Endpoint", against which there would be no problem to make AJAX requests? ... View more

In Admin -> System - > Date and Time   I have choice only for  MM-dd-yyyy dd-MM-yyyy yyyy-MM-dd Use default (MM-dd-yyyy)   The option to change the string manually is not available. Has this changed or do I need to request permission from Lithium for this? ... View more

Not quite the same, but fitting to the title.   We would like to create an external web form to submit a ticket.   When the subject line is being entered, community suggestions should be displayed, just the same as on the community search. This is supposed to deflect requests to the community before they are submitted.    Can the search dropdown scoping the full community be called through the API while typing? ... View more