|
Peter
|
October 19, 2017 at 3:46 pm
Hi there,
Everything has been working great to date in EE4. We were previously able to move students around at-will, and the system executed those up until very recently (days? a week?).
Effectively what is going on:Needing to move students from one course to another course date
Process used is
1. login to oursite-wpadmin
2. Go to event expresso>events
3. Find event date that registrant is currently in
4. click registrations and find registrants’ name
5. click the correct name and scroll down to change ticket/event date
6. at step 1 select new event date it says “events cannot be loaded”
Cannot proceed past step 1 to move registrant to a new course. Step 6 is the step where there is an error.
This process worked in the past. Step 1 would load current event dates/tickets and was able to proceed through all 4 steps and registrant would be successfully moved to a new course.
I see that others encountered this issue in the past, however I am not sure how to check the “browser console” for the “406 error” other people have noted in the past. In those cases it might have been something called a mod_security rule, but I am again not super technically savvy and want to approach this problem methodically as it’s on a live instance that is collecting revenue today.
In the past I have used the test-credentials form, so you may still have the valid creds on file. If not I can provide any info you need.
Thanks in advance!
|
|
Josh
|
October 19, 2017 at 5:27 pm
Hi Peter,
The methodical approach to troubleshoot this will be to temporarily deactivate any new or recently updated plugins one-by-one to rule out a plugin conflict.
If the cause is a mod_security rule, then the mod_security logs will show the ruleset that was triggered from the attendee mover form, and your webhost may be able to make an adjustment to the ruleset to allow the attendee mover form to work again.
We do not store or keep website credentials so we do not actually have access to your site. In any case you should be able to contact your host and rule out a plugin conflict.
|
|
Peter
|
October 26, 2017 at 3:13 am
OK thanks. I went to the host, asked them to review the mod_security logs, they found something that had tripped – told me they reset it – and the issue was resolved.
I was a little worried, though, after this exchange with the host:
“It could trip again in the future. Is there any way you can set it to prevent from tripping from EE4?” and the representative responded “Yes, possible it happend again, and no way to permanently disable security rules on shared server.”
So yeah, I’m not sure exactly how these rules or whatever they are work, but I am concerned at the prospect that it might not be resolve-able this way.
|
|
Tony
|
October 26, 2017 at 3:23 am
Hi Peter,
That’s a limitation with your host rather than EE, we can’t control the mod_sec rules they have in place.
I have several shared hosting packages and have not had an issue with excluding sites from certain mod_sec rules they have set up rather than completely disabling mod_sec.
|
