[Barry]

@held2gether: you’re still absolutely welcome to seek a refund – but if you want to give it a try, this snippet (which you could add to your theme’s functions.php file, for instance) may help until we fix this in an upcoming release:

class Tribe_EDDTickets_Fix31092 {
	/**
	 * Override EDDTickets' own print_ticket_url() callback.
	 */
	public function __construct() {
		add_filter( 'edd_download_file_url_args', array( $this, 'print_ticket_url' ), 20 );
	}

	/**
	 * @param $item
	 * @return bool
	 */
	protected function is_print_ticket_item( $item )
	{
		static $download_files = array();

		if ( empty($download_files) )
			$download_files = edd_get_download_files( $item['download_id'] );

		foreach ( $download_files as $index => $download ) {
			if ( $item['file'] != $index ) continue;
			if ( TribeEDDTickets::TICKET_DOWNLOAD === $download['file'] ) return true;
			if ( TribeEDDTickets::LEGACY_TICKET_DOWNLOAD === $download['file'] ) return true;
		}

		return false;
	}

	/**
	 * Setup the print ticket URL so that a print view is rendered instead of a download file
	 *
	 * @param array $args
	 *
	 * @return array
	 */
	public function print_ticket_url( $args = array() )
	{
		// Determine if this is a ticket product
		if ( ! get_post_meta( $args['download_id'], TribeEDDTickets::$event_key, true ) ) {
			return $args;
		}

		// Interfere only with the tickets link (thus allowing additional files to be downloaded
		// as part of the purchase)
		if ( ! $this->is_print_ticket_item( $args ) ) {
			return $args;
		}

		$args = array(
			'edd_action'   => 'print_ticket',
			'ticket'       => $args['download_id'],
			'download_key' => $args['download_key']
		);

		return $args;
	}
}

new Tribe_EDDTickets_Fix31092;

[Barry]

Awesome, it’s great to hear that it has been effective and though the change probably won’t make the cut for our very next release we’ll do our best to look at integrating it as soon after that as we can.

Thanks again!

[Barry]

We’re generally happy to facilitate refund requests: please email us at pro (at) tri (dot) be and if possible include a copy of your purchase receipt and a link to this thread 🙂

[Barry]

Hi Emily,

I’m sorry to hear you have experienced difficulties. In the first instance, can you confirm which version you upgraded from?

I also wonder if you have any customizations in place (such as template overrides) or anything of that order that you could quickly and temporarily remove to see if they might be impacting?

The reason I ask is that, in the past, the duplicates have been just that: identical but separate copies of the event. When I look at November I see that it is more a case of the same event being linked to multiple times – so there’s a subtle difference there.

I see that others have had this problem with past upgrades. I am not able to shut down the theme – the site’s owners are panicking about all of this.

I can definitely appreciate that.

Given the slightly odd twist to the problem in your case I do think it’s worth eliminating the potential for a conflict here. Are you in a position to test things out on a separate test installation? Plugins like Duplicator and various other tools would make it easy to copy the existing site to a test installation (which could simply live in a subdirectory, ie yourdomain.com/testwp) and you could then troubleshoot there without fear of impacting the live site.

Is that a possibility?

[Barry]

Hi fortgordonmwr,

Thanks for posting 🙂

I believe this is resolved – if you are still experiencing difficulties though please do create a new support thread and one of the team will be happy to help.

That will allow us to focus on the problem as it is in your particular case and will also avoid everyone else who is participating in this thread from receiving update emails (bear in mind it relates to a discussion started over a year ago!).

Thanks!

[Barry]

Awesome, sounds like a solid plan.

In that case I’ll go ahead and close this thread – but please don’t hesitate to create new threads as needed if any of those problems (or anything) crops up 🙂

Thanks again!

[Barry]

… I’d also add that we do try very hard to stick to one issue per thread.

Let’s try to focus on just one of the three issues you initially raised (I’d suggest the third point, ie the recurring event problem) and, if you need further assistance with either of the other two, please do create a new thread and one of the team will be happy to help 🙂

