Request to change the event view template (Calendar)

[Adriano Faria]

@Rikki

In the view template:

		{{if $event->rsvp || $address || $event->map( 270, 270 ) }}
			<div class='ipsColumns ipsColumns_collapsePhone'>
				<aside class='ipsColumn ipsColumn_wide'>
					<div>
						{template="eventSidebar" group="view" params="$event, $attendees, 'Mob', $address"}
					</div>
				</aside>
				<div class='ipsColumn ipsColumn_fluid'>
		{{endif}}

Happens that the same conditions are also checked in the eventSidebar template:

{{if $address || $event->map( 250, 150 )}}

and

{{if $event->rsvp }}

So it won't have any issue if you remove the condition from the view template. Leaving it as the way it is today, it prevents to add something in the eventSidebar, unless the event has an address/map or is RSVPed, which can't be required/necessary in all events.

Thank you.

[Chris Anderson]

You could require an address in order to make an event paid as a work-around if I understand you correctly. 

A board admin could create a venue calendar entry in the ACP for locations that are to be determined (Using the state in which the event will be located or board owner's state to fulfill the requirement that some value is shown for event address) or being hosted online as shown below:

Or they could create an actual venue location if they want to advertise it ahead of the event.  

"If" IPS ever gets around to making the change you requested then you can advise app purchasers that locations are optional going forward.

[Adriano Faria]

Nope. It doesn’t make sense. Online events has no address and much less RSVP (if you’re paying, you’ll participate, so why RSVP?).

It’s just a matter of removing a couple of lines in a template that has absolutely no use since it is called again in the other template.

[Adriano Faria]

On 3/17/2022 at 4:13 PM, Adriano Faria said:

@Rikki

In the view template:

		{{if $event->rsvp || $address || $event->map( 270, 270 ) }}
			<div class='ipsColumns ipsColumns_collapsePhone'>
				<aside class='ipsColumn ipsColumn_wide'>
					<div>
						{template="eventSidebar" group="view" params="$event, $attendees, 'Mob', $address"}
					</div>
				</aside>
				<div class='ipsColumn ipsColumn_fluid'>
		{{endif}}

Happens that the same conditions are also checked in the eventSidebar template:

{{if $address || $event->map( 250, 150 )}}

and

{{if $event->rsvp }}

So it won't have any issue if you remove the condition from the view template. Leaving it as the way it is today, it prevents to add something in the eventSidebar, unless the event has an address/map or is RSVPed, which can't be required/necessary in all events.

Thank you.

@Rikki @Matt