|
vallipow
|
August 8, 2018 at 11:20 am
When a user attempts to sign up for the Wait list from https://fasdsoutherncalifornia.org/events/wrightslaw-iep-training/#.W2sm17hlBhE, the error message:  displayed. This morning, I was able to create a Wait List entry. Would someone explain what triggered the Error, and what changed to make it do away? I am fearful that although I was successful at creating a Wait List entry, someone else will experience what happened yesterday and the day before. Please advise.
|
|
vallipow
|
August 8, 2018 at 11:23 am
I cannot see the error message in the original message. I hope this one is visible: https://drive.google.com/file/d/1H1BtLZpCdD7alQchc0gcNsQMSsZ44Fgv/view
|
|
Tony
|
August 8, 2018 at 11:57 am
Hi there,
I’ve just added a waitlist submission and didn’t see any errors, however looking on your site the hm_custom_css_js/custom.js file looks incorrect to me – http://take.ms/mfl6C
It’s a script, loading within script tags in an external file, you need to remove those script tags as its causing a JS error on the page.
The ticket selectors uses Javascript so any errors on the page can cause problems.
Do you know which browser the above error was thrown with?
|
|
Josh
|
August 8, 2018 at 12:05 pm
Hi,
I don’t see a waitlist form on the page you linked to, but it appears there was a validation issue on the form, and that might be the result of another error already on the page.
I checked the browser console and this error was present:
SyntaxError: expected expression, got '<'
which is pointing to this file on your site:
https://fasdsoutherncalifornia.org/wp-content/uploads/hm_custom_css_js/custom.js?ver=1513803612
That’s a straightforward fix: The opening and closing
|
|
vallipow
|
August 8, 2018 at 12:09 pm
Hi Tony,
Yesterday, I saw it using both Firefox and Chrome (latest versions) and IOS for mobile (latest version). My colleague, who is handling registrations, contacted me when several potential registrants called her to let her know what happened to them when they attempted to add themselves to the Wait List. I don’t know what browser they used, but because our audience for this event included many poor parents, I want to guess that at least some of them used whatever browser is available at their public library. My colleague saw the same response I did, and my guess it she used the latest Edge or IE browser.
Thanks for showing me at least one thing that seems to be wrong in a script. Although I’m the most technically sophisticated person in this nonprofit organization, I am not a coder. What I saw in the screen shot you shared seemed as if the strings in RED were broken. However, I need explicit instructions of what to edit, from the first caret to the last character, in each string to modify. Can you help?
|
|
vallipow
|
August 8, 2018 at 12:18 pm
Hi Josh, I can do anything you tell me to do, as long as the instructions are explicit. So, for
<script id=”mcjs”>!function(c,h,i,m,p){m=c.createElement(h),p=c.getElementsByTagName(h)[0],m.async=1,m.src=i,p.parentNode.insertBefore(m,p)}(document,”script”,”https://chimpstatic.com/mcjs-connected/js/users/55f7227fea3ace94b93937f18/40de93947ad048b45125bec58.js”);</script>
Do I remove “<script id=”mcjs”>” and “</script>” – that looks to me like opening and closing tags. My only concern is that there’s a lot of content between these strings, and I don’t want to assume anything.
I’m not a coder, but I follow instructions flawlessly. BTW, you only have to tell me once.
|
|
Josh
|
August 8, 2018 at 12:19 pm
This file:
https://fasdsoutherncalifornia.org/wp-content/uploads/hm_custom_css_js/custom.js?ver=1513803612
needs the first tag removed:
<script id="mcjs">
and the ending tag removed:
</script>
The reason is because <script> is an html tag and does not belong in a JavaScript file.
|
|
vallipow
|
August 8, 2018 at 12:44 pm
OKay. I edited the file and saved it in the same location with the <script> tags removed.
|
|
Josh
|
August 8, 2018 at 1:31 pm
You may need to do some further troubleshooting on this. There are a number of JavaScript errors in the console and the hash bang (#.W2tFbmaZNsY) at the end of the URL seems to be triggering one of them.
You also may need to review the custom scripts like the one you just edited. For example, what function do they perform and are they needed? Sometimes these things get added and forgotten about, and aren’t needed, and can cause conflicts.
|
|
vallipow
|
August 8, 2018 at 1:53 pm
Unfortunately, I didn’t write any of these scripts, and I don’t know what they do. Our nonprofit hired a consultant to design our site. She created the WP.org site and handed it over to us. As if it would be easy for us to maintain using the templates she created. My guess is the hash bang refers to a tab on a page that is set up in Elementor to display as either an accordion-style (with open-and-close sections), or with tabbed display.
I realize this admission makes me look like an idiot, but before this site, my only experience was using Adobe Dreamweaver or Google sites. The former was the tool used by one of my employers that, as a technical writer (that is an online help writer with a training background, not an engineer who writers software specs); the latter was what I used to create the web site that is the ancestor of the site I administer now.
I am a newbie with WP.org, the site has no blog posts (only pages), and a cheap, offshore ISP. But as I said, I’m *the* techie in the organization. The others hired the consultant because someone knows her as a good graphic designer who has web skills. She thought she was doing us a favor by setting up the Elementor templates and the host, and then handing it over. She probably did, but I wanted to provide more than just static pages. Hence, EventEspresso, NinjaForms, AddThis, and other plugins that I rely on.
After about a year administering the site, and installing plugins that I’d hoped would do the work that we need the site to do, such as events management, I think I can manage fairly well, unless there is a bug that pops up.
I realize I should have a troubleshooting resource who knows about scripting, but frankly I don’t know what I would ask them to do. One thing that seems appropriate is to trim down the number of plugins we have, but I don’t even know where to start with that.
But this is off-topic. If you have other suggestions, probably we should take it off of this thread.
|
|
Josh
|
August 8, 2018 at 2:07 pm
It’s on topic because the Wait list manager does not normally throw this type of error, and this will involve some troubleshooting to get sorted out.
Another approach you could take that will help narrow down the issue is install the Health Check plugin, then go to WP → Dashboard → Heath Check → Troubleshooting. There you’ll Enable Troubleshooting Mode, then once that’s activated you’ll reactivate Event Espresso only via the Health Check’s Troubleshooting item in the WP admin bar.
At that point, can you check to see if the issue persists?
|
|
vallipow
|
August 8, 2018 at 2:21 pm
Thanks. Where does the Health Check plugin come from?
|
|
Josh
|
August 8, 2018 at 3:13 pm
It’s hosted on wordpress.org. You can go to your site’s Plugins admin page, click Add New, type “Health Check” into the Search field, then install.
|
