Posted: September 15, 2015 at 5:01 pm
When we select a ticket and click register the user is directed to a page that says: Thank you so much. Your ticket selections have been received for consideration. https://safetycoursesforkids.com/courses/babysitters-course-brampton-fortinos/ We need a resolution to this ASAP since we are completely out of business until this is resolved. Thanks! |
|
Alright I looked at your source code and apparently it is being shown because your system things I am a bot? I guess for some reason process_bot_trap is being called? |
|
Ok guys, I tracked the issue down to line 102 in EED_Bot_Trap.module.php $suspicious_timing = $bot_trap_timestamp > ( time() – 1 ) || $bot_trap_timestamp < ( time() – HOUR_IN_SECONDS ) ? true : false; I didn’t go through the whole debugging process since it was faster for me to just disable the bot trap detection, but I think the problem lies in your logic there. Please let us know when you have a fix for this so we can re-enable line 36. |
|
Also not too sure if this variable debugging data will assist you [15-Sep-2015 23:56:22 UTC] Bot trap timestamp: 1442361376 |
|
Hey Susan, That’s pretty strange. What web browser (and version) were you using when this happened? Not sure, but it could also be something related to your WP timezone settings. I’ll leave a note for the developers in the morning. |
|
Hi Seth, I was using Chrome. Thanks! |
|
Hey Susan, Our developers are looking into this. Thanks! |
|
Thanks Seth! |
|
Hi there, It appears that the encryption for the bot trap data is getting highjacked on your site. So we’ve added an option to enable or disable Encrypt Bot Trap Data in version 4.8.10. After you update to 4.8.10, you can disable the encryption by going to Registration Form Admin Page > Settings Tab, then set Encrypt Bot Trap Data to No. |
|
Hi Josh, Can you explain how it is getting hijacked? Just curious… |
|
September 22, 2015 at 10:06 am I can’t explain why, it appears to be something unique on your server. We could see that the resulting input value from viewing the source (after decryption) was way out of whack, which led to the problem you were seeing. So it was decided to add an option to allow for disabling the encryption. |
|
The support post ‘HUGE PROBLEM AFTER Update’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.