[Barry]

Hi! It’s been a while with no follow up so I’ll go ahead and close this thread. If you still need help with this or anything else please do create a new thread. Thanks!

[Barry]

This reply is private.

[Barry]

Hi! It’s been a while with no follow up so I’ll go ahead and close this thread. If you still need help with this or anything else please do create a new thread. Thanks!

[Barry]

I’ll go ahead and close this as it has been a while without any activity – but if you need further help please do feel free to post a new thread. Thanks!

[Barry]

OK. I see what you mean, but this isn’t really what ticketing plugins like WooCommerce Tickets are geared up to do. The attendee list, for instance, is pinned to a specific event.

I think the best way forward in your case is either to concentrate on a solution using WooCommerce itself, independently of WooCommerce Tickets (you could set up virtual and/or downloadable ticket products, for instance), or else you might consider setting up some “convenience events” suitably far in the past or future so that they are out of sight and just use them as a vehicle for issuing tickets (in that approach, you would probably also want to change the catalog visibility setting of the ticket items).

Last but not least, though recurring events are not officially supported you could create an event that recurs each day and set up one or more tickets for it which, at least with our current releases, have the side effect of being available for every instance of the recurring event. I’d caution however that this may be subject to change in the future.

Beyond those suggestions, I don’t know that there is much else we can do for you here.

[Barry]

OK – thanks for trying that. I’m not sure though if you found there was still a problem with everything else deactivated – can you confirm if there was?

If it actually resolved the problem, did you notice if any plugin in particular (or your theme) seemed to trigger the return of the problem once reactivated?

[Barry]

Hi John, that’s great.

It’s difficult to say for sure what the problem was at this point, but it sounds as if you were perhaps being served an older (cached) copy of one or more assets such as Javascript files and that may have been at the root of this.

As you’ve marked this resolved I’ll go ahead and close the thread, but if anything else crops up/you have further questions please do create new threads as needed.

Thanks!

[Barry]

OK, so though I can see various classes being applied to the body element I’m not convinced it is using WordPress’s body_class() function to do so, which is the expected convention – certainly numerous classes I would expect to see are notable by their absence.

Every theme is different and since your theme is retailed commercially I can’t see the code – which makes this a little tricky – but I wonder if you could locate its header.php template (if it has one) and share the code via Pastebin, Gist or some similar service so I can see if this theory has any merit?

Thanks!

[Barry]

Thanks to both of you for your patience. EDD Tickets 3.4.1 is now available and should resolve the problem with download files duplicating. Thanks for your support and patience!

[Barry]

Hi again: we have just released EDD Tickets 3.4.1 and it is available on the downloads page. Can you try updating and see if this resolves the primary issue (of customers being able to purchase more tickets than should be available)?

Thanks!

[Barry]

Hi Michael,

Thanks for posting and I’m sorry to see you are experiencing difficulties.

It looks like something else – your theme or another plugin – is adding a bunch of CSS (rules governing the appearance of your website) to the page which seems to be behind this issue. Here’s the relevant rule which is being added:

.first{
font-family: Georgia, "Times New Roman", Times, serif;
font-size:540%;
/*display: block;*/
float: left;
margin-top:18px; /* use -0.205em for two lines */
margin-right: 6px;
height: .5em;

}

So we could either investigate which component is causing it – some themes for instance allow custom CSS to be added and if that was the case you could make an adjustment there – or else we could just attempt to workaround it. If you add a rule like this to a custom tribe-events.css stylesheet for instance that should fix this.

.tribe-mini-calendar-wrapper .first{
    float: none;
    height: auto;
}

You can find guidance on setting up a tribe-events.css stylesheet in our Themer’s Guide (link over on the right under useful resources) – does that help at all?

[Barry]

Hi @oscarl,

Thanks for posting.

Unfortunately the plugin is not really geared up to do that – though it’s possible you could handle this as a customization if you generally feel at home developing for WordPress.

Can I ask why you need to create a ticket that isn’t associated with a specific event?

[Barry]

Hi John,

I’m sorry you are hitting problems here – but thanks for creating a fresh thread.

On visiting your site it seems to work perfectly (I tried both Firefox and Chrome, in case it might have been specific to one browser). Have you done anything to resolve this since you posted?

Thanks!

[Barry]

Hi Marlene,

I’m sorry you are having difficulties.

It looks like that meta box – Orderrader – you highlighted is a collapsed state (most meta boxes can be expanded or collapsed). Can you click on the small arrow in the top right corner of the same box and try expanding it?

[Barry]

Hi, I assume that you can change the colour of the min-calendar widget by CSS.

You certainly can. I’m not sure exactly what you’re thinking of but the first step would be to review the Themer’s Guide (link over on the right, under Useful Resources) and the section on custom CSS in particular, which will guide you as to safely setting up your own stylesheets.

Does that help?

[Author]

Posts