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
Extend characters in cart ticket descriptions... | Event Espresso - Staging Server

Support

Home Forums Pre-Releases Extend characters in cart ticket descriptions…

Extend characters in cart ticket descriptions…

Posted: October 10, 2013 at 7:20 am

Viewing 3 reply threads


Robert White

October 10, 2013 at 7:20 am

Currently the character limit is too small to allow a full description of the ticket type in the multi=event cart view. I have looked for threads but the only reference made is to a change in the database to the event titles rather than ticket descriptions. Can I have the name of the table to edit please?

Secondly, I’d like to to give the ‘View Cart’ and ‘buy tickets’ shortcode link display text more of a button appearance. Which css do I need to change?

Many thanks.


Anonymous

October 10, 2013 at 10:55 am

I would advise against altering the database as this is not something we support.

Having said that the database table to edit is wp_events_price.
The field to edit it price_type.

It is currently a varchar(50), to double the length you would change this to varchar(100) through phpmyadmin.

For the cart buttons you need to add the css to your themes style.css file.

We have a video available here http://staging.eventespresso.com/wiki/using-css3-to-style-links/

You could also use an image following here http://staging.eventespresso.com/wiki/multiple-events-registration-use-add-to-cart-link-instead-of-default-registration-form/#customizing


Robert White

October 11, 2013 at 7:34 am

Many thanks for your response however that hasn’t altered the titles of the ticket lengths.:http://www.salsadance.co.uk/event-registration/?regevent_action=show_shopping_cart as you can see the tiles of the ‘ticket’ types is being cut off despite the change to the database character lengths?

Can you advise?


Anonymous

October 11, 2013 at 8:00 am

Although you have modified the DB, the tickets will have saved with the character limit active, so they still only have a max of 50 chars. You will need to go to the events and add more to the ticket description which will then be allowed to save to the DB as the limit is now higher.

You are also using an older version of Event Espresso (3.1.34) and as such I would advise you to update, although I would recommend backing up first.

Please be aware after you update the limit may once again be reset depending on what the update is doing (one of the reasons it is not recommended) it wouldn’t be regular, but something to be aware of.

Viewing 3 reply threads

The support post ‘Extend characters in cart ticket descriptions…’ 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.

Home to preview versions of next-generation Event Espresso products.

Status: closed

Updated by Anonymous 11 years, 3 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server