[David]

This reply is private.

[David]

This reply is private.

[David]

Hi Geoff,
the error message you noticed is present only in the staging environment. But in the dev environment, the problems with The Event Calendar are still present. It’s related to Bedrock / Trellis (https://roots.io/bedrock/ / https://roots.io/trellis/) setup that I’m using for this website. Months ago I had some problems with that and wpml, but after an update from their side all works fine, without the error message that you noticed.

Maybe the problem with the events calendar plugin is a compatibility problem with Roots setup? Could you check this please?

Thanks,
David

[David]

This reply is private.

[David]

This reply is private.

[David]

This reply is private.

[David]

This reply is private.

[David]

Hi Geoff, thank you for your answer!

Here you can find two screenshots of /wp-admin/admin.php?page=sitepress-multilingual-cms%2Fmenu%2Ftheme-localization.php page: https://tppr.me/woQRJ – https://tppr.me/mwHlE

I understand that the filter bar is not fully supported by WPML, but cases 1, 2 and 3 occur only when “the event calendar” and “the event calendar pro” are enabled.

Do you have any idea on how to solve this?

Thanks,
David

[David]

Hi Cliff,
Thank you for your answer!
I’m not really understanding how to change che id from string to integer and why the id should be an integer. Is this the cause of the warning?

Could you help me to understand how and where to intervene, please?

Thanks,
David

[David]

This reply is private.

[David]

This code shows the meta-box and loads the information of the organizer’s post type inside the filed, but when saving the page nothing is added to the custom fields list. If I change the ID “_EventOrganizerID” with something else, instead, the value is added.

<?php
add_filter( 'rwmb_meta_boxes', 'register_meta_boxes' );
function register_meta_boxes( $meta_boxes ) {

$meta_boxes[] = array(
            'id'         => 'events_roles',
            'title'      => __( 'Roles', 'uplift' ),
            'post_types' => array( 'tribe_events'),
            'context'    => 'normal',
            'priority'   => 'high',
            'autosave'   => true,
            'fields' => array(
                array (
                    'name'        => esc_html__( 'Organizer(s)', 'uplift' ),
                    'id'          => "_EventOrganizerID", //ID defined by tribe_events
                    'type' => 'post',
                    'post_type' => 'tribe_organizer',
                    'field_type' => 'select_advanced',
                    'multiple'    => true,
                    'query_args' => array('post_status' => 'publish',),
                    'placeholder' => esc_html__( 'Select Organizer(s)', 'uplift' ),
                ),
          )
     );
    return $meta_boxes;
}

reference: https://metabox.io/docs/registering-meta-boxes/

[David]

Hi Cliff, thanks for your information!

Regarding point 1, I need to organize the event creation in the backend in different meta-boxes in a way that it makes clear that all information about one thing (like Organizer) is all grouped in the same place (so, an “Organizer” meta-box that contains both your default fields and new custom ones).
To do this, I deleted the Venue and Organizer default fields from events-meta-box.php and created new meta-boxes using metabox.io.

The problem is this: when, in the new meta-box, I use _EventOrganizerID or _EventVenueID to save the custom field, it doesn’t save (or add) it. But, if I change the ID, everything works fine and the custom field is saved.
So, I immagine that there is a hook somewhere in the plugin that prevents the custom field to be saved with _EventOrganizerID or _EventVenueID outside your meta-box. What can I do to solve this problem?

Thank you!!

[Author]

Posts