Jump to content

usengines

Members
  • Posts

    47
  • Joined

  • Last visited

Profile Information

  • Location
    Tampa FL
  • Activity
    User/Merchant

Recent Profile Visitors

3,768,580 profile views

usengines's Achievements

Newbie

Newbie (1/14)

2

Reputation

1

Community Answers

  1. We get the same malformed response on all our sites on Hostwinds but not on Hostgator? Our transactions are set at 3.1 at Authorize.net. Posted the error on the developers page on GitHum but have received no comment.
  2. Running into the same problem with 1.6.1.24 Authorize,net AIM 1.5.7 Also enhanced version 1.5.8 by DH.
  3. The basic problem is that the ID in CSV only accepts numbers. This produces another problem in that the ID then is different from the manufactures and that makes it difficult to maintain a shop when products are being discontinued, superseded and added. One would think that the solution then would be to use the UPC or EIN number, however not all the products have those assigned.
  4. We have more than 100,000 products to import. When we import similar products such as models in a series PrestaShop keeps overwriting one item with another. For instance we have 104M02-0021-F1 and 104M02-0196-F1. If we import either of them using the model number as the ID and the name and then import the other it overwrites the other as prestashop is only using the first three characters of the number. More dangerously it keeps the price of the first item imported which is often much different than the other depending on such features as electric start. We have tried using the reference as the key but it still overwrites the other product. We are using 1.6.23 as the most important modules we use are not compatible with 1.7 namly Authorize AIM and both the FEDEX and UPS carriers.
  5. After upgrading to 1.6.1.2 customers cannot save address. After hitting save the add new address form comes up again blank accept for customer's name but no address is saved in my addresses. One customer has 13 addresses all blank. Address update does not work either, after edit, blank again. You also cannot delete the black addresses in My Address.
  6. After upgrading to 1.6.1.2 customers cannot save address. After hitting save the add address form comes up again blank accept for customer's name but no address is saved in my addresses. One customer has 13 addresses all blank. Address update does not work either, after edit, blank again.
  7. AuthorizeAIM module is not connecting with Authorize.net though the keys are correct and work on eBay. Unlike the FedEx or UPS con not modules AuthorizeAIM does not provide any feedback that the module is on line and working. Currently using 1.6.1.1.8
  8. Do you know whether Authorizeaim module uses tls 1.02? We are using authorize.net and the authorizaim module
  9. I copied a working prestashop version 1.6.1.7 from one host and ftped it to another host for use on another similar domain. I changed the settings in the config file and attached a copy of the database changing the shop_url folder to matche the new site. Now I am getting this error. [30-Dec-2017 13:49:23 US/Eastern] PHP Fatal error: Class name must be a valid object or a string in /home/sport/public_html/briggsengines/classes/controller/Controller.php on line 134 I also made copies of working prestashops already on the site, copied the original database and attached it to the new shop and n ow I am getting the same error there as well? I compared the classes directory with the working one in both cases and they are identical?
  10. This occurred upgrading from 1.6.1.2 to 1.6.1.3 but has happened with previous version upgrades. If you get a situation where you are not getting an error message stating that your email used or password is wrong but the program times out before reaching the admin with no error message leaving you at the log in screen. The solution is this: Use file manager or ftp program and go to the shop, then open config and edit settings.pdf. Make sure everything is accurate especially the folder for the shop. Open the database using myphp (make sure that you are not trying to use the same database for two shops unless you are using multi-store) admin and go to the shop url, make sure the shop url is accurate as if it is not it will create a conflict. If you are using a directory for your shop such as prestashop make sure there is a forward slash before and after the sub-directory. If everything is accurate go to employee and edit. Now go back to the settings.php edit in the file manager and delete the code in the cookie but be careful you do not delete the whole line or the punctuation characters just the numbers and letters in the cookie code. Then go back to the php admin of the edit of employee and current password code and put in the same password you have in the settings,php without putting anything in for the cookie key then save it making sure you use md5 for the encryption settings in the drop down list. Then go down and hit go. Go back to your login page and whala you should now be able to log in.
  11. If you get a situation where you are not getting an error message stating that your email used or password is wrong but the program quits before reaching the admin with no error message. The solution is this: Use file manager or ftp program and go to the shop, then open config and edit settings.pdf. Make sure everything is accurate especially the folder for the shop. Open the database using myphp (make sure that you are not trying to use the same database for two shops unless you are using multi-store) admin and go to the shop url, make sure the shop url is accurate as if it is not it will create a conflict. If you are using a directory for your shop such as prestashop make sure there is a forward slash before and after the sub-directory. If everything is accurate go to employee and edit. Now go back to the settings.php edit in the file manager and delete the code in the cookie but be careful you do not delete the whole line or the punctuation characters just the numbers and letters in the cookie code. Then go back to the php admin of the edit of employee and current password code and put in the same password you have in the settings,php without putting anything in for the cookie key then save it making sure you use md5 for the encryption settings in the drop down list. Then go down and hit go. Go back to your login page and whala you should now be able to log in.
  12. We are having a problem with importing into 1.7.1. The csv file of 2000 products is 100% verified but then stops on the actual import. Unlike 1.6.1.3 it will not import anything once an error is found. If you go back to the csv file and delete the products that are indicated is errors it finds four more and stops. Errors occurred: 1707593SM (ID: 1707593SM) cannot be saved 1720812SM (ID: 1720812SM) cannot be saved 1754211YP (ID: 1754211YP) cannot be saved 325796MA (ID: 325796MA) cannot be saved 41740MA (ID: 41740MA) cannot be saved 1.6,1.3 will skip the problems and import all remaining products.
  13. We can't even get back into the admin on two shops we "upgraded" to PrestaShop version 1.6.1.5. After the upgrade when we tried to log in there were no message errors just blinked and sat there. The only way we could get back in and take it out of maintenance was to add the domains to multi-shop in a working 1.6.1.4 with thousands of fewer products.
  14. The obvious places to check are under the config folder Settings.inc.php you have to make sure you have the whole database name and user name. Most hosting companies have a prefix they put in front of the name for instance your_host_ID_prest1 same with the user. If you have copied prestashop and the database and put it on the new hosting site the prefix for the database will change. Second of course you have to make sure that you have assigned the access rights for the user to the database. We often will create a new prestashop installation and then change the original database to one used on another one of our sites to avoid having to upload 100,000+ products. Sometimes even though you assign rights to a user it still will not work. We have found that the most likely users to work is the one used to install the original program on the original database. Of course you have to reassign rights for that user to the database that you now want to use. The second most likely to succeed is the user name that was being used on the database that was copied. You still have to match the cookie key in the database table employee to with the one assigned in settings.inc.php by copying the cookie key, erasing the current password in the employee table and pasting in the cookie key you copied from settings.inc.php and with no spaces add the password you used in the settings.inc php.right after the cookie key then make sure you assign the code MD5 before you hit go. MD5 is not the default and if not used you ill not match the password with the database. If one user does not work try another, even though database rights have been assigned to both one may work and the other not? Another error that will cause the link not to be established is having the wrong url assigned in the table shop_url. You have to edit this very carefully. Even if you are using the root category you still have to put the slash \ on the next line physical url ​if you don't it will not link at all or you will find you have no sub directory tools menu in the backend admin. If you are placing the shop in a subdirectory such as prestashop make sure that the slash / is not only before but after the sub-directory on the physical url line. /prestashop/ otherwise there will be no link or again you will be missing the subdirectory menus in the admin section and only get the first default category such as general in preferences.
  15. Recently we attached a larger copied database to a new prestashop installation to replace the default one created by the new installation. When we logged into the back-end admin the main headings showed up such as in advanced parameters only the configuration would appear, the same with preferences where only the category general was shown. After spending an embarrassing amount of time on this problem. the answer was pathetically simple, we had left out a single / in the physical url line of the database table shop url. If the shop is in the root directory the / has to be put on the physical url line. If the shop is in a sub-directory such as prestashop or shop, you not only have to put in /prestashop on the physical url line,you also have to follow that with a back slash /prestashop/ following the sub-directory otherwise you you will not get the sub-category choices in the back end admin.
×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More