[Barry]

OK … let’s leave this open a little longer then so you can confirm/let us know if more help is needed 🙂

[Barry]

Hi, Guilherme!

Using PRO won’t quite facilitate that goal but it will let you create new fields that accept plain text values – with a little work, you can use those to replace the default start/end dates and times on the frontend.

Again, I’d emphasize that some amount of custom dev work would be required. What you’re seeking isn’t supported ‘out of the box’.

I hope that clarifies things 🙂

[Barry]

That’s an idea with a lot of potential: you could certainly accomplish this with some custom development work, but I’m afraid it’s not currently part of our feature set.

https://tribe.uservoice.com

You could however propose this idea on our UserVoice page – this would help us to measure how much demand there might be and we could consider baking this into the plugin from there 🙂

[Barry]

Thank you 🙂

We see the problem now – we have this on our issue tracker and as soon as a solution is ready to ship, we’ll update you.

Something that you might try in the meantime: install and activate The Events Calendar, even if you don’t intend to use its functionality. You may find its presence resolves this problem (as a temporary workaround until we supply a substantive fix).

[Barry]

OK, that’s weird but also great 🙂

Perhaps code from other plugins was running (and taking a long time), when triggered by the various actions that fire when new posts are created, or something of that order?

Whatever the cause, I’m glad it’s fixed itself and I’ll go ahead and close this topic – but of course feel free to create new topics if we can help with anything else in the future.

Thanks again!

[Barry]

Interesting; I still can’t seem to replicate though.

Regarding Unyson, if you do deactivate this – when you follow our standard conflict testing steps – and enable ticketing support for regular posts or pages, can you replicate the problem then … or does this only occur if Unyson is enabled (I’m a little unclear why this still needs to be enabled even when you’ve switched to Twenty Seventeen)?

It looks like you have only enabled ticketing for “fw-event” type posts at present. Is that post type generated by Unyson and, if you can’t follow the steps I outlined above, can you still test if the same problem happens when applying tickets to normal posts/pages?

Thanks so much!

[Barry]

Hi @akumu,

Sorry to hear you are experiencing difficulties.

I can’t immediately seem to replicate the same problem so would love to gather a little more information:

• Can you confirm your plugins are all up-to-date?
• Could you share your system information with us?
• I’d like to double check that you did indeed test for conflicts and found this was still a problem, even with a only a default, unmodified theme (like Twenty Seventeen) running alongside our plugins, plus your ecommerce plugin?

Thanks!

[Barry]

Possibly!

That’s a little more involved than we’d normally help with, though.

Can I ask if the Location of Tickets Form setting found in the Events ‣ Settings ‣ Tickets admin screen provides a workable approach for you?

[Barry]

Hi Kam,

Thanks for contacting us – I’m sorry to hear you’ve hit up against difficulties, here.

If this is happening consistently, could you try updating manually? Ideally that would not be required, but it may be the fastest path to a solution here.

Can you also tell me if this is a problem with other plugins, or do you only experience it with Events Calendar PRO?

Thanks!

[Barry]

Hi Simon,

Thanks for reaching out!

It sounds like each ticket (“A → B” and “B → A”) needs to have its own separate inventory (100 tickets for each).

This is fully supported by our plugins, so if for example you set yourself up with Event Tickets, Event Tickets Plus and a suitable ecommerce plugin such as WooCommerce, I believe you can get close to your end goal here.

With the above plugins in place you could also take advantage of shared capacity (sometimes called “global stock”) – more about that here:

theeventscalendar.com/knowledgebase/making-tickets

If I’m understanding you correctly, though, you probably don’t need that capability – though it’s worth being aware of it.

Remember also that we offer a 30-day refund period, so you could try this out and work with us to tune things a little (while we can’t provide you with custom dev services, we may be able to offer high level guidance and at least point you in the right direction) and see if you can bring about a final solution you are comfortable with 🙂

I hope that helps, but do let me know if you have any further questions.

[Barry]

That’s strange.

I’m assuming if you – as a site admin – create and publish an event via the admin environment things are faster? Can you also confirm if it’s ok for us to make a test submission on your site?

Thanks!

[Barry]

Hi @pwnhcca,

I’d strongly recommend taking the WPML (multilingual) part of this across to their team – I know they’ve been working hard and doing a great job at maintaining compatibility and would probably be glad of your report.

Also previous Enfold appropriate stylings for various page elements have been affected by the latest update.

We did make a number of changes to the way assets (including stylesheets) are loaded which could certainly have impacted here. Have you made the Enfold crew aware of this? Again, that’s probably a great starting point in this case.

[Barry]

Hi Amanda,

We need you to fix this.

I know, and we want to help you fix this 🙂

Can you confirm if you made any headway with my last two suggestions (setting up a staging site, or using Duplicator to create a file that will let us replicate locally)?

If for any reason you cannot follow either, please let me know and we can explore other options.

If you have a phone line, this would have been solved weeks ago – but this 24 hour forum this is NOT HELPFUL.

We don’t offer phone based support at this time; however I’ll certainly check in on this conversation more frequently if I can.

[Barry]

Understood – we’ve nudged the team about this again. Thank you for your patience in the meantime.

[Barry]

Hi Brian,

The string to translate is %s – Attendee list which is itemized in Event Tickets’ .POT file:

Event Tickets 4.7.6 lang/event-tickets.pot (line 252)

Does that help/clarify?

[Author]

Posts