[Barry]

Hi!

How do you want to identify the events that need this treatment? Would tagging them (simply using a straight forward tag like “coming soon” or “TBA”) be acceptable?

[Barry]

OK, thanks for clarifying.

At present tribe_get_cost() does not return the cost of any tickets that might have been set up using plugins like WooCommerce Tickets.

Once a ticketing plugin is active, the default cost field that is normally visible in the event editor actually becomes hidden: the goal of this is to avoid confusion, but it’s possible to reinstate it and we can explore that if you think it would be useful to do so.

With regards to what you’ve described, is it possible that – prior to installing and activating WooCommerce Tickets – you had set up prices for previous events using the default cost field? That might explain what you’ve detailed here.

[Barry]

OK. Could it be that you’re testing this in the default view (map view) but those particular events are not bound to venues with geographic information attached to them?

If I perform the same search in list view for instance:

portal.brasileirinho.com/eventos/proximo/?action=tribe_list&tribe_paged=1&tribe-bar-search=carlos

Then all three of the events you listed are returned.

While I see they do have what look like valid addresses for their respective venues, I seem to recall we previously determined the nature of your hosting setup was preventing actual geographic data – namely, coordinates – from being pulled in via the Google API.

Unfortunately, if the plugin does not have this information it cannot include events taking place at those locations within map view.

Might that explain the problem?

[Barry]

Ah, gotcha!

Though that is definitely a pain it’s something we’ve already got on the radar and we hope to turn out a fix soon. The problem isn’t that the image is jpeg as such, but rather it’s because of the extra information following the .jpg file extension.

Unfortunately, at present, that extra stuff (oh=8c3ab36813ae772…) is not being stripped out and that makes WordPress think it is dealing with some unknown filetype. It does seem to happen that this often occurs with jpeg format images though that may be nothing more than coincidence.

At any rate, this basically boils down to an oversight in our existing plugin code: please know that we are in the process of fixing this and we’ll do our best to keep you posted by updating this thread as things move along.

Thanks again for your patience 🙂

[Barry]

Hi rariasjr,

I’m sorry you’re hitting up against this.

This is actually a known bug and one we’re working hard to resolve – all things being equal we should see a fix being delivered with our very next upcoming event (though while I’m hopeful this will be that case, I can’t offer any guarantees or promises).

Thanks for your patience and support in the meantime 🙂

[Barry]

Hi!

I’m going to move this from pre-sales over to the WooCommerce forum as that seems a more appropriate home for this one, given your license type 🙂

I’ve been using the tribe_get_cost() function to show the price of an event on single-event.php.

So do you mean you added it as a customization? Can you share your custom template code (via Pastebin, Gist or similar) if so?

Also, just to clarify (as I note you are a WooCommerce Tickets user) how have you defined the price for the event? Are you expecting the ticket price to come through?

[Barry]

Hi veruska,

I’m sorry to hear you’re hitting problems.

Can you give me a concrete example so I can offer you more guidance? If I visit your site what sort of keywords would generate the kind of limited results you are describing (and can you also link me to a couple of the events you would expect to see that are absent in these cases)?

Thanks!

[Barry]

My pleasure 🙂

[Barry]

Hi Frederick,

I’m sorry to hear that.

You are of course welcome to request a refund: please email us at pro (at) tri (dot) be and include a copy of your purchase receipt – if you could also link to this thread to give the team member dealing with your request some context that would be great.

Thanks once more for giving it a shot and I do hope you will be able to consider Events Calendar PRO again in the future 🙂

[Barry]

Thanks for that update – I actually see this myself even if I create a brand new event and set the custom fields at time of creation, but I’ll definitely add your note to our internal bug tracker in case it helps the assigned developer to reproduce 🙂

[Barry]

I used the code in the tutorial (copypasta).

OK. On doing the same thing (and, to be clear, in this case we’re interested in the second snippet from that tutorial) this works as expected.

Could something else be getting in the way? Might it be worth running through our standard troubleshooting steps and – before reactivating anything – add the snippet and see if it works then?

[Barry]

OK, before we go any further can you confirm if you’ve tried visiting your Permalink Settings page (you don’t need to change anything – just visiting this page “flushes” WordPress’s list of rewrite rules).

Does that help with this at all?

[Barry]

WooCommerce Tickets does not actually interfere in the checkout process. Adding custom fields and using that information is really the sort of customization that you’d need to drive forward yourself – though we’re happy to point you in the right direction if we can.

That said, we don’t typically offer technical support here in the pre-sales forum and would ask that you post your question over in the WooCommerce Tickets forum: one of the team will then be along to help as quickly as possible 🙂

Thanks again!

[Barry]

Thanks again Nick!

[Barry]

Thanks Nick – thanks for posting – hopefully that helps others out there 🙂

[Author]

Posts