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
Event ID broken by special characters | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Event ID broken by special characters

Event ID broken by special characters

Posted: December 6, 2013 at 3:07 pm

Viewing 6 reply threads


Stian Morsund

December 6, 2013 at 3:07 pm

Hi, I have made a lot of courses with titles containing Norwegian characters (æ,ø,å). As a consequence of this, my event ID’s gets messed up and events can’t be called with the [SINGLEEVENT]-shortcode. For instance: “å” is displayed as: “%c3%a”.

Is there an easy way to edit the ID’s without messing with the database tables/resubmitting all the events?

May I add that ALL of my event titles contain special characters (only “æ”, “ø”, “å” though), and since there are a lot of them, I hope there is a workaround for this so I don’t have to submit all my events from scratch.. :)

Thank you!


Stian Morsund

December 6, 2013 at 3:34 pm

Update:

I am building a conditional event-displayer with Gravity Forms.
Using the shortcode inside GF’s html block gives me a message saying the event is expired or no longer available. When I’m using the shortcode on a regular page it says that the event has reached the maximum number of attendees, allthough there are zero attendees.

Could this be related to the event id or is it likely to be something else?


Stian Morsund

December 6, 2013 at 3:38 pm

Update 2:

I tried making a new event without the special characters in the title, which works, so it’s got to be the event ID messing things up..


Josh

December 6, 2013 at 4:22 pm

Hi there,

We have an alternative shortcode that you can use instead of SINGLEEVENT that uses the numeric event ID instead that you can try:

http://staging.eventespresso.com/wiki/shortcodes-template-variables/#reg-page

Not sure what might be causing the Gravity Forms issue though. It may be that there is an issue with the shortcode being parsed within another shortcode.


Stian Morsund

December 7, 2013 at 1:52 pm

Thank you, Josh, I didn’t notice that.
I do have to use a link to the registration page anyway, because a form inside of a form (Gravity Form) is, off course, not valid HTML


Josh

December 9, 2013 at 8:50 am

You’re welcome. That’s a good idea to place a link to the reg form inside the other form. Here is another idea that might work for your use case too:

http://zackeryfretty.com/posts/creating-conditional-redirects-or-conditional-confirmation-messages-with-gravity-forms


Stian Morsund

December 10, 2013 at 1:42 am

Thank you, Josh! I actually thought of implementing automatic redirection myself. Didn’t know GF could do it that easy though, I was thinking of using Javascript..

I’ll mark this one as resolved :)

Viewing 6 reply threads

The support post ‘Event ID broken by special characters’ 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