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
Custom Table Filtering | Event Espresso - Staging Server

Support

Home Forums Custom Files Custom Table Filtering

Custom Table Filtering

Posted: September 27, 2012 at 2:12 am

Viewing 10 reply threads


islesser

September 27, 2012 at 2:12 am

Hi im currently using the custom table additional code and currently it wont filter out the expired events or by category

[ESPRESSO_TABLE show_expired=”false” category_id=”coventry”]

is an example of my shortcode

Thanks


Dean

  • Support Staff

September 27, 2012 at 3:39 am

Hello,

I will ask a dev to look at this, I can’t see any reason why it isn’t working.

If the event has ended, it removes it from the list as normal. Just not if registration only has ended.

  • This reply was modified 12 years, 3 months ago by Dean. Reason: added info


islesser

September 27, 2012 at 7:55 am

is there a way to sort it so it doesnt show evens whose registration hasnt started yet, or has ended, like with the calender version>


Dean

  • Support Staff

September 28, 2012 at 2:20 am

[ESPRESSO_TABLE show_expired="false"] 

Should do the trick


islesser

October 4, 2012 at 3:55 pm

im already using that as shown in my initial post, but its not working


Josh

October 4, 2012 at 4:04 pm

Can you try:

[ESPRESSO_TABLE show_expired="false" category_identifier="coventry"]

Also, be sure to verify that the actual category identifier is coventry. Event Espresso will by default append a randomly generated numeric string to the end of the Unique Category Identifier. This can be overridden by entering your own Unique Category Identifier in the edit category screen.


islesser

October 4, 2012 at 4:53 pm

that now displays only the events for coventry but events for all time, so the show_expired section appears not to be working


Dean

  • Support Staff

October 5, 2012 at 2:31 am

Hello

OK, I have done some extensive testing on this. I think that the problem lies in an issue with the category aspect rather than the expired. This has been resolved in 3.1.27.P

screenshot note the categories table being empty is correct as there was no active events under the category I chose and they appear when expired is set to true.

Also note that the category_id from .26 is now category_identifier in .27


islesser

October 12, 2012 at 8:37 am

Ive updated to the newest version of event espresso and it still is showing events that you are unable to register for

http://www.rm-test.co.uk/derek/birmingham/

is an example


Dean

  • Support Staff

October 14, 2012 at 11:22 pm

Hi,

Looking at this again, it seems I have been focusing on the expired rather than future registrations.

There is currently no mechanism built in to stop future registrations which arent yet open from being displayed. You would need to edit the shortcode’s code or implement some conditional logic in the template file to achieve this.


Dean

  • Support Staff

October 15, 2012 at 4:31 am

Further to this, there is a mechanism that may help you, the attribute max_days

[ESPRESSO_TABLE max_days=”30″ category_identifier=”coventry” show_expired=”false”]

It will only show events up to X days in the future (example is 30 days). This doesnt fully do what you want in terms of hiding all events where registration isnt open but it might be something you could use

Viewing 10 reply threads

The support post ‘Custom Table Filtering’ 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.

Event Espresso - Staging Server