Card Fieldgroups not working properly

[Stefan Boelts]

Hello
We have got the problem that when we want to edit a card field group that a click on the plus button for a new field are often ignored so that its impossible to add new fields.

The other problem is that the fields are not displayed anywhere while buying a ticket.

[Stefan Boelts]

Please inform me on thread updates to [email protected]

[Cliff]

Hi Stefan.

Forum reply notifications only get sent to the address in your My Account page. If you want replies to go to a different email, updating your account’s email is the only way our forum could send them to another email.

To solve your issue, I’m guessing there’s a plugin or theme conflict — specifically, a JavaScript issue.

I’d suggest following our recommended troubleshooting steps:

There might be some new updates available. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

• Downloads / Version Numbers
• TEC Automatic Updates
• or TEC Manual Updates
• WordPress core updates

Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.

If it is, please follow our Testing for Conflicts Guide (basically switch to TwentySixteen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG and share any PHP errors you see while changing tickets quantity, navigating your site’s home page, events page, single-event pages, and any other of your site’s pages relevant to this ticket.

Then, please share your System Information (while in Testing for Conflicts mode).

You might also see if you can spot any console errors at your site. (If needed, you may reference our KB article Using Google Chrome Developer Tools.)

Let us know what you find out.

Thanks.

[Stefan Boelts]

Thanks for your answer.
After using the actual harddisc on another test computer everything works great.
So I switched into DEBUG mode on the production system and the error was away even after switching DEBUG mode off everything is working great now 😉

[Cliff]

Stefan, thanks for working hard to resolve this. Have a great day!

[Author]

Posts