Support

July 3, 2013 at 5:33 am

That will be available in 4.0 onwards as standard. You could use the Custom Post type system built into 3.1.X to display events. https://eventespresso.com/wiki/custom-post-types-basic-setup/

July 3, 2013 at 6:07 am

Hi,

The basic usage is to create or edit an event and at the bottom make sure “Add/Update post for this event?” is set to yes and the post type is Events.

This will create a duplicate of the event but as a custom post type.

Then create a page and give it the Espresso Events template. Now when you go to that page it will list the custom post types.

As mentioned 4.0 will work with custom post types by default.

July 3, 2013 at 6:42 am

Sorry, I misunderstood. Did you refresh your permalinks? (Go to Permalinks and just save)

July 3, 2013 at 7:14 am

If you have the single-espresso_event.php file in your theme folder it should show the registration form, unless you have hidden that form in the event itself (they are linked).

July 5, 2013 at 8:46 am

Hi Noomia,

I can’t say for 100% that this will work because I do not have a copy of WPML to test, but you can make the labels run through gettext by changing line 34 of event-espresso/includes/funcitons/form-build.php to read like this:

$label = '<label for="' . $XATT1 . $field_name . $XATT2 . '" class="' . $class . '">' . trim( stripslashes( str_replace( '&#039;', "'", __($question->question) ))) . $required_label . '</label> ';

basically what the above is doing is changing $question->question to __($question->question)

Then you can copy the entire function to /wp-content/uploads/espresso/custom_functions.php to keep it from getting overwritten on an update. See https://eventespresso.com/wiki/custom-files-addon/ for more info on the custom files add-on.

Then you should be able to use WPML’s String Translation feature to translate the labels on the registration form:

http://wpml.org/documentation/getting-started-guide/string-translation/

July 10, 2013 at 8:05 am

Can you outline what was tried here? The code that I posted was tested to work with the gettext filter. So what I did to test it was run a function like this:

function mycustom_filter_gettext( $translated, $original, $domain ) {
 
    // This is an array of original strings
    // and what they should be replaced with
    $strings = array(
    	'First Name' => 'Blammo',
        // Add some more strings here
    );
 
    // See if the current string is in the $strings array
    // If so, replace it's translation
    if ( isset( $strings[$original] ) ) {
        // This accomplishes the same thing as __()
        // but without running it through the filter again
        $translations = &get_translations_for_domain( $domain );
        $translated = $translations->translate( $strings[$original] );
    }
 
    return $translated;
}
 
add_filter( 'gettext', 'mycustom_filter_gettext', 10, 3 );

Which changed the “First Name” string to be “Blammo”. So if WPML uses gettext for its string translation feature it should be good to go.

July 10, 2013 at 9:07 am

Registration Details is in /templates/registration_page_display.php ~ line 201.