[Barry]

Hi Larry,

I see what you mean – that’s definitely a little misleading and I’ll make a note for us to amend the tutorial accordingly. In general though, you will not be able to use any names that also include square brackets quite in this manner.

That’s not to say you can’t or shouldn’t try to catch those and use them in your own required field check – just that you’d need to do a little extra work to make that happen.

Apologies for any inconvenience on that one.

[Barry]

Hi Graeme, I can understand your position here and would ask that you email us at pro [at] tri [dot] be – please include a link to this thread to provide the team member dealing with this some context and ideally also a copy of your purchase receipt.

Thanks again for trying to work through this with us and hopefully at some future point you’ll have a reason to give us another try.

(I’ll go ahead and close this thread.)

[Barry]

Hi! You would pass the class name into the_widget(), so it would indeed be something like:

the_widget( 'TribeVenueWidget' );

You can also pass arguments across as in Snorton’s example in the thread you linked to – full documentation for the_widget() is available here: http://codex.wordpress.org/Function_Reference/the_widget

I hope that helps – but as this is really custom development territory we cannot assist any further with this one and will go ahead and close the thread. Of course if you have any other questions please don’t hesitate to let us know (by creating new threads).

Thanks!

[Barry]

OK: I can appreciate this is frustrating but we are trying to help and I’m confident we can get to the bottom of this 🙂

Can you confirm what version of the plugin you updated from? Could it have been 2.0.11 or earlier? What I notice is that the output of the widget (at HTML level) is nothing like it should be. That leads me to wonder if:

• The update process didn’t complete quite as smoothly as it should have done, and legacy files have been left in place
• Perhaps more likely, this could be a caching issue – it looks like you are using WP Super Cache
• It may even be some sort of strange mix of the two

On the caching front, though I appreciate you taking the time to deactivate all of the plugins, it’s important to note that in the case of caching plugins this does not guarantee all caching effects will be removed. So clearing the cache and, if that doesn’t work, deactivating WP Super Cache and then clearing out the cache and ensuring no trace of it remains (please follow their instructions for doing so – it may include a change to the .htaccess file) is a good way to go.

The last theory I have is that a customization was made somewhere along the line (perhaps to add a featured image) and that was either made in the wrong place or somehow was missed when testing with a default, unmodified theme.

Does that help?

[Barry]

…Ahhh… apologies.

I realize now what went wrong there (and completely misunderstood your question as a consequence, sorry about that). When you mark a reply as private our own follow-up reply is consequently also marked private but may not be visible to you – and unfortunately it isn’t particularly obvious to us that that has happened on our side of the forum.

Clearly that’s a problem we need to resolve and we hope to do so soon. What I’d asked though, was that you share your credentials here a a private reply. Does that clarify things?

[Barry]

You should be able to see a checkbox something like this:

Is that not visible to you (I didn’t send an email, as sharing the details here should suffice).

[Barry]

Thanks for the update:

I checked all users and all have the API key in their profile, so that didn’t seem to be an issue.

That is definitely different to what I am seeing and I cannot replicate that – so long as the users have the very same API key then there is no issue when they edit events. Can you confirm they are indeed identical (I’d just like to be sure as this might change the shape of how we proceed here).

Thanks!

[Barry]

Hmm, ok. Minifiers can be problematic especially if they re-minify scripts and stylesheets that have already been minified (like ours).

If that is the key to this – ie, disabling it resolves the problem – it’s definitely one to take to that plugin’s author, or else reconsider using it/look at the settings it offers to workaround this as I don’t imagine it’s too uncommon a problem in terms of what minification plugins face (some will let you define exceptions, for instance).

I hope that helps

[Barry]

Sure: well if you could make the theme available as a downloadable .zip that would be great – please just share a link here, as a private reply if you prefer.

Thanks!

[Barry]

OK: it is worth exploring the possibility of a theme or plugin conflict in that case.

Can you deactivate all other plugins except for The Events Calendar and Events Calendar PRO and also switch to a default but unmodified theme (such as Twenty Twelve). Does that make any difference to this issue?

[Barry]

The Location field certainly ‘maps’ through to the code that essentially hinges on Google’s API. However, that’s an interesting question and I daresay if you knew the actual venue data was accurate (ie, the city field was correct in each case) you could certainly rewire it and/or restrict searches generally to results where the event is assigned to a venue with a certain value in the city field.

So yes that’s another option you could explore (though, again, we can’t provide particularly deep support for a customization like this).

Hope that helps 🙂

[Barry]

Thanks for helping out there, Patti 🙂

@wineevents hopefully that gave you some other ideas to explore – and I’ll go ahead and close this thread. Of course if you have any other questions please don’t hesitate to create new threads. Thanks!

[Barry]

Hi! It’s been a while without any follow-up so I’m hoping you managed to figure this one out and will close this thread. Of course if you still need help with this or anything else please don’t hesitate to create new threads as needed.

Cheers!

[Barry]

It’s been a while here so I’m guessing you got to the bottom of this or else found a suitable workaround. For that reason I’ll go ahead and close this thread – but if we can assist with anything else please don’t hesitate to create new threads as needed.

Thanks again!

[Barry]

Closing this thread.

[Author]

Posts