yaniv14

So basically your original problem was not related to nochex module but was a problem with Knowbands Super checkout module? Now that you disabled supercheckout module both your payment modules works fine?

If Paypal module throw the same error than I guess the error caused by the supercheckout module. Try to disable the module and revert back to standard TB checkout

can you post the content of this file: modules/nochex/nochex.php

I just went to your site and I am getting error 500 when going to checkout. please check your php error log or check this attached log. exception_2020428292.txt

Care to give access to your back end so I can take a look?

can you put "9999" in "Will be applied when the weight is < " and also mark "All" and put "0" in the amount column, which will mark all continents and add "0" amount to them. and than save and see if it works

send a screenshot of section #2 "Shipping locations & costs"

can you send a screenshot of how you setup your carrier price range?

Go to modules -> payment. and check all restrictions and payment methods.

Look under preferences -> general and/or localization->currency

are you sure you are changing in the validation file? all you need to do is to change from: $this->module->execPayment(); to $this->module->execPayment($cart);

As you can see this variable is not even being used in the function. anyway just do this and you should be fine.

This error has nothing to do with newer version of TB. this is related to PHP7+. the message is very clear about the reason. look at file: modules/iemt/controllers/front/validation.php on line 51. this function require 1 argument which is not passed. this function exists on file: modules/iemt/iemt.php at line 237, now i can't tell much about what is expected for $old_cart. but i guess you can try to pass the cart from validation. so try changing line 51 in validation.php file to: $this->module->execPayment($cart); if you can show the rest of the code after line 247 it will be better.

I guess you can remove/hide it from the relevant templates when you have a button or form related to registration. Like: authentication page, checkout page...

Its hard to tell without seeing the module or looking at some error log info. My guess that it something minor, as long as it is working on php 7+

My guess would be something related to your server/hosting. I never had this kind of error. I know some hosting use Apache webserver with mod_security that might cause problems.

are u using any module for checkout?

create a file "ContactController.php" and place it inside "override/controllers/front" folder. the file should look like this. <?php class ContactController extends ContactControllerCore { public function postProcess() { $email_address = Tools::convertEmailToIdn(trim(Tools::getValue('from'))); $emailParts = explode( '@', $email_address ); $emailDomain = end($emailParts); if ($emailDomain == 'qq.com') { header('HTTP/1.1 403 FORBIDDEN'); header('Status: 403 No China here!!!'); header("Location: https://www.qq.com/"); } return parent::postProcess(); } } i think it should work, don't have time to test it right now. you should delete cache/class_index.php as well

Its better to have it as an override. also delete cache/class_index.php file

If all attacks comes from the same ip address than you can block the ip address on your nginx/apache server block. if not and you need to block it on the code level, than you should make an override to ContactController postProcess function and check the email domain and block it there. $emailParts = explode( '@', $email_address ); $emailDomain = end($emailParts); if ($emailDomain == 'qq.com') { // do something }

check that the db table collation is utf8

Start by blocking the ip address and see if this bot attack again from different ip

Please post this in github as a bug.

All these speed test tools. Gmetrix, Google page speed, YSlow...... are pure garbage that all they do is provide job for SEO companies. I never run those tests on my sites. You can tell if your site is running fast or not. btw: do you know how much loading time you will save with the compress version (61 bytes less)? you will save about 0.000000000000001 second.... so you should defiantly go for it 🙂