Multiple bug reports

[Robert]

I have a few bugs to report:

1) I’ve been encountering a fatal error that only seems to happen when you already have a ticket in your cart for some time (seems like at least a day), then attempt to add another ticket to your cart. The errors persist every time you try to add a new ticket until you remove the existing ticket from your cart. I don’t think this is exactly common for most users to do, but I have had it happen to someone other than myself. Note: After the last time this happened (earlier today) I updated the plugin, so it may now be fixed – there hasn’t been sufficient time to leave a ticket in my cart and see if it happens again – if it does I’ll update this post to confirm it still exists.

Also, while testing this I at one point logged this error:

[08-Dec-2016 18:47:18 UTC] PHP Catchable fatal error: Argument 1 passed to tribe_array_merge_recursive() must be of the type array, boolean given, called in /home/***/public_html/wp-content/plugins/event-tickets-plus/src/Tribe/Meta/Storage.php on line 97 and defined in /home/***/public_html/wp-content/plugins/event-tickets/common/src/functions/utils.php on line 14

I’m not sure if this is the same issue however as this one white-screen-of-death’ed me, while the normal ticket error throws a 500 error.

2) Post update the function “toggle_js_class” in \wp-content\plugins\event-tickets\common\src\Tribe\Main.php (line 280) has malformed JS which adds the text ”; to the end of every page. The code for this function is:

	public function toggle_js_class() {

?>

		<script>

( function ( body ) {

			'use strict';

body.className = body.className.replace( /\btribe-no-js\b/, ‘tribe-js’ );

		} )( document.body );

</script>”;

		<?php

}

And you can see the extra characters right after the closing script tag. I have removed these from my copy of the plugin as a temporary fix.

3) In both the current and previous version of the plugin the settings page is horribly broken visually, I will attach a screenshot. The problem appears to be related to the CSS attached to .tribe-settings-form legend, removing the “float: left;” style fixes this particular issue but of course causes the input field to wrap to the next line. I haven’t been able to figure out exactly why it would cause this problem though. I am using the Beta channel of Google Chrome in this screenshot – I’ve not tested this in other browsers as I can get around it using the inspector, so it’s only a minor inconvenience for me.

[Cliff]

Hi.

Thank you for your detailed question.

In our forums we keep our threads focused on just one issue at a time to ensure we fully answer each of your questions/issues. Please keep this in mind for the future and start a new thread for your additional questions from this thread. Thanks for your understanding, and I’ll reply here only your second question. Please re-post your first question in a new thread.

Thank you for reporting this. I found the errant code at https://github.com/moderntribe/tribe-common/blob/4.3.4/src/Tribe/Main.php#L287

This is a rare scenario where it’s probably okay to just edit the core plugin files to remove this little typo from all 3 of these files:

• /wp-content/plugins/event-tickets/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/common/src/Tribe/Main.php
• /wp-content/plugins/the-events-calendar/vendor/tickets/common/src/Tribe/Main.php

I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

I apologize for this issue and appreciate your understanding and patience.

[Nico]

Hi there,

I wanted to let you know that we just released a hotfix that includes a fix for this bug. Please update The Events Calendar and/or Event Tickets to version 4.3.4.1 and let us know if this makes the issue right in your site!

Best,
Nico

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts