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
Espresso_table correction | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Espresso_table correction

Espresso_table correction

Posted: January 5, 2013 at 3:03 pm

Viewing 2 reply threads


John Clark

January 5, 2013 at 3:03 pm

Hi

I just wanted to point out a problem with the shortcode usage example contained in Espresso_table.php It reads

Usage Example: [ESPRESSO_TABLE max_days=”30″ qty=”3″ category_id=”gracecard” order_by=”state”]

This does not work. “category_id=” should be “category_identifier=” followed by the unique category identifier.
This was noted on these forums by a year or so ago by a couple of members of the dev team but it seems that they haven’t got around to updating the docs or php file.

cheers

John


John Clark

January 5, 2013 at 3:04 pm

Here’s the post that explains it

http://staging.eventespresso.com/forums/2011/05/custom-files-espresso_table-php/


Dean

  • Support Staff

    •

January 7, 2013 at 1:02 am

Hi John,

Thanks for pointing that out, not sure why it wasn’t fixed previously. I have raised a developer ticket it to get it fixed.
Viewing 2 reply threads

The support post ‘Espresso_table correction’ 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.

The original Forum description...

Status: closed

Updated by Dean 12 years ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server