Thanks!

[Barry]

Interesting.

1. I have test with other events it works with change status to publish, but strangely only one event won’t change to publish in admin after I clicked blue Publish button and reload the page! It work ok for other event with similar set up.

I’m not sure what to suggest here as you can only replicate it in the case of one event and I cannot replicate it at all (nor have I seen other users report this).

2. Yes correct, edit all is work if the post ID is all the same, I have notice some recurring events break up into single that caused different post ID … I have explained to client if they edit single this will happened.

OK – so this does indeed sound like it may be expected behaviour (when a chain of recurring events is either split in two or a single event is broken out of the chain) and it sounds like you don’t need anything further on this front.

Here’s 6th Dec event which generate permalink http://redacted.domain/event/event-slug/2014-12-06/ when you go to this link it changed to 7th Dec http://redacted.domain/event/event-slug/2014-12-07/ we couldn’t get 6th Dec to display.

That’s odd.

Interestingly I find if I visit /event/event-slug/all/ for the event in question there may be a fatal error happening and stopping the page from rendering completely.

With that in mind, and also considering the first point, I would again like to ask if you can confirm the outcome of your conflict testing? Could it be another plugin, your theme or some custom code is having an adverse impact here?

[Barry]

Sure – so it seems fine to me and I don’t see any of the issues you detailed initially (if you still see some of the same issues though, please let me know). Perhaps then this was a problem with your customizations?

[Barry]

Great! We’d never recommend changing core plugin code and it does additionally make it hard for us to form an accurate picture of the problem when such changes are in place. If you could remove them, at least for troubleshooting purposes, that would be appreciated.

[Barry]

Appreciated!

Can you confirm that you have also removed any customizations/custom template overrides? I may not have been explicit about that, but when switching to a default theme we’re really asking that you switch to a clean, unmodified copy.

Right now I see various comments in the HTML source that I’m assuming are either:

• The result of custom code making use of various filters/actions throughout our plugin
• Or, they have been added via template overrides
• Or, the core plugin itself has been modified

Can you confirm if that might be the case and ensure our plugins are restored to a default state / disable or temporarily remove any template overrides / disable any other custom code (whichever of those are appropriate)?

Just for clarity, here’s an example of the sorts of comments I am seeing:

Nave note => change page title style to the BetterMag theme style

I wouldn’t expect to see those on a clean installation running an unmodified, default theme and pristine copies of our plugins.

Thanks!

[Barry]

All I can do is offer our apologies: this is a priority for us, but that still doesn’t mean we can arrange for any fix to go out in our upcoming release.

That said, we may quickly follow up with a secondary release – but we do need to deliver a range of other fixes and improvements in line with our schedule as best we can.

We’ll keep you updated and are actively working on this.

[Barry]

Hi – I’m not sure if I missed the window of opportunity there but that doesn’t seem to be a default theme. As it’s a test site, is there any chance you can leave it in a default state for just a little longer?

[Barry]

We’re always happy to help but try to avoid operating directly on users’ sites unless it’s really necessary.

Is there a reason you can’t go ahead and deactivate all other plugins by yourself? It’s normally only a matter of checking off a few boxes in the plugin admin screen and choosing to deactivate them (and switching to a default theme is, similarly, pretty straightforward).

Is anything in particular about this process causing confusion that I could help to clarify in the first instance?

[Barry]

But ‘Day’ in drop down menu was intranslateble by *.po file – but I was able to translate it by modyfing the-events-calendar.class.php

I’m surprised to hear that, as again – with reference to the German translation – day is correctly translated to tag – which suggests it is translatable (I also see it in the .pot catalogue) and direct modification of the plugin code shouldn’t really be necessary.

What I’ll do though is move this thread to the translation forum and ask my colleague who’s the expert on these things to assist with any other issues re the Polish translation 🙂

[Author]

Posts