Event creation backend language / Events without tickets

[jacotec]

I've discovered alf.io which is really extremely close to what I'm looking for since some time: A self hosted event calendar for our village. So I spun up a docker and played with it. Unfortunately it currently has some "blockers" to use it like this:

• I can't find the backend language setting for the "event creators". This form is always shown in English and we have a lot of (older) people in local organizations who would need to create events but who don't speak a word English. The "frontend" works in German.
• I can't see a setting to allow events without tickets. Apart from events which would benefit from a ticket booking there are also events where people just can "pop up" which should also be in the calendar
• I can't see the ability to make the fields "Terms and Conditions URL" and "Website URL" of an event optional. These are not required for my use case.

Did I overlook other config options (env variables) for this, or are these features which are simply (not) there?

[cbellone]

Hi @jacotec ,

thank you for evaluating alf.io!

can't find the backend language setting for the "event creators". This form is always shown in English and we have a lot of (older) people in local organizations who would need to create events but who don't speak a word English. The "frontend" works in German.

the current version of the backoffice is only available in English. We are starting to work on the new backoffice which will bring a more modern UI and will be available in multiple languages.

I can't see a setting to allow events without tickets. Apart from events which would benefit from a ticket booking there are also events where people just can "pop up" which should also be in the calendar

Alf.io is a ticket reservation system for conferences, trade shows, workshops, meetups. It is focused on these use cases. The concept of "Ticket" is at the core of our system, so we don't support events without tickets. At least not for now.

I can't see the ability to make the fields "Terms and Conditions URL" and "Website URL" of an event optional. These are not required for my use case.

These are mandatory fields for the supported use cases. For example, we need them to write in the auditing log what URLs (T&C, Privacy Policy) a person has accepted and when.