Liquid: Sort Webapp items by custom date

Question

I would like to be able to sort a list of web app items by a custom date. It is a list of events that have dates associated with them. They all get released on the same day, but they have unique event dates to each of them for when the event actually happens.
This is what I have so far:
{module_webapps render="collection" filter="classified" collection="warroadEvents" id="17654" itemId="122469" hideEmptyMessage="true" sortType="datereverse" template=""}
{% for event in warroadEvents.items %}
     {% assign todaysDate = globals.site.dateNow | date %}
     {% assign eventDate = event.['Event Date'] %}
     {% assign dateOrder = todaysDate | minus: myDate %}
     <div class="col-xxs buffer event-callout">
         <a href="{{event.url}}"><img src="{{event.['banner image']}}?Action=thumbnail&Width=825&Height=275" alt="{{event.name}}" class="img-responsive"></a>
         <a href="{{event.['e-split url']}}" target="_blank" class="ticket float-right" style="margin-top: 1.5em;">
             <img src="/_images/layout/buy tickets com.PNG" alt="" class="ticketimage">
         </a>
         <h2>{{event.name}}</h2>
         <p><strong>{{event.['Event Date'] | date:"dddd"}}, {{event.['Event Date'] | date:"MMMM d"}}: {{event.['Start Time']}}</strong></p>
         <h4><a href="{{event.url}}">View More Details</a></h4>
    </div>
{% endfor %}
I have created 3 variables. One that stores today's date, another that stores the event date from the web app item, and a third that subtracts the two to find the difference. I think I am part of the way there. I am not sure how to re-sort my for loop so that the date that is coming up soonest shows up first and so on.

Answer 1

Custom filter solutions are one of the big limitations with this stuff at the moment.
Basically you cant.
While you could wrap the items in an if..... And do date matching and comparing and not show them etc you will not be able to sort or order them based on that.
And with anything you do you can only do it in a scope of a total of 500 items or per pagination page. Per pagination page stuff creates an issue where it will show say 24 per page and lets say 3 on each page do not match you get 24 render pagination still but 21 shown on a page. It creates some funky results a bit.
I have been going on about this for a while now and that we need some core changes to Liquid to make it a bit more viable in the scope of how BC spits out data. For now though you cant do what your doing really.