traceyweb

I copied the site to a staging server and before checking plugins I thought I would check to see if the payment fields displayed on the ticket and they did….

So I checked with hosting support and it turns out it was an issue with CDN/web optimisation. When I disabled that and reloaded the ticket page everything worked as normal.

Thanks for pointing me in the right direction.

Also noticed these javascript errors in the console:

Uncaught ReferenceError: tribe is not defined
at tec-ky.js,qver=5.1.15.2.pagespeed.ce.LCkHx_tRx4.js:2:1

Uncaught ReferenceError: tribe is not defined
at checkout.min.js,qver=5.7.0.pagespeed.ce.qORiOSodgd.js:11:1

Hi Darian

Thanks for your quick reply. I tried both those options but neither worked.

On the website where it does work I didn’t set up a webhook. It says “Webhooks not validated yet” but it still works.

I set up the webhook on the site it’s not working on and tried again but it didn’t work. I then added the code to the wp-config but still nothing.

I’m not sure why it works on one website but not the other when they’re both using the same theme.

Thanks. I had given the ticket the name of the event but have now added the date as well so we can differentiate between events with the same name on different days. Simple now you pointed it out!

Yes. I just did some more testing and it seems the plugin Contact Form 7 Connector is the one causing a conflict (even though I disabled that before). I’ve rolled that one back and it’s all working. So it wasn’t this plugin that was a problem, sorry to bother you ??

Oh I see. Sorry I didn’t see that. I’ve got it working with CF7 so that’s OK.

That’s what I suspected so I did use a different browser, cleared cache, made sure I was logged out and it still doesn’t show the forms. When I use a browser where I am logged in I see the message “you are already logged in”. So if I was logged in using the other browser shouldn’t it also display that message?

I had someone else check it on their computer and they also don’t see the login form.

This was on the default login page [arm_form id=”102″ logged_in_message=”You are already logged in.”

In the CSS it has this on the form:

.ng-cloak, .x-ng-cloak, [data-ng-cloak], [ng-cloak], [ng\:cloak], [x-ng-cloak] {
display: none!important;
}

I also followed the configure plan + signup page but it doesn’t display a signup form.

??

Thanks @ashfame. The hosting company did a purge of the cache (even though I’d already done one) and this seems to have fixed it.

Thank you. It looks like there was a conflict with the Tutor LMS Elementor Addons plugin. When I disabled that things started to work correctly.

So this “magically” resolved itself. The user was accessing a free course but after I added the user to a paid course they could see lessons. Why that would be?

In addition to that, when the user logged out there is nowhere for him to login again. The default profile page said “This user does not public their profile.” So I changed the setting “Publish profile” to “User course data will be public”. Now it displays a page with a blank profile and 0 courses – but no login form.

I even tried creating a new Profile page just in case the default page wasn’t working but still the same.

I was concerned this setting meant profile information would be public so that’s why I hadn’t enabled that option. So what does it mean? And where do I find the login form?

I found the dashboard page but the issue is someone pays for the course in Woocommerce but then how do they get to the course? The customer receives an email with a link to the course but it just shows the course registration page which asks them to pay again.

Thanks, that worked ??

Yes that is set up but if you click the reset button all the question answers are erased. So if it’s a 10 question quiz and he just got one question wrong he has to answer all 10 again. I need the person to be able to edit the one question he didn’t get right and resubmit – with all other answers still there.

Yes, plugin definitely needs an update. I had to rollback WordPress to 5.4 to get it working again.