[Cliff]

Hi Chris. Glad to hear you like it so far.

Please note that your /events page is really a WordPress archive, not a regular WordPress ‘page’.

You could accomplish what you’re wanting via CSS, like this:

body.post-type-archive-tribe_events section.page-title-bar {
display: none;
}
body.post-type-archive-tribe_events .post-wrap {
padding-top: 20px;
}

You can add custom CSS code via your child theme’s style.css file or via a plugin like Simple Custom CSS or, my favorite, Jetpack. Jetpack supports regular CSS and the LESS and Sass pre-processors.

If you’re not a CSS expert, Jetpack’s Custom Design reference may prove helpful.

Please let me know how it goes for you.

[Cliff]

Hi Martin. Thanks for the detailed question.

Please follow our Testing for Conflicts Guide on your staging site and see if that helps narrow down the cause of this.

I see from your screenshot that you’re using the now-defunct Event Rocket plugin.

I suggest you start by deactivating that one and see if things work for you at your-staging-site/events

Let us know what you find out.

Thanks.

[Cliff]

Hi Michelle.

Our core/free plugin includes a CSV importer but no built-in exporter.

However, Events, Organizers, and Venues are 3 separate post types and should work just fine with WordPress’ built-in wp-admin > Tools > Export functionality.

General advice is to activate all the same plugins and active theme on your new site and then run the wp-admin > Tools > Import > WordPress tool.

I hope this helps. It usually goes very quickly.

Please let me know 🙂

[Cliff]

Hi Ted.

It looks like that’s an error message with our WooTickets legacy plugin.

While we are committed to solving such fatal errors for our legacy products for several more months, one solution would be to migrate to the product that replaced WooTickets: Event Tickets Plus.

Will that work for you?

If yes, please check out our migration article and get Event Tickets Plus from your Downloads and License Keys pages.

===

If you need to stick with WooTickets legacy plugin for now, would you mind grabbing your system information and pasting it here? Make sure to use the “Set as private reply” checkbox to protect your private information from the public.

You can find the system info by going to WP Admin > Events > Settings > Help tab > System Information section

That will give me extra information to help diagnose the problem.

[Cliff]

Hi Yan. Thanks for your detailed question.

The lat/long are custom fields for the Venues post type, not the Events post type.

That’s just the way the plugin works.

Please visit our plugins’ UserVoice page to vote for (if you find an existing one) or add your feature request there.

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.

Once you find a link or post a new idea, feel free to link to it from here in case anyone comes across this forum thread in the future.

[Cliff]

Hi. Cliff chiming in here…

If I understood the latest replies, your WordPress timezone is set to UTC-6 for Houston, TX, but your events still aren’t being set to the right times, correct?

Houston follows Central Time so please try “Chicago” timezone setting. I believe I’ve seen where the “UTC…” choices don’t work but the city choices do work. Added benefit is that you don’t need to edit your timezone setting twice each year when Daylight Savings Time changes the UTC offset.

Please let us know what you find out changing to “Chicago” so we can log it as a bug if you confirm it.

Thanks!

[Cliff]

I have logged the request with our developers and mentioned your thread and another one that I fielded on the same topic.

Thanks for your feedback.

[Cliff]

I have logged the request with our developers and mentioned your thread and another one that I fielded on the same topic.

Thanks for your feedback.

[Cliff]

Excellent. Glad that was it! 🙂

[Cliff]

Hi. The Event Add/Edit screen PDF helped.

Check out this screenshot:

 

That “March 1, 2016 events” is probably being interpreted by the plugin as “12,016 events” or something like that. That field should be a “count of events” field, not a “date deadline” field.

Please revise that field to be something like “10 events” and let us know if that results in what we’d expect it to.

I’ve logged this as a bug to improve this field to be more user-friendly.

Thanks!

[Cliff]

Sorry about the UTC vs named timezone issue. Will that be an acceptable timezone for you to use permanently?

There’s not a way to easily “fix” those events that aren’t set right.

For events imported/created via iCal Importer, when you delete them, they’re not really deleted and therefore the duplicate-checker built into the iCal Importer detects them as previously imported and doesn’t re-import them.

[Cliff]

Sorry for the delayed response. I’m not sure what else to suggest. Many people use several Toolset plugins with our plugins.

Please provide a screencast video of what you’re experiencing.

If you’d like, you can provide us with a database dump too.

Thank you.

[Cliff]

I have been informed by a developer that our plugin switched from microformats to JSON-LD since v4.0.

I verified your site acts the same as my local testing site:

• archive views (e.g. Event List Widget and main /events link) do not output JSON-LD data
• single events do output JSON-LD data (View Source and find ‘ld+json’ in the page)

You can learn more about JSON-LD at https://developers.google.com/schemas/formats/json-ld

Please test a few of your single event pages in Google’s testing tool and then feel free to let me know your thoughts on this change.

Thank you.

[Cliff]

I have been informed by a developer that our plugin switched from microformats to JSON-LD since v4.0.

I verified your 5.k3.de site acts the same as my local testing site:

• archive views (e.g. Event List Widget and main /events link) do not output JSON-LD data
• single events do output JSON-LD data (View Source and find ‘ld+json’ in the page)

You can learn more about JSON-LD at https://developers.google.com/schemas/formats/json-ld

Please test a few of your single event pages in Google’s testing tool and then feel free to let me know your thoughts on this change.

Thank you.

[Cliff]

I saw you marked my answer as “correct”. I’m glad it solved your issue. I’m going to close this ticket. Feel free to open a new ticket if you have any other questions come up. Have a great day!

[Author]

Posts