Participant information missing

[bruce williams]

We occasionally have a ticket purchase which is missing participant information even though it is correctly configured (other tickets have the information). I’m guessing that this is due to the participant information fields using Javascript to display; the tickets with missing participant information being due to Javascript being disabled when purchased.

Questions:

1) there is apparently no fallback method for collecting participant information if Javascript is disabled (I tested this and the fields don’t display AT ALL when Javascript is disabled). If this is the case, is it possible to code a fallback method for collecting participant information in the event of Javascript being disabled?

2) if there isn’t a way to code a fallback method to collect participant information, is it possible to include a notice to the purchaser that they MUST turn on Javascript to purchase tickets?

3) if all of the above are not options, is there an easy way to include a generic Javascript test that would display a notice to users on event pages that to purchase tickets they MUST enable Javascript.

I did not deactivate plugins nor revert to the Twenty Fourteen theme as this is obviously a Javascript issue.

Thanks!

[Brook]

Howdy Bruce,

That’s a great question. You’re undoubtedly right, those are probably NoScript users buying tickets from you.

1) there is apparently no fallback method for collecting participant information if Javascript is disabled (I tested this and the fields don’t display AT ALL when Javascript is disabled). If this is the case, is it possible to code a fallback method for collecting participant information in the event of Javascript being disabled?

I’m a huge believer in supporting users who have disabled JavaScript when possible. Unfortunately I do not see a way to add compatibility for this. Since our plugin allows you to purchase multiple tickets at once, and each will have their own meta fields, it is not really possible to show all of those fields on the page. You need something like JavaScript which can dynamically add or remove fields based on the quantity of tickets you’ve purchased.

You could introduce two steps to this process. A user selects the quantity, hits submit. Then they are sent to another page with the appropriate amount of fields. While this is possible it will take a lot of custom coding to make it happen. Probably too much for you to be interested in investing in this route.

2) if there isn’t a way to code a fallback method to collect participant information, is it possible to include a notice to the purchaser that they MUST turn on Javascript to purchase tickets?

That should be easy to do. The HTML <noscript> tag is built for just this scenario. If you paste this in your theme’s functions.php file, it will add just such a notice:

https://gist.github.com/elimn/f0e6b8ee3ee87df1ee1ee2937947619c

Did that do the trick?

Cheers!

– Brook

 

[bruce williams]

The <noscript> modification did not work for me.

[Brook]

Howdy Bruce,

Thanks for testing that out. I just retested and it is working great if I go and manually disable scripts in Google Cheome. How are you testing this out? Do you see the <noscript> element inserted in the HTML source code?

Cheers!

– Brook

[bruce williams]

I’m using a child theme of Kallyas (https://themeforest.net/item/kallyas-responsive-multipurpose-wordpress-theme/4091658) and adding the code to the functions.php of my child theme.

The <noscript> tag does not appear in the HTML source of the event page when using our child theme nor when using Twenty Fifteen.

I’m omitting the leading <?php in your code snippet from above as the functions.php file already includes that.

[bruce williams]

Can’t this functionality just be added to the plugin directly instead of trying to hack it in via functions.php? That would seem to be the “correct” way to do it.

I’ll hunt around in the code to see if I can figure out where the relevant Javascript is located and modify the code myself.

[Brook]

Howdy Bruce,

I am sorry that the code is giving you difficulty. To help I just packaged that into an “extension” —  a small plugin you can download, install and activate. Once activated it should show the <noscript> on your single pages:

Event Tickets Plus Extension: Attendee Meta Noscript

Can’t this functionality just be added to the plugin directly instead of trying to hack it in via functions.php? That would seem to be the “correct” way to do it.

We are certainly considering including this, we are also considering making the attendee meta page a separate page for noscript users. The solution is currently in the strategy and planning phase, alongside literally hundreds of other small feature ideas we see great potential in. From there it will be sent to a designer, then a developer, then finally QA. As you might imagine the whole process can easily take months.

Hence why I was interested in getting you a snippet or extension you could use today.

Does that all make sense? Did that work for you?

I typed the above response up on the 11th. But, it evidently did not go through. It’s probably human error 🙁 I might have forgot to press submit or closed my browser tab too quickly after clicking submit. My apologies.

Cheers!

– Brook

[bruce williams]

I looked in the “Extensions Archive” for the extension you mentioned having created and found nothing. Am I looking in the wrong place? I did not see a link to the extension in your response…

Really appreciate your quick response and work in addressing this issue. Thanks!

[Brook]

Howdy Bruce,

I am sorry you were having trouble finding the link. It is just under the second paragraph in my response. Maybe you had just viewed my response in your email inbox? I believe that the emails get stripped of some HTML elements, particularly ones that might get the email marked as spam.

Here is the link again: https://theeventscalendar.com/content/uploads/2017/02/tribe-ext-noscript-attendee.zip

 

Let me know if it gives you any trouble. Cheers!

– Brook

[bruce williams]

Still nothing.

I loaded the plugin to our development site at devel.reveresriders.org and the page source does not contain a <noscript> tag. Even switched to Twenty Fifteen theme to make sure this wasn’t a theme issue.

I don’t currently have the time to pursue identifying whether this is a plugin issue or not.

[Brook]

That is strange. I just tried replicating your exact settings and it is working great on a couple of other sites.

If you have a caching plugin, or just a server side cache, maybe that needs to be cleared?

But I understand if you don’t have the time to mess with it. If it’s not urgent for you, at least it is something we will address as soon as we can in the plugin. As I said at the outset waiting on it to become built-in might take a while, but it should be a nice solution when it does come.

Cheers!

– Brook

[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