[Barry]

OK, so it looks like things are breaking in some critical way when the <title> tag is created.

Would it be possible for you to temporarily turn on WP_DEBUG and see if on visiting an event category page you see any useful error messages? In this situation, it may be you need to use your browser’s view source option to see them.

Alternatively, if you are comfortable doing so, you may be able to find the error in your server’s error logs.

[Barry]

and template override means the additional field with do_shortcode() let event creator decide which product to add dynamicaly

If that’s a problem you could hardcode the product ID instead, then the event creator will not be able to change it.

I tried to use Advanced Custom Field but with no success until now.

I can see the field when creating a new event but displaying the page do not show additionnal field content.

Is there any conflict with ACF ?

Not that I’m aware of, but unless I’m mistaken I’d point out you need to do some customization work within your templates to actually expose any custom fields you set up using ACF – reading though the ACF documentation, particularly with regards to template tags like the_field() and get_the_field() is probably worthwhile here 🙂

[Barry]

OK – so, unfortunately, it would seem we’re hitting up against one of the problems I initially suspected:

It is also possible that they are refusing to supply geolocation data – and this can happen if you have exceeded the free quota, or, you are using a shared hosting package and other websites/apps running on the same machine have collectively done so.

Can you confirm if you are indeed on a shared hosting package?

If so, would it be possible to chat with your host and see if they can move you to a different server or even consider upgrading to something like a VPS package which would provide a better degree of isolation?

[Barry]

Sorry to hear that.

I think we need just a little more information: can you delete the test plugin, then download a fresh copy (it should show in your plugin admin screen as The Events Calendar: Test Geoloc Connectivity) and repeat the test?

This time if you could tell me what you see A) at the top of the plugin or any other admin screen and B) if you could visit the venue editor for this specific venue and tell me what you see there that would be appreciated.

What’s changed is that the plugin should now report the actual error/status code returned by Google, which could be useful.

Thanks again for your patience while we work through this 🙂

[Barry]

Awesome – happy to help 🙂

[Barry]

Hi oniregoc,

Might a template override allow you to accomplish this? You could then safely customize the ticket form (the template you’d be interested in is wootickets/tickets.php) and use do_shortcode() to add the desired product.

If you also make clever use of either WordPress’s own custom fields (or else Event Calendar PRO’s additional fields) you could set the actual product ID from the event editor.

Does that help at all?

[Barry]

Hi Martin,

I’m sorry you’re experiencing difficulties.

I haven’t actually heard of this specific problem, either, but visited the URL you provided and event categories appear to work correctly – is that because you have deactivated your SEO plugin – or has the problem been resolved some other way?

[Barry]

OK: that indicates that, for some reason, Google cannot determine or guess at the coordinates of the address it is being supplied with.

I’m not sure why that would be the case as it worked perfectly in my own local test, but one thing that does come to mind is you have “stuffed” the initial street address with the name of a campus – perhaps that is throwing a spanner in the works – and I wonder if you could try again without the campus name in that field?

[Barry]

Happy to help!

[Barry]

Glad that worked.

I’m surprised to hear Excel doesn’t make it easy to generate UTF-8 output, but it definitely looks like the same approach you used here – using Google Sheets – is what others have had to fall back on, too.

Anyway, happy it’s all working 🙂

[Barry]

Awesome!

[Barry]

Hmm, well, you could certainly achieve something similar if you override the community/edit-event.php template to include some code like this near the top:

if ( ! user_can( 'minimum_capability' ) ) {
    echo 'Sorry you cannot submit events';
    return;
}

You would need to adjust the initial line to accurately target those roles/capabilities you are interested in here.

Does that help?

[Barry]

Ahh, I see.

That setting exists to control access to the admin environment, not from the community submission form.

In this case you’re going to have to write a snippet to take care of your specific needs. In outline, I’d probably think of doing something like this:

• Hook into parse_request or some other suitable action and test to see if the request is for the submission page
• If it is, check out the current user’s role or whether they have some specific capability you are interested in testing against
• Depending on the outcome, redirect to an appropriate location

I hope that gives you some ideas – and good luck 🙂

[Barry]

Hi Elisa,

Thanks for posting 🙂

This short snippet – which you might add to your theme’s functions.php file – should remove the additional fields section from your single event’s meta area:

add_action( 'init', 'remove_additional_fields_from_single_meta', 100 );

function remove_additional_fields_from_single_meta() {
	if ( ! class_exists( 'TribeEventsPro' ) ) return;
	$callback = array(TribeEventsPro::instance()->single_event_meta, 'additional_fields');
	remove_filter( 'tribe_events_single_event_meta_primary_section_end', $callback );
}

Does that help?

[Barry]

Hi – sorry you’re experiencing difficulties.

Yes, your data should remain intact, but we’d always recommend making a complete backup (and knowing how to restore it) as a sensible precaution 🙂

To the problem at hand, it looks like requests to load the next/previous month are being redirected, so that they use the secure HTTPS protocol: I’m curious, could this be because you have a security or SSL helper plugin installed, or due to some configuration setting?

Can you confirm the problem was still present when you removed all other plugins and switched to a default theme (I realize you indicated having done this, but I’d like to double check as what I’m seeing isn’t the expected behaviour on a clean WordPress installation).

Let me know how you get on!

[Author]

Posts