Skip to content

Frontend sends is_ticketing_enabled=false even when ticketing is enabled #3664

@iamareebjamal

Description

@iamareebjamal

Same for is_map_shown.

When creating an event, if the user enters ticket information, is_ticketing_enabled is turned to true by frontend. This toggling is redundant as there is no switch for the admin to turn off ticketing per event on the event wizard. So, either add a toggle on frontend and map it to is_ticketing_enabled which allows the admin to toggle ticketing on or off. Or remove this parameter from the schema in the server and let server decide if it should be on or off.

Similarly, the case with is_map_shown. There is no toggle for it and frontend tries to be smart about it on event creation and sets it to true if location info is added. Please don't do implicit things when there is no control over the field. This field is redundant as well. If there is location info in the server, it means that the map is to be shown. So, either remove this field from the schema or add a toggle in event wizard to show or hide the map.
Edit: This toggle is present on the wizard but hidden until Enter Address is clicked on.

Programs hiding controls and trying to be smart about it are very annoying. Every controllable field should either be editable by a human, or should be decided by server and removed from schema and not be controllable by anyone. Frontend should not try to make decisions for the server or humans

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions