Jump to content

bellini13

Members
  • Posts

    8,396
  • Joined

  • Last visited

  • Days Won

    27

bellini13 last won the day on November 12 2021

bellini13 had the most liked content!

Profile Information

  • First Name
    Bellini
  • Last Name
    Services

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

bellini13's Achievements

  1. and the email you receive includes the PDF invoice?
  2. Amazing that it is 3 years later and neither of my suggestions were implemented
  3. it appears the certificates domain is for mail.hagogreen.com ? which does not match your website domain which you said is www.hagogreen.com you should work with whomever installed your certificates
  4. But you also have ssl, sslv3, tls and tls1.0 enabled. all of which should be disabled as they are no longer secure protocols. also with them enabled, paypal may be defaulting to them
  5. who are you, and why would I send you my email address?
  6. perhaps you have a custom theme or module that does not support it. enabled debug mode and see if that provides a helpful error
  7. <?php phpinfo(); ?> I would suggest creating a php file with the above contents, and place it into the root of both of your stores and compare the differences. virtual hosts can have different php configurations At the end of the day, you need mcrypt to use Prestashop, since their Rijndael class still appears to require it. You can also do a small test on the fresh install store that is working. Locate the Rijndael.php file in the classes folder, and search for line 124, which should be this line $this->_iv . MCRYPT_RIJNDAEL_128 . $encrypted, That line is part of the generateHmac function. protected function generateHmac($encrypted) { $macKey = $this->generateKeygenS2k('sha256', $this->_key, $this->_iv, 32); return hash_hmac( 'sha256', $this->_iv . MCRYPT_RIJNDAEL_128 . $encrypted, $macKey ); } I would suggest putting a die statement at the very beginning of that function, to show that it gets called on your working store. protected function generateHmac($encrypted) { die(); $macKey = $this->generateKeygenS2k('sha256', $this->_key, $this->_iv, 32); return hash_hmac( 'sha256', $this->_iv . MCRYPT_RIJNDAEL_128 . $encrypted, $macKey ); } If this function gets called, then it will immediately stop because of the die statement.
  8. PHP can be configured differently for subdomains and/or folders. I would suggest running phpinfo on both stores and reviewing the differences
  9. No parameters I am aware of. Your hosting environment for those 2 stores must not be configured the same
  10. The Ciphering algorithm now only supports Rijndael, and the Rijndael.php class references a constant variable named MCRYPT_RIJNDAEL_128 The error you are receiving is that the constant MCRYPT_RIJNDAEL_128 does not exist. That constant is provided by the mcrypt library, which I assume you have either disabled or not installed on that test domain.
  11. 5.6 loses support from PHP this month. PHP 7.0 does as well so really you should be looking to properly maintain your store and keep it up to date being afraid to upgrade because of customizations you made is unfortunately not a good answer. And will instead leave you open to security issues
  12. That might depend on your skill level with coding. Generally I go through the release notes and change logs for Prestashop, identify the individual changes that were made so that PS v1.6 would support PHP 7.1, and then manually apply those changes to your core files. If you are not a proficient coder, then you might need to look into hiring a developer
  13. PS v1.6.1.10 does not support PHP 7.1 Your options? Upgrade to the latest version of PS v1.6 Downgrade your PHP version to PHP 5.6 or possibly 7.0 Apply patches to Prestashop to support PHP 7.1
  14. What is your exact version of Prestashop? Perhaps you should not use PHP 7.1, and should revert to a supported PHP version
  15. then perhaps you have a different issue. Perhaps you have installed a custom module that is interfering, or maybe some misconfiguration on your webserver.
×
×
  • Create New...