[Barry]

Hi Tomas,

I’m sorry you have hit up against some difficulties.

When did this happen? Can you share your system information by private reply to give me an idea of how your site is configured?

[Barry]

Hi Irene,

Unfortunately I can’t view your site (all I see is a “Coming Soon” message) so I’m not entirely sure what you are referring to … is this something I would expect to see with this widget even with a default theme, or is the “separator” something your theme is implementing?

Thanks!

[Barry]

Hi Brad,

I’m not sure if this is a bug in Gameday itself – or if your own copy has perhaps been modified – but it seems that under some circumstances it tries to call the is_shop() function – however if this function is not defined (noting here that the theme itself does not define it) a fatal error is triggered.

Since this happens when the wp_footer hook fires, most of the page is already assembled – but photo view depends on adding various scripts during this same action and, because of this error, it doesn’t get a chance.

Here’s the actual error:

Fatal error: Call to undefined function is_shop() in /.../gameday/functions.php on line 1118

My guess is this code is assuming and relying on WooCommerce or some other e-commerce type component that implements the is_shop() function being present and activated — and that it is missing in your WordPress site (as it is on my test site).

With that in mind, I’d recommend approaching the theme vendor for assistance (unless of course it was a modification you/someone working on your behalf made to the them code).

I hope that helps!

[Barry]

Besides basically manually checking them like you have already done, I’m afraid not 🙂

Back to the primary problem of registration emails being marked as spam, I’m afraid at this time I don’t think there is much more we can do on that issue: apart from being something that WordPress itself facilitates – rather than being a facet of our own plugins – it seems likely that the method used to send emails is a strong factor and that isn’t something we control.

For that reason I’m going to close this topic, but if you hit other problems definitely feel free to create new topics referencing this one if needed.

Thanks again!

[Barry]

Could you create a .zip of the (parent) theme and upload it to your WordPress site – or to a service like Dropbox – then share the URL by private reply?

Though I can’t offer any guarantees as the problem seems to relate to third party code I’d be happy to take a look as I believe this is a theme quite a few of our users have in place 🙂

Thanks!

[Barry]

This reply is private.

[Barry]

Fantastic: once again, we appreciate your help and cooperation here – we’ll aim to deliver a substantive fix as quickly as we can.

As a token of our appreciation, please find below a coupon you can use sometime in the next year when you either renew one of your personal licenses or if you decide to purchase a new personal license for another of our products 🙂

[Barry]

My pleasure 🙂

[Barry]

Great – I’ll keep this open in the interim in case you do find anything.

Thanks for your patience while we worked through this.

[Barry]

… Do also note that it looks as if a number of your plugins are now out of date, for instance Filter Bar appears not to have been updated (generally its best – and safest – to keep all plugins in sync, so if our core plugin The Events Calendar has a version number like 3.11.x then all linked plugins ought to be 3.11.x, too) 🙂

[Barry]

Hi Keira,

I’m sorry you’ve hit up against some difficulties.

That’s an odd problem and not one we’re seeing wide-ranging reports of following the recent releases. Is it possible it might relate to any customizations you’ve made targeting our views?

[Barry]

Hi Diane,

Great question!

That’s definitely possible. There are a few ways you can insert new fields but I’d probably recommend using a template override. To ensure the terms have been accepted, you’ll also want to add some sort of additional form validation.

Check out these resources which, between them, cover both template overrides and setting up new form requirements:

• theeventscalendar.com/knowledgebase/themers-guide
• theeventscalendar.com/knowledgebase/required-fields-for-events-submission-form

Does that help?

[Barry]

Hi Irene,

Fantastic idea!

The calendar widget is very customizable so you could certainly tweak it and re-form its output to meet your needs here – but, realistically, I’m not sure I’d recommend that over actually building out a fresh widget/shortcode given your requirements.

Definitely take a look through our Themer’s Guide for a better sense of how customizations work within The Events Calendar/Events Calendar PRO, however this is very much custom development territory so we probably will be unable to assist too much (though feel free to ask questions and if we can help – or point you in the right direction – we’ll happily do so) 🙂

Thanks!

[Barry]

Hi Shelby,

The best starting place is our Themer’s Guide, which explains how to safely override and customize various templates that ship with our plugins 🙂

In the case of Community Events and the editor fields, you will probably be interested in any number of the templates within src/views/community/modules/* – and also src/views/community/edit-event.php.

Does that help here?

[Barry]

Hi John,

the instructions do not seem to tell me to add this to the theme’s child theme, but the main theme itself. Is this correct?

Our use of the term “theme” is slightly lose, there – but you can certainly add to the child theme (and if you’ve already got one in place, we’d recommend it).

Does the CSS file need to refer to the plugins main style sheet , as in all other cases of creating a child CSS file?

In the sense of an @import statement? No, it does not.

If you set up a custom tribe-events/tribe-events.css stylesheet then it is loaded in addition to those stylesheets our plugin already enqueues – it does not replace them.

Finally, do if I already have a Child Theme CSS file — can I just simply put the code into this file when styling the plugin’s features???

Potentially, yes.

Really it’s all about observing the normal CSS rules: it either needs to be added after the rules it builds on or else be specific enough to not be impacted by the load order of the various stylesheets.

Ultimately, give it a go! If it doesn’t work within that existing stylesheet you can either tighten up the specificity of the rule or else roll with the recommended approach of using a custom tribe-events/tribe-events.css stylesheet.

Does that help?

[Author]

Posts