datakick

I see not really an alternative to the kind of solution that I proposed in this post: keeping a compatible Smarty version (that means lower than 3.1.28 as far as I can see) and fixing it so that it runs under PHP 7.2. isn't it better to fix the newest smarty version instead?

Build-in debug mode is a very useful tool, but it's not recommended to turn it on in production because it can leak sensitive information about your website. This free module is here to help you with this shortcoming, as it allows you to enable debug mode only for specific sessions. This module creates secret url, and anyone who access your site via this url will browse with debug mode enabled. This way, you (or anyone you share this url with) will have access to debugging information, yet your normal visitors will not be affected. Download link

uff, you are running bleeding edge php version on non-supported operation system. That's a killer combination. Thirtybees is not yet even 100% compatible with php 7.2. I suggest you downgrade to 7.1 if possible

what's your php version?

@Traumflug how do you plan to tackle database migration? Say 1.0.9 will introduce new db column for table A, and foreign key to this column from table B. how will be these db changes created when migrated from 1.0.8 to 1.0.9? what happen when you downgrade from 1.0.9 to 1.0.8 what about order of modification (for example we need to drop constraint before we drop column itself)?

@rubben1985 these particular changes are fine. We don't know, of course, how does the external file look like. I really think that some module or vendor library introduces class named Validate, and that this class gets loaded at the very beginning of the request. That would prevent loading Validate core class, and results in this kind of error. Search for class Validate

as long as the module is for ps16, it should be compatible

Search for 'prestashop checkout extra fields module', you should be able to find few of those (paid).

Could you elaborate?

That seems to be problem related to supercheckout module. I'm afraid nobody can help you without the knowledge of its source code

Also, the same error message is also saved inside your log directory within your thirtybees root. So you can always ftp and look for errors there.

That does not help much. Copy error, then go to Advanced Parameters > Logs, and paste it to Decrypt an exception message. It will show you the error message in readable format.

What does the error log says?

@Chandra please look into tb_configuration table and verify that PS_MAIL_PASSWD is correct. Maybe this problem is related to configuration escaping issue... although not likely

Not necessary, it's simple fix, already submitted

It's probably problem with your infrastructure. I've just tested stmp (mailgun) on 1.0.8, and it works as expected.

This problem originates from referralprogram module. I'm pretty sure this exception will be thrown even on tb1.0.7, if this module is installed and url does not contain &sponsor=xxx parameter. The reason this exception is thrown is because Tools::getValue('sponsor') returns false when 'sponsor' parameter is not part of the request. This invalid value is then passed to cipher tool for decryption. Blowfish would return null for invalid input (boolean type), while PhpEncryption will throws exception. This should be fixed in the core -- the behaviour should be consistent. But the module itself should be fixed as well -- there's no need for decryption call, if we don't have anything to decrypt.

The error message is complaining about missing method Validate::isJSON. That's very strange, because this method is clearly there. There are only two explanations I can think of. you have modified core class classes/Validate.php and removed/renamed this method. That's very unlikely. The other possibility is classname conflict. It's possible that some module have class with name Validate, and this class gets loaded at the very beginning of the request. Thirtybees uses lazy loading autoloader, which means it will load any core class only when needed. In this case the core class would never be loaded, because class with the same name exists. But this third party Validate class does not contain isJSON method. This is another way to override core classes. Unlike normal overrides, which extends core class, this method replace the whole core class. Very dangerous, and officially not supported. But some module developers do this kind of things

@movieseals you can download release 1.0.7 and use Configuration.php file from that version

@wakabayashi unfortunately it's a real problem in tb core with incorrect escaping of configuration value. This module stores serialized json object into configuration table. Due to improper escaping, this json can't be decoded when read back from the configuration. That triggers cascade of errors and problems, one of them manifests as smarty notices. But the module is indeed unusable because of this bug

I've tracked this to another issue in 1.0.8 release. @movieseals if you need immediate fix, you can revert this commit: https://github.com/thirtybees/thirtybees/commit/12d2d6c5f9f8c6d821603fba011e9de03eb1f70d

@elund it seems to me that the captcha is working on your site. I've just performed simulated attack -- tried to submit new message via curl, with invalid captcha validation token. My attack attempt was successfully intercepted by the captcha module, see the screenshot. How many spams are you receiving? PS: from your screenshot it's apparent that you are not using latest version of the module. Maybe that would help

@movieseals sure, send it to me. I'm curious.

hard to tell without the module source code

I've just went over the code and found one bug. If the Login attempts is set to non-zero number, the validation for Contact controller is always skipped. So make sure it's zero until this bug is fixed.