Attendee input fields not saving data

[Jesper J Nohr]

Dear support,

I have created a new fieldset and it is showing the input fields when I add tickets on the events page, but the data is not saving.

What could the issue be?

I have tested for conflicts but with no luck.

Best,
Steffen (Nohrcon Developer)

[Geoff B.]

Good evening Steffen and welcome back!

Thank you for reaching out to us.

We are sorry to hear about the new field set not saving.
I would love to help you with this topic.

As a first troubleshooting step, could you please provide us with your system information in a private reply ? (following the instructions found in the link)

Furthermore, if you could provide me with links to screenshots of the step-by-step procedure you used to Create the fieldsets and Add them to the tickets (prior to saving), that would be super helpful

Best regards,

Geoff B.

[Pasi]

I’m seeing this issue aswell, but it only happens when entering special characters to “text” field .. if the customer enters only normal “a-z” characters the text field gets saved OK. Is there any way to configure filtering rules, so the user gets a warning about incorrect/un-acceptable characters, instead of the fields not getting saved?

Thanks.

[Pasi]

To be more specific.. at least & character seems to get discarded, and everything after it..

[Geoff B.]

Good afternoon Pasi,

Thank you for sharing your findings with us. I just ran a quick test and I was able to add special characters in text fields including the & characters.

If you don’t mind, I would recommend opening a separate thread on this so that you can get the proper attention.

Have a great day!

Geoff B.

 

[Jesper J Nohr]

This reply is private.

[Geoff B.]

Good evening Steffen,

Thank you for your answer and for providing the system information and the screenshots.

Actually, I do not log into our customers website,  as our policy does not allow us to do so for several reasons, including liability.

After some testing, I have a couple of follow-up questions and suggestions to get even more specific on the cause of the issue. Thank you for your patience while we figure out what is going on.

First, I am noticing that you have a great number of plugins (which is awesome), but that also increases the risk of incompatibility (as you might know).

You mentioned earlier that you had tested for conflicts. Does that mean that you deactivated ALL of the non-basic plugins and temporarily reverted to a default WordPress theme such as twenty-fifteen ?

The reason I ask is because I have personally encountered surprising conflicts with some plugins such as Visual Composer, Advanced Custom Field Pro, Tiny MCE advanced, Capability Manager, Script plugins and Loco Translate.

Just to be clear, I am not suggesting these are the causes, just that sometimes because of the configuration or version of these, I have seen issues. As such, it’s certainly worth investigating what happens when they are deactivated (preferably in a staging environment).

 

The other question I had for you is: are you creating the fieldsets while creating the ticket or separately before hand ?

Best regards,

Geoff B.

[Jesper J Nohr]

Hi Geoff,

I believe that the issue may be a theme conflict. The theme we use uses jQuery buttons to iterate the quantity field, and the click event for adding the custom fields isn’t firing the function that adds attendees, so we just rolled our own. It appends and removes the html from the script tag to the ticket meta, creating fields which seem to have the appropriate name and lie within the html form. We used your own javascript as a model for this, the function for which is this:

var prod_id = input.attr('name').substring(9),
			$prod = jQuery('#tribe-event-tickets-plus-meta-fields-tpl-' + prod_id);

		$prod.parents('.tribe-event-tickets-plus-meta').eq(0).append(
			$prod.html()
		);

The fields are appended and removed just fine, but they do not save to the DB– I’m sure I’m missing something small, but I can’t seem to figure out what it is.

Thanks!

[Geoff B.]

Hey Steffen,

I believe you might be right in this case. I have seen my fair share of jQuery or Javascript related bugs.

Just to set expectations, as you might know, the scope of our support is mostly to get our customers started on the right track and to help them in case of issues. We unfortunately do not provide complete support for customization.

With that in mind, what I could do is have one of our Dev guys take a quick look at your code and see if they can’t get you pointed in the right direction to resolution.

Unfortunately, at this time, this will have to wait until tomorrow.

Thank you for your patience.

Best regards,

Geoff B.

[Geoff B.]

Hey Steffen,

As promised, I had one of our most awesome Dev people take a look. Here’s what their feedback is.

I think the code is based on tribe_event_tickets_plus.meta.set_quantity() (“my.set_quantity” in the source) … if that’s the case, a key difference is they are dynamically adding that chunk of HTML (so none of the listeners will fire) whereas in our own code those elements already exist and we merely show/hide them

if I’m right,

$ticket_form.on( 'submit', tribe_event_tickets_plus.meta.event.handle_submission )

could be the missing piece (of course, they’d need to determine

$ticket_form themselves)

My recommendation is to replicate our way of showing and hiding thing.

Hopefully this helps,

Have a great day!

Geoff B.

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts