[Barry]

Hi Oliver,

This seems to be a translation problem.

In this particular scenario, we try to pull in the translation of %s Categories with an _n() call (which lets us switch between singular and plural forms).

However, although we do have a translation in most languages – German included – for %s Categories it has not been setup in such a way that it can be used through _n(). I don’t see an obvious way to get around this on our translation site and it may be we need to reconfigure a couple of things on our end before we can make that happen.

Please bear with me and we’ll see what we can do to fix this 🙂

[Barry]

OK, so one or more of your template overrides are likely to be the problem.

Are you able to run through any which relate to list view, compare them to the current default versions and see what’s what? You could also follow a similar strategy as you did with the tribe_events directory itself and temporarily rename individual template overrides to see which specifically is the culprit (bearing in mind, it’s possible that there might be problems in more than one).

Alternatively – or additionally – if you add a plugin such as Query Monitor or Debug Bar those may help in highlighting areas which are misbehaving.

[Barry]

Thanks Kyle,

I appreciate the kind words (and have shared with the team)!

I was just curious on the shortcake to add it to a page; maybe something to be added as a feature in the future? I think it could be very useful and great addition.

It definitely could be useful and it’s under active consideration – even so, please feel free to up-vote and/or comment further in this feature request thread 🙂

I think we’ve gone as far as we can on the issue at hand so I’ll go ahead and close this topic, but of course please do not hesitate to create new topics if you find you do have follow-up questions, or indeed if anything else should crop up.

Thanks again!

[Barry]

Thanks Matt.

Can you confirm exactly where you are seeing that message? After reviewing your account I would expect an “out of domains” error or something similar (as your keys are activated against what appears to be a temporary, testing or staging URL) but it’s strange to hear that you would see something other than that.

As a starting point, I would definitely recommend you visit the license key management page, clear or “disconnect” your keys and then return to and re-save them within the Events → Settings → Licenses on your own WordPress site to ensure they are linked with the correct domain.

Does that get us any closer?

[Barry]

Thanks for sharing 🙂

Could you also let me know if you’ve had an opportunity to temporarily turn off your template overrides (this is as easy as renaming the tribe-events subdirectory within your theme to off__tribe-events or something similar) and does that restore the expected behaviour of list view?

[Barry]

Hi @dmtalvdal,

I’m sorry to hear you have hit up against difficulties.

The ajax navigation seems to be working without any Javascript-related problems, though there does seem to be an unrelated Javascript error coming from your theme or another plugin:

SyntaxError: unterminated string literal

However, I don’t believe that has a direct bearing on this. Can you confirm if this problem just suddenly started? I don’t actually experience it locally using the same version of the plugin, though I also don’t have exactly the same plugin/theme stack as you do.

Are our standard troubleshooting steps something you could consider, either on your main site or a testing site?

[Barry]

Hi Matt,

I’m sorry to hear that.

Can you confirm which license key is entered in the licenses tab and which domain this is happening on?

(If you could share your system information by private reply that would also give us this information 🙂 )

[Barry]

I’m afraid there isn’t a shortcode to make that happen.

The above CSS was just a minimal starting point to help steer you in the direction of making things presentable – I appreciate it doesn’t result in an appearance (in regards to the header area) that is identical to the blog page, etc – but, as can be the case given how many themes there are out there, sometimes more in depth customization work is needed to really get a glove-like fit between theme and plugin.

Now that you are using the Default Events Template though, do bear in mind that you can override and customize it (again, please refer to the Themer’s Guide for information on doing so).

This is useful because your theme’s header.php template is called from our default-template.php – therefore, if you override it, you can set some kind of condition or even call an alternative header.php that puts a nicely formed header in place for event views that matches your other pages.

However, we’d have to leave you to drive that forward and figure out the details: perhaps your theme vendor could provide you with a few more hints in this regard? Much as we’d love to be able to help further, ultimately the people who best understand the theme’s code are the same people who wrote it 🙂

Does that help any further?

[Barry]

Hi Kyle,

