Search the Community

We have had our store open a week and a half, and I still have to check paypal to find out if we had a sale. If I have a new payment amount, I then have to go back to my BO and find the cart that's worth that amount, and then manually convert it into an order. Doing this keeps the sale from registering with my affiliate program. Then I have to manually add our affiliate's commission, and then HOPE that the customer commented with the affiliate's name that referred them. The Post Affiliate Pro software that I'm using can't track my sales, and who gets the commission, when an order does not convert into a sale after receiving a payment acceptance from Paypal. I have spoken to Paypal and they informed me that if we are getting an email about the payment, and are getting a payment, then we are integrated correctly. PAP is also integrated correctly because it does keep track of the IP address from all the raw clicks on our site. My BO does sometimes provide an IP address of the customer, but checking multiple IPs against 10s of thousands of raw clicks, is not feasible. Please help! (Using PrestaShop 1.6.1)

Hi, I would like to know if there is any official guide or guidelines to promote PrestaShop installations between environments. In case there are 2 or more environments for a shop (test environment, production environment), which are the recommended steps to take to promote from one environment to another? My concerns are: - promote the shop main configuration options - promote specific modules configuration options - promoting the catalog - promote changes in core or module files - avoid long downtimes To avoid some headaches, I'm thinking about this "simple solution": There would be 2 environments: test (private) and production (public). The test environment is where all the changes are made (with previous backups): core updates, module updates, shop configurations, catalog management, etc. Once the test environment is "accepted", it gets cloned to the production environment (with previous backup). The cloning procedure would have this steps: Backup production files Remove all the old files from production Copy all the files from test to production Backup production database Remove production database* Copy the database from test to production Change the /config/settings.inc.php with the production database values * I should save before the orders, the carts, the user information, etc before. Am I missing something? I just want to know if anyone has easier solutions, or solutions that minimize the downtime. How are you making your environment promotions?