tarmogr

HAHA Good thing I still use 1.6

No, I can confirm you are not the last person using Prestashop, there atlest 10 more people. The error is still there and client also sees the error and is unable to check out

any solutions yet?

Still no solution? (ver 1.6)

---

Hi all Since the official free support has ended I have decided to make a new repository where everybody can contribute. It is based on the latest official free release 1.15.5 https://github.com/tarmogr/Prestashop-Ebay-Free I invite everyone to add their contributions and bug fixes. There are several issues that need to be dealt with in order to use this free module. Some items ToDo are listed below: Compatibility with New ebay HTTPS polycy Shipping policies are not revised properly Need to add USA site Add more countries to item location list

This one helped mee too. I had this issue about 3-4 months, very annoying. First 1.6.1.6 then updated to 1.6.1.15, still same problem. The 15 version had a bug fix mentioned related to cache in its changelog but apparently this did not solve it. The bug is still there somewhere and we need to find it.

May I ask what version are you using? I had very similar issue as described here, but with firefox, not chrome: https://www.prestashop.com/forums/topic/563269-for-those-who-find-difficulty-to-register-products-with-prestashop-1617/ For me updating to 1.6.1.15 helped You may also try the solution offered in a link above.

This is a typical bug in prestashop. I'm also unable to change the quantity of the product. Try using a different browser/machine or delete browser history.

