[Barry]

That is strange. Is it possible something else is conflicting here? Though I appreciate you noted having tried deactivating all other plugins/switching to a default theme, can you confirm that you also deactivated any WooCommerce specific addons (with the obvious exception of our own)?

What payment gateway are you using here?

 

[Barry]

Hi Andreas,

Some great questions there.

Removing downloads from the ticket doesn’t actually annul the order itself; nor is there currently a two-way link between the download object and the attendee’s presence on the attendee list. I’m not actually sure at this point if it would make sense in every case to facilitate this and think the best course of action here is to post a feature request detailing how you would like the system to behave in this situation.

As well as giving other users a chance to show their support for the idea, it also means they can share any concerns (if for instance it would stop them from doing something else).

In terms of actually working around situations like this, cancelling the order and asking the customer to resubmit – or using any addons for EDD that let you manually build orders, perhaps – is probably the best approach.

Also, it still has the total counting set wrong, since it does not seem to be subtracting those tickets that I REMOVED in the actual order for that attendee/customer.

True, and that is connected with the above. However, if you cancel or refund the entire order I believe the count will be adjusted at that point.

Does that clarify things at all?

[Barry]

Hi! The answer is yes: where possible, the venue and organizer will also be imported. Does that answer your question?

[Barry]

Hi – great point about the lack of a “PRO” tag in the credit link … we’ll certainly get that noted down for some further attention – great catch!

I’ll try and summarize what the situation with the two issues you listed – I would ask though if you need further help to try and stick to one issue per thread, it makes it easier and faster for us to help you 🙂

With regards to the countdown widget – this depends on Javascript to function properly. Unfortunately it looks like a couple of scripts added by your theme, namely default_dynamic.php (despite the .php file extension it is used to supply JS) and default.min.js, introduce some not insignificant errors and so working with the theme author to resolve those problems in the first instance is going to be the best way to approach this.

Last but not least, the issue with month view appears to be the result of your theme and an overzealous “polyfill” script it adds. Again you could talk to the author about that and see if they could even provide a snippet to kill the polyfill (what I’m referring to here is a script that takes placeholder text like Search and actually populates the field with it) or alternatively you could try adding this snippet fellow team member Brook put together (try adding it to your theme’s functions.php file) and see if that helps.

Thanks!

[Barry]

This is pretty puzzling and it sounds like perhaps – for some reason – you have _EventStartDate entries in the database for one or more events, but those entries are empty.

We’re not sure why that would be or how that situation would arise, but we’re investigating ways to deal with this. One approach you could use in the meantime (though normally we don’t recommend editing core code, but if you feel fairly comfortable working with code and take some precautions like making a backup you should be good) is to open:

events-calendar-pro/lib/tribeeventspro-schemaupdater.php

Then locate the convert_recurring_event_to_child_posts() method, which begins on or near line 50. Within that, look for:

foreach($start_dates as $date) {
	$instance = new TribeEventsPro_RecurrenceInstance( $event_id, $date );
	$instance->save();
}

Change this to:

foreach($start_dates as $date) {
	if ( empty( $date ) ) continue;
	$instance = new TribeEventsPro_RecurrenceInstance( $event_id, $date );
	$instance->save();
}

Hopefully that provides you with a working solution until we can roll out a substantive fix.

Once again – our apologies for the inconvenience.

[Barry]

Can you share a screengrab (or just detail here) the event settings? For instance:

• Starts on 1st April 2014 ends on the same day
• Is an all day event
• Recurs using a custom pattern, weekly, each week on Saturday and Sunday until 30th April 2014
• … and any other pertinent details

Could you also share your system info as provided in the Events → Help admin screen?

Thanks!

[Barry]

Well that’s not good!

Just to clarify, you’re saying that this happens with an exact duplicate of the original template placed within your theme? Or do you mean it occurs after trying to follow the steps in the tutorial?

 

[Barry]

