[Nico]

Howdy Nienke,

Welcome to our support forums and thanks for reaching out to us. I’ll help you out with this issue!

What you describe is the default behaviour of the plugin: once you import an event via iCal importer and then delete it the system stores a “note” so that deleted events are not re-imported (as this would be the desired behavior for most cases and for automatic imports as well).

To delete saved “deleted events notes”

Add this snippet to your theme functions.php file and re-load the page (it will run once per page-load) until the message is shown, after that remove or comment the script:

/* Deletes 50 posts per page load*/
$posts = get_posts( array( 'numberposts' => 50, 'post_type' =>'deleted_event') );
if (!empty($posts)) {
foreach ($posts as $post) {
wp_delete_post( $post->ID, true);
}
} else {
echo 'Done deleting!';
}


To prevent “deleted events notes” from being created in the future

Add this other snippet to modify this default behaviour:

/*
* Prevents iCal importer from saving a copy of "deleted" events
*/
function tribe_ical_dont_save_deleted () {
$ical_importer = Tribe__Events__Ical_Importer__Main::instance();
remove_action( 'before_delete_post', array( $ical_importer, 'deletedEventSave' ) );
}
add_action( 'wp_loaded', 'tribe_ical_dont_save_deleted' );


will reimporting the same feed (but with in the meantime changed events…like changed descriptions) results in the ical updater updating the already imported events?

The events should be updated yes, give that a try and let me know.

Please let me know if you get the events to show again after using the snippets,
Best,
Nico

[Nico]

This reply is private.

[Nico]

Hey Dan,

Thanks for confirming this! Sorry I couldn’t catch this last week, this was out of my radar (probably I didn’t set the right ticket status after replying, but not sure).

Other issues with stock weird behaviour had been reported this past week as well, so the complete fix (negative stock issue + stock level issue) for this might take a bit longer than I anticipated. Hopefully we can see those out soon but I don’t have an specific date for this.

I’ll set this ticket status to ‘Pending Fix’ and update you on this if any news is available.

Thanks for the patience while we get this sorted,
Best,
Nico

[Nico]

Hey Marc,

Thanks for the follow-up and sorry for the delay on this! We do not monitor the forums on weekends and I couldn’t get a reply on Friday!

Well first of all I’m glad you could sort the original issues – thanks for the compliment 🙂

We generally recommend opening up a new thread if a new issues comes up, this was -as you state- it’s easier for other folks to find an benefit from an existing question.

This particular issue you mention it’s a bug that has been logged a couple of days ago and there’s not much we can do for it until a fix is developed and released. I’m helping some folks with the same bug in this thread: http://theeventscalendar.com/support/forums/topic/sold-out-ticket-quantity/, you can post in there, so you’ll be notified of my replies.

So please let me know if you are good with this (following along a the other thread), and therefor I can close this thread as the original issue had been addressed.

Thanks,
Nico

[Nico]

This reply is private.

[Nico]

Hey Quimbly,

You are welcome 🙂

As you marked this as resolved I’ll go ahead and close out this thread, but if you need help with anything else please don’t hesitate to create a new one and we will be happy to assist you.

Best,
Nico

[Nico]

Hey everyone,

Sorry once again for this issue, I could finally run some additional tests (as some in the QA team were not able to reproduce this I was doubting of a conflict) and gather more info on this for the dev team. We are close to release another maintenance release (4.0.2) and I’m pushing this forward to be addressed in the release.

We currently don’t have a workaround for this, but if the fix is not included in the maintenance release I’ll insist on a snippet or hot fix plugins till this gets fixed + released. I’ll have more news on this tomorrow.

Thanks for the patience and sorry for the hassle,
Best,
Nico

[Nico]

Hey Stéphane,

Jus wanted to give you a heads up on this. I’ve just reviewed this with one of the developers and it turns out that indeed we are dropping the ball here, and missing to load the text domain on actual activation. You were right 🙂

This will be included in the upcoming maintenance release of Event Tickets Plus, but if you want to manually patch the file till this is released you can take the translation load out of the compatibility check statement:

...
function event_tickets_plus_init() {

tribe_init_tickets_plus_autoloading();

$langpath = trailingslashit( basename( dirname( __FILE__ ) ) ) . 'lang/';
load_plugin_textdomain( 'event-tickets-plus', false, $langpath );

if ( event_tickets_plus_is_incompatible_tickets_core_installed() ) {
add_action( 'admin_notices', 'event_tickets_plus_show_fail_message' );
return;
}
...


Thanks a lot for reporting this, and sorry for not seeing your point earlier (it appeared to work on my end),
Best,
Nico

[Nico]

Thanks for confirming it works Jeff, that’s music to my ears 🙂

I’ll go ahead and close out this thread, but if you need help with anything else please don’t hesitate to create a new one and we will be happy to assist you.

Best,
Nico

[Nico]

Hey @pwnhcca,

Thanks for following up with the requested info! I can confirm that there’s a bug with Past Event and ordering we just logged. It seems you are being affected by this as well. A fix is being developed and will be shortly available. I’ll keep you posted on it.

Regarding the featured image issue, I see in your site that has been fixed, can you confirm this? Browsing the photo view of events I see that the image is displaying correctly there.

@ Douglas, thanks for jumping in as well… You were right about this!

THanks for the patience till this is fixed (should be soon),
Best,
Nico

[Nico]

Hey Justin,

Thanks for following up on this and for running the troubleshooting steps. I can confirm that there’s a bug with Past Event and ordering we just logged. It seems you are being affected by this as well. A fix is being developed and will be shortly available. I’ll keep you posted on that front.

Regarding the out of installs issue, it seems you have your licenses configured for the staging site. Checkout this article explaining how to move your license keys.

Sorry for the inconvenience this issue might cause until fixed,
Best,
Nico

[Nico]

Hi Jesse,

Thanks for confirming this and sorry to hear about it’s still an issue 🙁

I can now see on your website how the actual issue and also see that the snippet won’t solve this. I’ve been discussing this with one of the devs from the team, and we came to the conclusion that it’s in fact a bug. A ‘hotfix’ for this is being developed right now!

If the fix can fit in a snippet I will send it over as soon as it’s ready. Hopefully that’ll be very soon. The intention is to include this in the upcoming release (4.0.2) coming out later this week (initially).

I’m sorry for the inconvenience this might cause until fixed, I’ll keep you posted…
Thanks,
Nico

[Nico]

@ Hans, thanks for sending that over. Please note that this doesn’t imply a commitment! Every contribution is much appreciated 🙂

@ Oliver, Sure I’ll keep you both posted on this.

Thanks!

[Nico]

Hey Dirk,

Thanks for the heads-up, I’ve just rechecked and there was a typo in there. Class name Tribe__Tickets_Plus__Main was missing an underscore, my bad sorry for that.

Try this corrected version instead:

if ( class_exists( 'Tribe__Tickets_Plus__Main' ) ) {
remove_action( 'tribe_tickets_ticket_email_ticket_bottom', array( Tribe__Tickets_Plus__Main::instance()->qr(), 'inject_qr' ) );
}


Please let me know if it works as expected now,
Best,
Nico

[Nico]

Hey Paul,

Just wanted to give you a heads on this issue, maintenance release (4.0.1) has been released last week, Can you update the plugins before re-testing this?

Thanks,
Nico

[Author]

Posts