I found a solution for that. Find: /js/jquery/plugins/jquery.tagify.js delete the content of the function so that all is left is this: /* Author: Alicia Liu */ (function ($) { $.widget("ui.tagify", { options: { delimiters: [13, 188], // what user can type to complete a tag in char codes: [enter], [comma] outputDelimiter: ',', // delimiter for tags in original input field cssClass: 'tagify-container', // CSS class to style the tagify div and tags, see stylesheet addTagPrompt: 'add tags' // placeholder text }, }); })(jQuery); Now all tags are just comma separated words which you can copy. You may have to clear cache for it to take effect.

Is there a system in prestashop to automatically generate discount code when customer writes a review?

I have exactly the same problem. Prestashop 1.6.1.10 and paypal 3.11.1. it is also very dificult to debug because firebug wont show the missing image url. is there really no solution since june 2015???? Its unbelievable that prestashop cant fix most basic issues in their official modules but continue to come out with new useless developments. There are so many elementary things that an owner has to fix and hack before going live.

Exactly the same problem as Guest_locen_* has but I have a image with "?" instead. Fresh install of v3.11.1

Hello Matte If you use the same code as I did, there is no need for separate table. You should copy the whole code above to the override/Customers.php file You then need to modify the class OSCPassword class according to magento algorithm. I used print_r($some_variable); to debug the code and see contents of variables.

It works, I have operated oscommerce from version 2.3 through 2.3.3.4 and all my test accounts from various versions of osc worked. I used eldman code but I had to upgrade it since his code is not for presta 1.6.1.10. Also if you use eldman solution you cant import passwords via prestashop CSV function (other data can), need to use phpmyadmin/sql query. code for prsta v. 1.6.1.10 override/Customer.php: <?php class Customer extends CustomerCore { public function getByEmail($email, $passwd = null, $ignore_guest = true) { if (!Validate::isEmail($email) || ($passwd && !Validate::isPasswd($passwd))) { die(Tools::displayError()); } $result = Db::getInstance()->getRow(' SELECT * FROM `'._DB_PREFIX_.'customer` WHERE `email` = \''.pSQL($email).'\' '.Shop::addSqlRestriction(Shop::SHARE_CUSTOMER).' '.(isset($passwd) ? 'AND `passwd` = \''.pSQL(Tools::encrypt($passwd)).'\'' : '').' AND `deleted` = 0 '.($ignore_guest ? ' AND `is_guest` = 0' : '')); // == BEGIN OSCOMMERCE TO PRESTASHOP PASSWORD INTEGRATION == // == BY Martin Edlman - [email protected] // == @ 27/2/2014 // == USE AND MODIFY AT WILL // == TESTED ON PRESTASHOP V1.6.X if(! $result) { // <- INVALID PRESTASHOP LOGIN, IT MAY BE AN OSCOMMERCE PASSWORD $resultOSC = Db::getInstance()->getRow(' SELECT `passwd` FROM `' . _DB_PREFIX_ . 'customer` WHERE `email` = \'' . pSQL($email) . '\' ' . Shop::addSqlRestriction(Shop::SHARE_CUSTOMER) . ' AND `deleted` = 0 '.($ignore_guest ? ' AND `is_guest` = 0' : '')); if(! $resultOSC) return false; // <- EMAIL NOT FOUND, SO IT IS AN INVALID LOGIN if(! OSCPassword::check($passwd, $resultOSC['passwd'])) return false; // <- WRONG OSCOMMERCE PASSWORD GIVEN // WE'LL UPDATE THE CUSTOMER TABLE WITH ITS PRESTASHOP ENCRYPTED PASSWORD... Db::getInstance()->Execute(' UPDATE `' . _DB_PREFIX_ . 'customer` SET `passwd` = \'' . md5(pSQL(_COOKIE_KEY_ . $passwd)) . '\' WHERE `email` = \'' . pSQL($email) . '\''); // REUSE ORIGINAL SQL TO AUTHENTICATE WITH UPDATED PRESTASHOP PASSWORD $result = Db::getInstance()->getRow(' SELECT * FROM `'._DB_PREFIX_.'customer` WHERE `email` = \''.pSQL($email).'\' '.Shop::addSqlRestriction(Shop::SHARE_CUSTOMER).' '.(isset($passwd) ? 'AND `passwd` = \''.pSQL(Tools::encrypt($passwd)).'\'' : '').' AND `deleted` = 0 '.($ignore_guest ? ' AND `is_guest` = 0' : '')); if(! $result) { return false; //incase our password rewrite does not match prestashop authentication } } // == END OSCOMMERCE TO PRESTASHOP PASSWORD INTEGRATION $this->id = $result['id_customer']; foreach ($result as $key => $value) { if (property_exists($this, $key)) { $this->{$key} = $value; } } return $this; } } class OSCPassword { private static $itoa64 = './0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz'; private static function encode64($input, $count) { $output = ''; $i = 0; do { $value = ord($input[$i++]); $output .= self::$itoa64[$value & 0x3f]; if($i < $count) $value |= ord($input[$i]) << 8; $output .= self::$itoa64[($value >> 6) & 0x3f]; if($i++ >= $count) break; if($i < $count) $value |= ord($input[$i]) << 16; $output .= self::$itoa64[($value >> 12) & 0x3f]; if($i++ >= $count) break; $output .= self::$itoa64[($value >> 18) & 0x3f]; } while($i < $count); return $output; } private static function crypt($password, $setting) { $output = '*0'; if(substr($setting, 0, 2) == $output) $output = '*1'; $id = substr($setting, 0, 3); // We use "$P$", phpBB3 uses "$H$" for the same thing if($id != '$P$' && $id != '$H$') return $output; $count_log2 = strpos(self::$itoa64, $setting[3]); if($count_log2 < 7 || $count_log2 > 30) return $output; $count = 1 << $count_log2; $salt = substr($setting, 4, 8); if(strlen($salt) != 8) return $output; // We're kind of forced to use MD5 here since it's the only // cryptographic primitive available in all versions of PHP // currently in use. To implement our own low-level crypto // in PHP would result in much worse performance and // consequently in lower iteration counts and hashes that are // quicker to crack (by non-PHP code). if(PHP_VERSION >= '5') { $hash = md5($salt . $password, TRUE); do { $hash = md5($hash . $password, TRUE); } while(--$count); } else { $hash = pack('H*', md5($salt . $password)); do { $hash = pack('H*', md5($hash . $password)); } while(--$count); } $output = substr($setting, 0, 12); $output .= self::encode64($hash, 16); return $output; } public static function check($password, $stored_hash) { $hash = self::crypt($password, $stored_hash); if($hash[0] == '*') $hash = crypt($password, $stored_hash); // PrestaShop has varchar(32) for password return substr($hash, 0, 32) == $stored_hash; } } ?>