Attachments yes, attachments no..

Hi guys. Simple question. If i don't want to show attachments section in submit event/venue pages, how should I do? I want to have the possibility to choose whether to disable it, make it optional or mandatory, as is the case for the "upload image" in backend of JEM.
Tank U

@pajaura,.


Actually it can be done very easy but it will require some additional code to do it. It are good points but so think it will be integrated.

What can be done is to add the two parameters (image yes/no, attachment yes/no) to the view. So when you make the menu-link to the submit view you can decide what to do.

The above is part 1 but adding the param is not enough so you have to add a switch like $params->get('disableimage') within the default page.

//

If you know a bit about php i could give an example how to do it.
--> will add the changes also to github when finished

are there more things you would like to hide?.
perhaps custom fields or the second tab in general.

Thanks for the reply Bluefox. I do not think there's something to hide too. Custom fields remain invisible if left blank (in this regard there is a problem "aesthetic": it would be nice to be able to change the titles of the custom fields as being "Custom Field 1: text text text" after the category line isn't the best style..). Reservations, waiting list and recurring events are already optional in the backend, so are fine. For my part i think the only thing to make optional is attachments field.

it would be nice to be able to change the titles of the custom fields as being "Custom Field 1: text text text" after the category line isn't the best style..).

You're right, it would be nice if you could define your text directly in there and maybe some other options for the boxes.

What i mean is that if you want to make something an url you can select that option and the output will be an url, or if it's a value in currency then it will add the currency sign before the output. And text will be simply text..
--> aldo those things are possible to add it will be something for Christmas time

"Custom field x" has to be translated with a custom translation. This has to be made more clear in the component.