[Cliff]

Thanks for this detailed information. I reported the issue in our internal bug tracker.

I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

I apologize for this issue and appreciate your understanding and patience.

[Cliff]

Kevin, I checked with one of our developers and apparently the code snippet in that KB article is only filtering gettext and not ngettext. I have asked that this KB article’s snippet be updated for this.

In the meantime, you could try filtering ngettext yourself or you might try a plugin like Say What?

Let me know if you get further along with this or if you still need help.

[Cliff]

Amy/Lindy,

I apologize for my incorrect initial reply. I logged this as a bug and marked this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

I apologize for this issue and appreciate your understanding and patience.

[Cliff]

Thanks for your understanding and your business, Math.

Have a great rest of your week!

[Cliff]

To be clear, I suggested using wp_update_post() as a workaround, but I reported that as another (third) bug based on this forum thread.

Thanks again for bringing up these issues.

[Cliff]

Lindy/Amy, thanks for asking.

I will double-check about the purpose of “add another rule” to make sure I provided you accurate information.

In our forums we keep our threads focused on just one issue at a time to ensure we fully answer each of your questions/issues. Please start a new thread for your additional questions. Thanks for your understanding.

[Cliff]

Mike, thanks for that update. Could you please provide a screenshot of what “author style” setting you’re referring to? I’m guessing it’s not part of our plugin’s settings (maybe your theme’s?) and temporarily switching to a default theme like Twenty Sixteen should work just fine.

Let me know what you find out.

[Cliff]

Hi Oliver.

Thanks for bringing the incorrect documentation to our attention again. I didn’t see the bug logged internally so I logged it, and I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

As it is now (until fixed), it returns either the Venue ID (integer) or void/null. It does not return false.

Regarding duplicating data, yes this likely for backwards compatibility / legacy reasons, but I have added another internal item to review this.

Regarding the Venue title, tribe_update_venue() only updates the Venue’s metadata (i.e. custom fields). You could use wp_update_post() to update the post_title for the Tribe__Events__Venue::POSTTYPE post type (default is tribe_venue).

I hope this information helps you progress with your implementation, and thanks again for sharing your feedback.

[Cliff]

Hi. Sorry you’re not having a smooth experience with this feature.

There might be some new updates available. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

• Downloads / Version Numbers
• TEC Automatic Updates
• or TEC Manual Updates
• WordPress core updates

Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.

If it is, please follow our Testing for Conflicts Guide (basically switch to TwentySixteen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG and share any PHP errors you see while changing tickets quantity, navigating your site’s home page, events page, single-event pages, and any other of your site’s pages relevant to this ticket.

Then, please share your System Information (while in Testing for Conflicts mode).

You might also see if you can spot any console errors at your site. (If needed, you may reference our KB article Using Google Chrome Developer Tools.)

Finally, to answer your question about where the ticket fieldset information is stored: they’re actually their own custom post type — ticket-meta-fieldset

Let us know what you find out with your testing.

Thanks.

[Cliff]

Amy, no this functionality currently isn’t possible. You should create the 2 time slots as 2 separate recurrence series. Sorry for this limitation.

You could request this as a new feature (or maybe search to see if the idea was already posted by someone else) at our plugins’ UserVoice page.

This allows others who are interested in that feature to easily voice their support. We frequently review suggestions there to find out which ones are popular, then we implement as many of them as we can.

If you post it / find it, feel free to link to it from here in case anyone comes across this forum thread in the future.

[Cliff]

Hi Stephanie. I think this plugin will work for your purposes — then just add a Text Widget or whatever you want to the new widget area(s) as you need.

Please let me know if you have any follow-up questions on this topic.

[Cliff]

Hi Kevin. Thanks for your detailed question.

I believe you’re referring to this line of code: https://github.com/moderntribe/event-tickets/blob/4.2.7/src/views/tickets/orders-link.php#L37

Please reference that line of code and this KB article (I believe you’ll need to enter %d Ticket and %d Tickets separately) and let me know if you have any follow-up questions.

[Cliff]

Daniel, I didn’t quite grasp your situation fully, but if things are working okay for you now, I’m glad to hear that. If they’re not, please open a new thread if needed in the future.

Thanks!

[Cliff]

Hi Michael.

Comments must be enabled at wp-admin > Events > Settings > General tab > “Show comments” option. Maybe you had that checked before but it got unchecked?

I’d also suggest making sure comments on your blog posts and elsewhere on your site are working as expected. If they are (and if Events comments is still checked), you might want to try playing with this setting: wp-admin > Events > Settings > Display tab > “Events template” option to see if changing it makes things work better for you.

Please let me know how things go for you.

[Cliff]

Thanks for all the info. Here’s the response from one of our developers:

You could temporarily include the following code:

function tribe_snippet_pro_requeue_scripts() {
wp_dequeue_script( 'handlebars' );
wp_dequeue_script( 'moment' );
wp_deregister_script( 'handlebars' );
wp_deregister_script( 'moment' );

wp_enqueue_script( 'handlebars', Tribe__Events__Pro__Main::instance()->pluginUrl . 'vendor/handlebars/handlebars.min.js', array(), apply_filters( 'tribe_events_pro_js_version', Tribe__Events__Pro__Main::VERSION ), true );
wp_enqueue_script( 'moment', Tribe__Events__Pro__Main::instance()->pluginUrl . 'vendor/momentjs/moment.min.js', array(), apply_filters( 'tribe_events_pro_js_version', Tribe__Events__Pro__Main::VERSION ), true );
}

add_action( 'tribe_events_enqueue', 'tribe_snippet_pro_requeue_scripts', 11 );
add_action( 'tribe_venues_enqueue', 'tribe_snippet_pro_requeue_scripts', 11 );

But they’ll also make sure to fix it in an upcoming release. I think it should be released really soon.

Please let me know if you have any follow-up questions on this topic.

[Author]

Posts