Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
New date added to recurring events appear out of chronological order | Event Espresso - Staging Server

Support

Home › Forums › Recurring Events Manager › New date added to recurring events appear out of chronological order

New date added to recurring events appear out of chronological order

Posted: March 28, 2014 at 3:00 pm

Viewing 4 reply threads


smendes

March 28, 2014 at 3:00 pm

Hi,

I have several recurring events on my website. I’m using an events listing and ordering by date, using the shortcode: [EVENT_LIST category_identifier=category_name show_recurrence=true show_expired=false order_by=date(start_date),id]

When I add new dates to a recurring event, the new dates appear at the bottom of the list, instead of being inserted into chronological order.

For an example, see the “Infant/Child CPR and choking – emergency response training” event on this page: http://www.carmelblue.com/prenatal-signup/

This is a problem because many people won’t look to the bottom of the list to find upcoming dates.

Thanks for your help!
Sharone

WordPress 3.8.1
EE 3.1.36.4.P
Recurring Events 1.1.8.p


Anonymous

March 31, 2014 at 1:59 am

Hi,

With the current shortcode you are using you have:

order_by=date(start_date),id

Which basically says sort by start_date, then ID. As your ‘extra’ dates will have the highest ID’s they will be placed at the bottom.

Simply removing ‘,id’ from that attribute should correctly display the events listed by start_date.

Hope that helps.


smendes

March 31, 2014 at 2:25 pm

Hi Tony,

Thanks for your help. However, I made that change to the shortcode, then cleared the cache and it is still displaying in the same manner. Is there something else I can try.

Cheers
Sharone


Anonymous

April 3, 2014 at 3:35 am

Hi smendes,

I took a look through the code, by default ORDER_BY is set to use ‘e.recurrence_id, date(start_date)’ which basically groups the events in a series together, then orders those events by start_date.

By adding you own attribute ‘order_by=date(start_date)’ you override this and sort only by start_date.

If you remove the order_by attribute completely the events should be sorted by start_date correctly.


smendes

April 3, 2014 at 5:21 pm

Hi Tony,

Brilliant! That did the trick! Thank you so much for the help. I’ll mark this topic as resolved.

Thanks
Sharone
Viewing 4 reply threads

The support post ‘New date added to recurring events appear out of chronological order’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Status: closed

Updated by smendes 10 years, 9 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server