When I check some field to be required, I would expect some indication of the fact. And in the case of the regular fields the indication is shown (as *), whereas in the case of custom fields it's not. So there's no way for the user to know which fields are required before pressing the post ad button.

When I try to post an item with a required fields, I would expect not to loose content of any other filled field when some required fields are missing. But this is what happens, and it only happens in the case of the custom fields, not the regular ones. It's really frustrating for users to fill the form over and over and loose all the input data because of last of the aforementioned information.

Point with star is good, we will take a look on that.
Regular fields use session to temporary hold values, not sure if this was made for custom fields as well, probably not.

When I check some field to be required, I would expect some indication of the fact. And in the case of the regular fields the indication is shown (as *), whereas in the case of custom fields it's not. So there's no way for the user to know which fields are required before pressing the post ad button.

What prevents you from adding to the text in the launcher (this field is mandatory)? Or put the same *?

I did this as a temp solution. But it looks horrible...

When I add some field with name, for instance Some name * it will be printed as  Some name *:

The other issue with the custom fields is with the select type of the fields -- it has the Select word in front of the field, and it can't be translated.

Also the date to be selected in the custom field is only in English.

The other issue with the custom fields is with the select type of the fields -- it has the Select word in front of the field, and it can't be translated.

Also the date to be selected in the custom field is only in English.

Custom fields are also translated.
Try downloading the (native) English launcher and re-translate. Perhaps you do not have the necessary fields for translation in the version you provided.

I updated from source, so I think I have all the fields that are needed. This select text isn't the only one that can't be translated -- there a couple more, for instance Drop files here to upload when you send files posting ad (I saw more, but I can't now recall where).

I updated from source, so I think I have all the fields that are needed. This select text isn't the only one that can't be translated -- there a couple more, for instance Drop files here to upload when you send files posting ad (I saw more, but I can't now recall where).

Take a screenshot where there is no translation?

Ok, I think I've found the Select text. But still can't find  Drop files here to upload:

I think the date in the custom fields will be translated automatically once the date in the Osclass settings is. I have no idea how to set the locale for it:

Any ideas?

There is a built-in translator in Osklass 8.1.
Go to the panel - Translations select the language, subject, open and translate the empty lines.

I'm using linux/poedit. I've translated the whole core/theme (the one I'm using and the default) almost all flash messages. So probably I've all entries translated.

I can even see in the core phrases like Feb, February and they are translated. So why in Osclass I see the original English text instead of the translation?

The cron section in the Osclass settings seems to see the right localized names of the months.

The date settings in the dashboard seems to affect the date format. So it looks like the date settings works for some parts of Osclass, but not for all of them.

@morfik
Date function cannot be translated, probably depends on language set for PHP.

@morfik
Date function cannot be translated, probably depends on language set for PHP.

How to change it?