[Barry]

Alright. In that case I’m pretty stumped. Possibly I’ve missed something obvious in all this – in which case it would anyway be good to get some fresh eyes looking over everything, so please bear with me while I check in with a fellow team member.

[Barry]

Hi Karen,

WP Router is a submodule of Community Events and is indeed required for it to function. You generally don’t need to worry about that however, so long as you cleanly upload the latest code (and none of the plugin code from the previous version remains) you should be good to go.

[Barry]

… And is this a “regular” WordPress installation or is it multisite? It definitely looks like a current release, based on your screenshots, but could you just confirm exactly which?

Edit: in fact, ignore the version number question – I see you added the WP version when you opened the ticket. So unless it’s different don’t worry.

[Barry]

OK. It could be I have to pull in another team member to review this with fresh eyes. Before I do, is there anything you can tell me about the hosting environment?

Is it a common hosting package or is there anything atypical at all (could it be Microsoft IIS instead of Apache as the server or anything of that nature)? If you could even link privately to the product page for your hosting package should that be appropriate it could definitely be useful.

[Barry]

So basically we can just build on that and reuse the same functions. The easiest way to work this into the calendar/grid view is probably to override month/single-event.php … so:

• Copy this template: the-events-calendar/views/month/single-event.php
• Place your copy in: YOUR_THEME/tribe-events/month/single-event.php
• Change it to something like this

[Barry]

I wasn’t aware of that.

Yes that plugin may be useful and it would be interesting to hear back from you on that count in case it helps other users.

Without wanting to sound like we are passing the buck this is however more of a WooCommerce issue (if this is something that businesses in Australia require) and – I guess this is what that plugin you referenced adds – the ability to mask the post IDs and use a different numbering scheme for orders would properly be solved at that level, not by changing the operation of either WooCommerce Tickets or WordPress itself.

[Barry]

I have to admit to being perplexed on this one. Though a bit of a long shot (because the published date I can see in the screenshots suggests your server or WP date/time settings are correct) could you try widening the sale dates so that they are on sale from a month prior to a month after the event?

I know also you said this is a bare bones install, but is there any possibility of custom template code or custom code within your theme’s functions.php file being present?

[Barry]

This reply is private.

[Barry]

Hi Matt,

Sorry you didn’t have a smooth experience there.

It rather sounds like some files were missing from the plugin directory. If you want to give updating another spin, please ensure all Modern Tribe plugins are updated and are in synch (you can’t leave one behind at version 2.0.11 for instance – so please do observe any notices to that effect that display in the plugin admin page) and perhaps even handle the update manually by FTP – just in case an unpacking error meant some files were dropped.

[Barry]

Well, it definitely should be working but, as you noted, there seem to be some other concurrent issues.

Thinking of your new base install, can you also share a screenshot of the ticket settings (event start/end sale date) for your test event? I didn’t see that in the Dropbox folder.

Thanks!

[Barry]

Thanks for sharing those screenshots. Can I ask you to provide us with one more – again showing the ticket config – except this time click on Edit before taking the screenshot so that we can for instance see the start and end sale dates and other fields?

Thanks for your patience!

[Barry]

Karen: after reviewing this one of the team noticed that some pages look as they did in version 2.0.11 of our plugin whereas some look just as they should when using 3.0.

What we suspect is that perhaps you updated manually (by FTP or even your hosting control panel’s file manager tool) and that you merged the new plugin directory with the old. Does that sound like something that might have happened here?

If so, would you be able to download fresh copies of our plugins, deactivate and delete the existing ones (on your server) and upload them afresh?

[Barry]

No need to apologize, we much prefer if you create individual threads for separate problems and we can often deliver faster support that way, too.

It would be much appreciated if you could help with the Italian translation – our point of contact for that is Leah who you can email directly (pro at tri dot be) – all contributions are gratefully received 🙂

[Barry]

Sure thing.

[Barry]

Could this also be the result of a conflict with your theme (if you switch to Twenty Twelve does the problem go away)?

As Jessica noted we don’t officially support third party themes, though we often make an effort anyway, but it may be you need to get help from someone more expert in working with your particular theme in order to work through this as expeditiously as possible.

Have you touched base with the theme author – assuming the theme is the ‘problem’ here – to seek support from them?

[Author]

Posts