Weird stuff happening when using a fieldset twice on one page

[Carsten Altena]

I’ve made a page and added a couple of events, twice of which use the same ticket fieldset.
This causes some weird stuff to happen. Please look at the source code of the pages below.

The page content in the main WordPress loop randomly gets mangled up inside the “script class=”tribe-event-tickets-plus-meta-fields-tpl”” portion of the page. Just search for the phrase “<div class=”mainsingle”>” on this page:

http://www.hondenschoolshyla.nl/puppycursus-test/

And compare this to this page:

http://www.hondenschoolshyla.nl/puppycursus-test2/

which uses the same content (starting with “<div class=”mainsingle”>”). This time, I only use the ticket field set on one of the tickets, and nothing gets mangled up. But if I add the same ticket field set to the other ticket, same thing happens as in the first page.

These are the things I’ve tried, with no luck:
– Change the theme (one of the standard WP themes): doesn’t fix it.
– Increase the memory limit in WordPress to 256 mb; doesn’t fix it.
– Change the content of the page; still happens.
– Deactivate all plugins except of course your plugins + woocommerce. No luck.

So weird. Any ideas here?

[Cliff]

Hi, Carsten. Thanks for your detailed request.

Are you adding tickets to a Page and not using The Events Calendar‘s Events?

Are all your plugins up-to-date?

[Carsten Altena]

Hi Cliff,

Plugins are up to date but as I said, it even happens with all the other plugins disabled.

I’m adding the event to a page, when editing the page there’s the box “Tickets”. So not using the calendar plugin.

[Cliff]

Could you please share your System Information in a Private Reply. That will give me a lot of extra information to help troubleshoot this.

Additionally, could you please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this?

Of course, we always recommend restorable database and file backups before modifying anything on your site.

[Carsten Altena]

Hi,

like I said in the original post, I already tried the “deactivate plugins and switch to standard WP themes” thing. But I’ll look into the guide tomorrow, hopefully there are some things I haven’t tried yet!

I’ll share my system info privately in a second!

Thanks so far. Hopefully we’ll find a solution.

[Carsten Altena]

This reply is private.

[Cliff]

I enabled tickets for Pages, created a Woo ticket on a page and saved the fieldset, then added a Woo ticket on a different page and used the saved fieldset. The Woo ticket on both pages displayed properly, along with the Attendee Information fields.

Could you please re-try Testing for Conflicts Mode and share your system information report while in Testing for Conflicts Mode?

[Carsten Altena]

This reply is private.

[Carsten Altena]

Hi Cliff,

I’ve done everything at once and just sent my system info report privately.

– disable plugins except for of course your tickets-plugin and woocommerce.
– 2017 WP theme enabled
– Updated the plugins

The problem persists.

I’ve found that the problem has something to do with the ticket fields. If I add a field set to a ticket past a number of fields, strange thing happen. Check out the attached screen shots. On the first screenshot (01) I have a bunch of tickets added to the page, some of the tickets have a couple of fields. In the second (02) I added a couple more fields to another ticket. Now my main content miraculously appears IN THE MIDDLE of the additional form containing the extra fieds… so strange! If I add even more fields, the places where my main content pops up is different everytime.

Could this be a database problem? Or a PHP parser problem?

[Cliff]

Carsten, thanks for your effort but your last reply included the System Information Report as if you did not follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this. (Of course, we always recommend restorable database and file backups before modifying anything on your site.)

Please do test if the issue’s happening when your site is in this mode. If the issue does not happen when testing, please re-enable your plugins and theme to determine the conflict via the process of elimination and report back your findings.

Thank you.

[Carsten Altena]

This reply is private.

[Carsten Altena]

Hi Cliff,

hope I did it right this time:

1. Switched to Twenty Seventeen
2. Disabled all plugins except for Event Tribe and Woocommerce
3. Added another ticket to a page, causing the error
4. Copied the system info and replied to this thread privately
5. Switched the site back 🙂

Hope you can find something in the system info!

[Cliff]

This reply is private.

[Carsten Altena]

Hi there,

Great news: I found out what is causing this. Tried a couple of things:
– At first I thought it was my database, some sort of corruption, but this was not the case.
– Then I made an exact copy and moved the site to a completely different host. No change.
– Then I did a clean install with the bare minimum plugins, and added just one page to which I added tickets. Same problems occured.

By now I knew it had nothing to do with my server, database, theme, other plugins etc.

I narrowed it down to: creating a fieldset with a checkbox without specifying a “label”. If you use a fieldset like that twice on a page, the weird stuff happens.

So the solution is basically: when using checkboxes in fieldsets, always specify a label. I omitted the label because I didn’t want the label text to be displayed above the checkbox.

So this is a bug in the plugin I guess?

[Cliff]

Great sleuthing!

I tried to recreate the issue and a checkbox field without a Label just doesn’t show up at all–on both an Event or a Page:

• back-end: https://cl.ly/0W053636201D
• front-end: https://cl.ly/1q2j0r122W1D

Please let me know your thoughts about this.

[Author]

Posts