[Barry]

Hi Dr Annette,

In general, I’d recommend posting your own support topic (even if the problem appears to be the same) 🙂

We did fix this, however as is often the case with translation-based problems there can be some delay before the translations themselves – which are provided by the community – catch up with the code.

In your case, I’d recommend undoing the change you made (if that was made in the Events Calendar PRO translation file) and instead updating the translation for The Events Calendar itself and ensuring ‘all’ is translated there.

Again, if you need further help with this, please do post your own support topic.

Thanks!

[Barry]

Hi Rupert,

I’m sorry to hear you are still experiencing difficulties.

At least one of those errors relates to your theme – and the others don’t really show a clear link to our own plugins – so I’m not sure they’re of immediate use, but it was worth gathering the information and we appreciate you sharing it.

As Nico requested in your last exchange about this problem, could you run through our standard troubleshooting steps? This isn’t a problem we can replicate and we aren’t seeing widespread reports from other users, suggesting that something specific to your site (your theme, another plugin or perhaps a setting) is causing this problem.

Perhaps, if you wish to avoid disruption to your live site, you (or your tech guy) could quickly set up a test site? This could be as simple as installing WordPress in a subdirectory, ie example.com/test-site, and you can then add our plugins and see if you can replicate the same issue in that environment, where no other plugins are running.

I’ve tried adding the log but it won’t let me upload any of the formats I’ve tried!

Some file formats are blocked – but you could also share a Dropbox (or similar) link by private reply. Additionally, if you place any disallowed formats in a ‘zip’ archive, you should find you are able to upload them that way 🙂

[Barry]

Hi Matt,

I’m sorry to hear that isn’t working for you.

Based on a quick look, the snippet is looking for something like ?tribe_organizer=7 in the URL whereas in your example the URL has ?organizer=7 at the end (the tribe_ prefix is missing).

Might that explain things?

[Barry]

Hi Somatic,

Thanks for contacting us 🙂

I’d like to double check that I’m understanding the problem correctly, as I seem unable to replicate. Here’s what I tried:

• I enabled the creation of accounts during checkout
• I ensured the requirement for users to be logged in before they can purchase tickets was disabled
• As an unauthenticated user, I purchased a ticket and created a new account during checkout
• The resulting attendee post was associated with the new user account (‘_tribe_tickets_attendee_user_id’ was not zero)

Am I missing any steps or misunderstanding anything needed to replicate the problem?

Thanks!

[Barry]

My wordpress settings is Norsk Bokmål

Great!

Though, that’s a little strange since we ship translations for many of the strings you highlighted. I’m not sure why they would not work in that case.

I could easily translate all strings manually if I could get the .POT file

You can find the .POT file in plugins/the-events-calendar/lang (and all our plugins basically follow the same pattern).

Do I have to disable wordpress auto translation then, so it will not override my manual translation?

My assumption is if an nb_NO translation (pulled in automatically from wordpress.org) does not already exist in wp-content/languages/plugins then your custom translation could live there.

At some future point once the WordPress-hosted nb_NO is mostly complete, it would hopefully not be a problem if it is downloaded and overwrites your custom version.

Does that help at all?

[Barry]

So here is a snippet you could add to a custom plugin or to your theme’s functions.php (less ideal – but workable!). I strongly recommend backing up your database — and knowing how to restore it — before doing this:

class Repair_Data_Fix_74105 {
	protected $old_slug = '';
	protected $new_slug = '';
	protected $candidates = array();

	public function __construct( $old_name, $new_name ) {
		$this->old_slug = sanitize_title( $old_name );
		$this->new_slug = sanitize_title( $new_name );
		add_action( 'init', array( $this, 'repair' ) );
	}

	public function repair() {
		$this->find_repair_candidates();
		$this->do_repairs();
	}

	protected function find_repair_candidates() {
		global $wpdb;

		$query = "
			SELECT post_id
			FROM   dev_postmeta
			WHERE  meta_key = '_tribe_tickets_meta'
			AND    meta_value LIKE %s
		";

		$this->candidates = $wpdb->get_col(
			$wpdb->prepare( $query, "%{$this->old_slug}%" )
		);
	}

