Skip to content

Commit

Permalink
fix: list front page restriction in frontpage tab (#5598)
Browse files Browse the repository at this point in the history
  • Loading branch information
@maze-runnar
maze-runnar authored Nov 18, 2020
1 parent d2ae456 commit 9372e34
Show file tree
Hide file tree
Showing 3 changed files with 116 additions and 0 deletions.
1 change: 1 addition & 0 deletions app/router.js
View file
Original file line number Diff line number Diff line change
Expand Up @@ -206,6 +206,7 @@ Router.map(function() {
this.route('payment-gateway');
this.route('ticket-fees');
this.route('billing');
this.route('frontpage');
});
this.route('content', function() {
this.route('social-links');
Expand Down
3 changes: 3 additions & 0 deletions app/templates/admin/settings.hbs
View file
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,9 @@
<LinkTo @route="admin.settings.billing" class="item">
{{t 'Billing'}}
</LinkTo>
<LinkTo @route="admin.settings.frontpage" class="item">
{{t 'Front Page'}}
</LinkTo>
</TabbedNavigation>
</div>
</div>
Expand Down
112 changes: 112 additions & 0 deletions app/templates/admin/settings/frontpage.hbs
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,112 @@
<table class="ui celled padded table">
<thead>
<tr>
<th class="single line"><h3>Featured Events</h3></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<i class="check icon green"></i> {{ t 'Any event that is switched to Featured Event by admins is listed here.' }}
</td>
</tr>
</tbody>
</table>
<table class="ui celled padded table">
<thead>
<tr>
<th class="single line"><h3>Upcoming Events</h3></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<i class="check icon green"></i> {{ t 'up to 21 events should be listed here.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'admins have the option to move any event without restrictions to the top of this line by switching events to Promoted Events in the event admin panel' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'promoted events should always show up on the top of Upcoming Events' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'The event should have location or online link and a date' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'The event should have Tickets.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'Do not show an event on start page if it does not have any public ticket.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'If the sales time of the ticket is passed then event should not show on the start page.' }}
</td>
</tr>
<tr>
<td>
<i class="close icon red"></i> {{ t 'Do not show an event on start page if it all tickets are sold or only hidden ticket remain.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'The event should have an Image.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'The event should have an logo.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'The event should have an Event Topic.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'The event should have an Event Sub Topic.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'The event should have a twitter link.' }}
</td>
</tr>
</tbody>
</table>
<table class="ui celled padded table">
<thead>
<tr>
<th class="single line"><h3>Call for Speakers</h3></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<i class="check icon green"></i> {{ t 'Up to 12 events would be listed here and there is a more link below to show more events on the cfs page if there are more events.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'Events listed here have a Call For Speaker.' }}
</td>
</tr>
<tr>
<td>
<i class="check icon green"></i> {{ t 'Requirements of Upcoming Events.' }}
</td>
</tr>
</tbody>
</table>

1 comment on commit 9372e34

@vercel
Copy link

@vercel vercel bot commented on 9372e34 Nov 18, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Successfully deployed to the following URLs:

Please sign in to comment.