Could you try the steps outlined here (and set up a tribe-events/tribe-events.css stylesheet within your theme) then add these rules to it:

#tribe-events-pg-template {
    position: relative;
    top: 12rem;
}

header#pageheader {
    background: darkcyan
}

That should get you a little closer and you can adjust further from there 🙂

[Barry]

Hi Charlie,

Right now I’m afraid that is not possible “out of the box” (though it certainly could be realized through some customization work).

WooCommerce Tickets – as with all of our ticketing extensions – has been designed as a simple but robust ticketing solution and for that reason doesn’t ship with some other more advanced event management facilities.

With that said, we’re aware of just how much demand there is for this and a new plugin, or set of changes to our existing plugins (the exact details haven’t quite been finalized), are in the works 🙂

[Barry]

Hi Kyle,

I am unfamiliar with your theme and it’s possible this might require a little assistance from the theme devs (it looks like the calendar is being converted into an excerpt accidentally) however before we do that I’ve got something we can try.

Can you visit Events → Settings → Display and try changing the default events template? With some themes the Default Events Template is a great fit – for others the Default Page Template does a better job and others still might require something else, so playing around with this initially is worth a shot.

Let me know if that helps!

[Barry]

Hi @simpleconnections,

I’m sorry to hear that.

Can we start by looking at your system information, if you are able to share it via a private reply?

I do see that if I go to …/events/month/ the calendar is populated, so it’s certainly puzzling that nothing would show on the main events page.

This also raised a couple of questions in my mind. Your system information may in part help to solve those, but I’d be interested in any feedback you yourself can provide here in case the problem relates to customizations you have made. For instance, it appears as if you have some template overrides relating to list view.

I see you noted trying to delete a template relating to the widget, but I’d be interested to know if list view becomes operable if you (temporarily) remove any list view template overrides?

Also, I’m not sure how to word this elegantly, but the last two times I have clicked update on Events Calendar plugin some site functionality has broken, which isn’t great, from a responsible and backwards compatible programming standpoint.

We try hard to get this right and certainly would agree we’ve come up short on a couple of occasions — and we greatly appreciate your support as we continue to move the plugin suite forward.

[Barry]

Hi Bill,

The text/calendar mime type must be allowed.

iCal Importer tries to ensure it is amongst the mime types returned when WordPress’s get_allowed_mime_types() function is called – but it’s possible this is being overridden, whether at WordPress level or something higher that that.

So, confirming with Synthesis that that isn’t blacklisted (or the converse, that it is whitelisted) is worth a shot.

Let me know if that gets us any further!

[Barry]

Hi Rafael,

Thanks for contacting us and I’m sorry for any confusion that has arisen.

Our apologies for not detailing the multiple-organizer change in our update notes: we should have been clearer on that point. Generally speaking, though, the Community Events form has and continues to be almost a direct reflection of the event editor found within the admin environment.

Is there a way to deactivate this feature?

I’m afraid no settings exist to change this. I’d love to hear more about the reasons you wish to “unwind” this change, though – as we’d certainly be open to the possibility of making a change.

Is there a way to remove the note about the “obfuscate plugin” below the email field?

We do in fact have an issue logged to remove this from the Community Events submission form. The intent is to help educate site admins about the danger of “exposing” email addresses and point them to a source of plugins that can help with this, however it doesn’t really make sense to have this in the Community Events form.

For both of these problems, if you create a new stylesheet in your theme at YOUR_THEME/tribe-events/tribe-events.css and add the following rules, you should be able to achieve something that looks close to how it did previously:

https://gist.github.com/barryhughes/2c2a03d4e5b8f3a0033b

Does that help?

[Barry]

Hi Advait C,

Essentially, if you’ve got WordPress up and running and it is already “talking” to your database (if it isn’t you’ll know – because WordPress simply won’t work without a valid database connection), then you need do nothing more.

The Events Calendar and all of our premium plugins talk to the database through WordPress itself, so no further database configuration is necessary after installing and activating them 🙂

I hope that answers your question but let me know if I can clarify anything else, here.

[Author]

Posts