Edit the DB to allow larger addresses for that column, then edit the following locations to allow for larger addresses:
Code: Select all
root@ubuntu:/var/www/store/catalog# grep -r 64 *
controller/account/address.php: if ((strlen($this->request->post['address_1']) < 3) || (strlen($this->request->post['address_1']) > 64)) {
controller/account/create.php: if ((strlen($this->request->post['address_1']) < 3) || (strlen($this->request->post['address_1']) > 64)) {
controller/checkout/address.php: if ((strlen($this->request->post['address_1']) < 3) || (strlen($this->request->post['address_1']) > 64)) {
controller/payment/protx.php: $crypt = base64_encode($output);
language/english/account/address.php:$_['error_address_1'] = 'Address must be greater than 3 and less than 64 characters!';
language/english/account/create.php:$_['error_address_1'] = 'Address 1 must be greater than 3 and less than 64 characters!';
language/english/checkout/address.php:$_['error_address_1'] = 'Address 1 must be greater than 3 and less than 64 characters!';
Is Daniel asian? 
Curious, varchar is used as the data type for address_1 and address_2 but I thought that varchar doesn't zerofill if you don't use the entire 255 chars. Isn't it a variable-length string type? Why then would one need to limit its length? You might get some weird addresses from people who live in the middle of nowhere and those can be very long...
Curious, varchar is used as the data type for address_1 and address_2 but I thought that varchar doesn't zerofill if you don't use the entire 255 chars. Isn't it a variable-length string type? Why then would one need to limit its length? You might get some weird addresses from people who live in the middle of nowhere and those can be very long...
Is the length eliminated in v1.1.9?Daniel wrote: 這問題會更正於V1.1.9!
Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 78 guests