Very odd: there seems to be a link with the Countdown widget, I’m not sure at this point what’s actually causing this though. Can I ask you to:

• Enable WP_DEBUG
• Install Debug Bar

Then if it’s ok I’ll log back in and take another look – thanks!

[Barry]

That is indeed the approach I’d recommend here – the alternative would be creating individual events for each day the event runs.

What sort of concerns do you have about using recurring events in this situation?

[Barry]

I definitely appreciate that since issues have been introduced by the recent update it is tempting to group them together in a single thread – but it actually makes it harder for us to assist. For any subsequent issues, please post new threads and stick to one issue per thread, unless they are very closely linked.

3. Changing “End of day cutoff” setting to 1am sorted the problem, though it still needs a fix?

It definitely does need a fix – we’re working on it right now 🙂

4. Yes, I got a clear impression on that from you here: “these are geared at making week view start at whatever time the earliest event in a given week is” (https://tri.be/support/forums/topic/adjusting-time/). You write “…in a given week” – but problem is that the neither Month or Week View shows the earlist event in a given month/week.

I’m sorry for the confusion, what I said was admittedly a little ambiguous.

What I meant was that, when a week is being viewed if the earliest event any day that week is (for example) 9am then the week view grid would initially set itself to 9am as the first row (though you would still be able to scroll up).

I didn’t mean that month view would automatically jump to August, if that is when the next upcoming event happens to be.

5. Why has this style=”height: 68px;” been set for all columns in the tribe-grid-header? It’s supposed to look like this: https://www.dropbox.com/s/vq3zf4r8x7u4scv/Screenshot%202014-03-29%2011.57.15.png …

Again, there is a bug which we are working to resolve. If you see an inline style being set it is generally being handled dynamically rather than as the result of a sylesheet.

6. This occured with the 3.5 update so it must be your end

6. (follow up): Check url here: https://www.dropbox.com/s/6t8y2ufc1j2cw2h/Screenshot%202014-03-29%2000.37.38.png

It may well be on our side, nonetheless I would once again ask that you post a new thread for this issue. Similarly, for your subsequent issues #7-8, please also create new threads if required and one of the team will be happy to assist.

Likewise, Cynthia, if you need assistance for your specific issue please post a new thread of your own (or if it is a general suggestion/request with regards to how CSS is handled our UserVoice page is also suitable).

To avoid any confusion I am going to close this thread out – we will continue to progress the bugs we have already acknowledged of course and will be more than happy to help with any other issues in separate threads.

Thanks!

[Barry]

Sure – well what I’d recommend in the first instance is approaching the theme author and telling them that you are concerned the theme does not allow widgets to add additional CSS classes as is expected in WordPress. You could also refer them to the WordPress Codex entry on registering sidebars, with particular emphasis on the example code for the before_widget property.

They don’t need to implement exactly the same pattern, but it’s a good starting point and should prevent issues like this one.

I hope that helps 🙂

[Barry]

OK. So though I appreciate this tied in with updating PRO, can you confirm you updated all of your Modern Tribe plugins and can you also confirm if this issue occurs with no other plugins running and only a default, unmodified theme?

Thanks!

[Barry]

Apologies for any inconvenience this has caused – we are aware of it and will fix it as soon as we can. In the meantime an approach like Cloud Genius outlined or this alternative will hopefully tide you over until that point.

Sorry once again.

[Barry]

Definitely feel free to post this as a feature request – the fact that two of you would like to see it is an indicator that others might, too.

In terms of finding help in the short term there are lots of marketplaces where you can hire freelance developers, including (though we don’t particularly recommend any in particular) WordPress Jobs, People Per Hour and many others besides.

Good luck!

[Barry]

You’d definitely need to make sure your upcoming (“dummy”) event is assigned to a venue with a valid address, so that it has geolocation data associated with it – apologies if that wasn’t clear.

Does that help here?

[Author]

Posts