[Barry]

Hoping you’re all sorted here and will go ahead and close this thread. If we can help with anything else please don’t hesitate to create a new thread – thanks!

[Barry]

I’ll go ahead and close this thread but if you have any further questions or need assistance with anything else please don’t hesitate to get in touch. Thanks!

[Barry]

Since there’s been no follow up I’m hoping you got to the bottom of this issue, but if you do need further assistance please don’t hesitate to create a new thread. Thanks!

[Barry]

It’s been a while so I’m guessing you’re all good here – but of course if we can assist with anything else please don’t hesitate to open a new thread. Thanks!

[Barry]

Hi Thomas:

Sorry for any confusion here.

We’re currently in the process of revising our structured data implementation (the “hidden” fields that some search engines and other services look for) as it did indeed recently come to light that some further work could be done to improve things in this regard.

That said, if I use a structured data testing tool to inspect the URL you shared – although some shortcomings are certainly apparent – there is at the same time a good amount of event related data that is successfully being read.

In summary then, yes, we definitely need to make further improvements and have a plan in place to do so, but at the same time your event-related pages are not completely devoid of structured data. I’m also sorry that the previous thread you linked to perhaps came across as a little misleading – that’s not our intention of course – but it’s worth bearing in mind that things change quickly and old replies from 2012 or earlier (which relate to a very different iteration of the plugin) probably are not too reliable a guide to rely on.

Does that clarify things at all?

[Barry]

Hi!

Thanks for getting in touch – it’s always great to see people doing interesting things with our plugins 🙂

Please remember that while we periodically make snippets and tutorials available it is often the case that they are intended to serve as blueprints for your own onward development rather than complete solutions and, indeed, something as specific as you are asking about isn’t generally something we can assist with.

And staying with that code for a moment, we haven’t been able to get it to work. Here’s what we inserted in the functions.php file:

…

‘organizer[Organizer]’,
‘organizer[Email]’

I’m not sure that Casey’s tutorial suggests you can specifically target specific indices of an array in that manner so you might need to take a different tack there.

This returns the error message. Unfortunately, it returns the error message even when we do complete the Organizer Name and Email fields. Alas. Maybe you can spot what we’ve got wrong.

So again it’s really a blueprint demonstrating how to add an error message to that view – so if you use it verbatim then, yes, it’s going to display the same message constantly. This is something where you would need to devise your own logic to control if an error message is displayed and what it should actually contain.

Does that clarify things and is there anything you feel we could add to the tutorial to make aspects like this clearer?

[Barry]

Hi Tony,

Thanks for getting in touch – we do indeed support tags in our current releases.

Does that answer your question?

[Barry]

Hi – great question!

Some themes let you add custom CSS or alternatively you could follow the steps prescribed in the Themer’s Guide to set up a tribe-events.css stylesheet – though this would load before events-admin.css you could use suitably specific rules to change the font sizes even so, such as:

#page .eventForm h4 { font-size: 3em; }

I tested the above out locally, but in the case of your theme you might change that to:

#wrapper .eventForm h4 { font-size: 3em; }

Does that help at all?

[Barry]

Hi Tobias,

If you want to get to know the meta walker/meta factory (which handles those elements) please refer to this handy tutorial:

How the Tribe Meta Factory works

Playing with this probably counts as a fairly advanced level customizing, however, so you’d ideally have a fair level of WordPress and general development knowledge, and some time to spare, to investigate this.

A straightforward alternative could be to “kill” that section (which is pulled in by the tribe_events_single_event_meta() call in the single-event.php template) and essentially replace it with a set of simpler calls which you could structure just how you want it to be.

Do either of those ideas help?

[Barry]

Hi – great questions!

1) can the tickets produced for events appear in the shop along with all the other wc products?

They certainly can. When you edit the tickets from within the event editor you should see a link offering to take you to the WooCommerce product editor. This lets you edit the tickets as if they were regular products … which of course they are. Look out for a Catalog Visibility setting – changing this from hidden to visible ought to achieve what you want here.

2) 404 error for single even page.

That’s unfortunate, but is probably a quite separate problem from the first issue. Let’s deal with this second point here – I would ask though that if you have any further questions relating to point (1) that you place them in a new thread, as we try to stick to a policy of one issue-per-forum-thread.

Though I see you already tried some basic troubleshooting steps I just want to lay out the following plan:

• Please deactivate all other plugins except for The Events Calendar, WooCommerce Tickets and WooCommerce
• Ensure they are all up-to-date
• Switch to a default, unmodified theme
• Visit Settings → Permalinks … you don’t need to change anything though, visiting this admin screen is sufficient to refresh a database entry known as the rewrite_rules

Are the single event pages visible now?

 

[Barry]

The approach with setting a global in the outer template and detecting it from the inner template certainly ought to work.

The reason tribe_is_event_venue() only works in the outer template (single-venue.php) is essentially because it inspects the global $wp_query object, however this is modified before the inner template (list/content.php) runs.

Can you share the code – perahps via Pastebin or Gist – that you tried when tackling this with the global variable approach? I see no reason why that wouldn’t work … perhaps the global just wasn’t pulled into scope within the inner template?

[Barry]

So you’ve mentioned two different websites there – I’m not 100% sure which I should be looking at. However I do note that the calendar widget displaying at cafehackersp.org is the WordPress (posts) calendar widget which relates to the dates posts were published (and do indeed see an entry for 12 February) rather than events, for which you should use the Event Calendar widget.

Does that help at all?

[Barry]

Hi!

I’m afraid this is a current limitation of the plugin (though one we hope to address in the future). Until that happens, can you try adding this short snippet to your theme’s functions.php file and see if that allows you to use shortcodes from within those fields?

Thanks!

[Barry]

Great question.

There’s no best practice as such – a workaround could be as simple as assigning the tentative date and pasting some text within the event description to the effect that the actual event date is still to be determined.

You could go a step further and use an additional field to flag the same information and from their make a small customization to hide the date and replace it with some other message – which could provide more convenience and consistency.

Does that help at all?

[Barry]

Hi, I’m sorry to hear that.

Does this problem only occur when WPML is in use? The fact is that, at this time, we can provide any support for issues arising from the use of WPML (though we hope to look at avenues to improve things in this regard at some future point).

[Author]

Posts