	protected function do_repairs() {
		foreach ( $this->candidates as $post_id ) {
			$ticket_attendee_meta = get_post_meta( $post_id, '_tribe_tickets_meta', true );

			if ( is_array( $ticket_attendee_meta ) ) {
				$ticket_attendee_meta = $this->correct_ticket_attendee_meta( $ticket_attendee_meta );
				update_post_meta( $post_id, '_tribe_tickets_meta', $ticket_attendee_meta );
			}
		}
	}

	protected function correct_ticket_attendee_meta( array $data ) {
		if ( isset( $data[ $this->old_slug ] ) ) {
			$data[ $this->new_slug ] = $data[ $this->old_slug ];
			unset( $data[ $this->old_slug ] );
		}
		
		foreach ( $data as &$entry ) {
			if ( ! is_array( $entry ) ) {
				continue;
			}

			foreach ( $entry as &$submission ) {
				if ( isset( $submission[ $this->old_slug ] ) ) {
					$submission[ $this->new_slug ] = $submission[ $this->old_slug ];
					unset( $submission[ $this->old_slug ] );
				}
			}
		}

		return $data;
	}
}

To actually make it do something, you’ll need to add a new more lines right after it along these lines:

new Repair_Data_Fix_74105(
	'Original Field Name',
	'New/Current Field Name'
);

Hopefully that’s fairly self-explanatory. Refresh any screen/page on your site a few times, confirm the problem (hopefully!) is fixed, then remove the code.

Again – please! – take the time to backup before doing this.

Hopefully that provides temporary relief for this issue.

[Barry]

Hi Jennifer (and Kelly!),

Sorry for the delay in responding!

I believe your theory is correct. Bear with me while I see if there is some sort of temporary solution I can offer you (though, of course, we’ll also file this as a bug and work on a fix as quickly as possible).

Thanks!

[Barry]

Hi Martin!

With some custom coding, yes you could. Our tribe_get_events() helper function supports a venue argument and should return a list of events associated with the specified ID:

foreach ( tribe_get_events( array( 'venue' => 123 ) ) as $event ) {
    echo $event->post_title;
}

The above is a pretty simplistic example – but could be developed further and wrapped into a shortcode, widget, or used in some other way.

I hope that helps!

[Barry]

Hi again, Børge!

So I have a theory (though I’m not familiar with Norwegian so could easily be off track here). If you select Norsk Nynorsk in the WordPress settings, you will receive a set of translations in that particular form of the Norwegian language (nn_NO).

Our plugin, on the other hand, ships with what I understand to be a slightly different form – Bokmål (nb_NO). That does contain translations for the various pieces of text you highlighted, but due to the different language code will not be used by WordPress when Norsk Nynorsk is enabled.

Added to this, my understanding is that – at least currently – wordpress.org will not release partial translations. So, even if the translation hosted by translate.wordpress.org contains the translations you are interested in, you cannot necessarily take advantage of them automatically. Some sort of manual intervention would be required (which might be as simple as downloading what translations do exist, and adding them manually.

Does that help at all, or provide any insights that are of use to you?

[Barry]

Hi Will/Molly: that is true – the shortcodes we provide for that purpose are a part of Events Calendar PRO itself.

[Barry]

Hi Wim,

What’s odd is that – for me – they import successfully (featured image included).

I’m interested in learning more about your site: normally, the system information (shared at the start of the topic, or automatically if you allowed it) contains a list of active plugins and details about your theme – this appears to be missing however. If you’re willing to share this information, could you perhaps manually copy and paste this data, which is found in the Events → Help admin screen, into a private reply?

I do also note you tried deactivating all other plugins and switching to just a default theme. Sometimes, though, customers check those boxes before creating a support topic because they think they have to. For that reason I just want to confirm – did you run through that process (as outlined here) and was the result the same?

Thanks!

[Barry]

Happy to help 🙂

I’ll go ahead and close out this topic, but feel free to post new questions as needed and one of the team will be only too happy to assist!

[Barry]

Excellent – thanks for bearing with us on this issue 🙂

[Barry]

Negative patterns or exclusions are not currently supported, I’m afraid (though you could certainly propose that for future consideration). It does however support partial matching — ‘algo’ would match ‘algorithm’, as an example.

Yes, it is designed to search titles (or summaries, in iCal parlance) as well as the description.

Please note, however, that it is quite possible the fine detail of how this works will change and be tweaked over time.

[Barry]

Great – thanks Justin 🙂

[Author]

Posts