tozama

I just finished all my setup+configuration inside a "catalog" folder and just successfully copied it all to the root of my public_html directory. My Presta Version is 1.4.4.1. Some/most of this is a repeat of above posts but I see they date back in some cases 2009 so here's the summary of what I did: 1. Using file manager in CPanel on my server I made a compressed file of the inside of my "Catalog" folder (the entire Presta website I made started in "www.mysite/Catalog/") called "catalog.zip". DO NOT just rightclick on "Catalog" folder and compress it. Doing this will create yet another "catalog" folder = exactly what you already have!!!! Go INTO/INSIDE the folder, then select all the sub-folders and files, and then right click - compress. 2. A zip file will appear now inside your current shop's root. I moved that zip file holding my entire Presta shop to the root of my server's public_html. You could download the zipfile, then upload it to your public_html root if you prefer. 3. Still in CPanel File Manager move to your root of public_html. unzip/uncompress it from within your root of public_html. Now you still have your working copy inside "www.yoursite/Catalog/" and ALSO the second copy to now get activated. This leaves you some safety until you see all works well. 4. Still in CPanel File Manager in your new root version of your shop, go into the folder called "Config". Download or edit online if you want the "settings.inc.php" changing: from define('__PS_BASE_URI__', '/your-old-presta-subfolder-name/'); to define('__PS_BASE_URI__', '/'); Save or overwrite the file. 5. Now try going into your admin back office through the root version www.mysite/admin/. It should allow you inside BUT you're not done yet. 6. Now go to Preferences -->SEO & URLs. Scroll way down and make sure PS directory only shows / 7. Go to Tools ---> Generators and click on the "Generate htaccess" then "Generate robots.txt" to sync those files. If you skip the last step your front office site will still point to the old locations and the robot text will as well. 8. Go into "Modules" and fix any payment areas that require your specific URLs if required. 9. Go to PayPal.com and/or Google.com if you use them as payment gateways and again revise their settings URLs to match your new one. After testing your new rooted site enough you could delete the old one or maybe just set it to "catalog mode" in Preferences --> Products to make it there for backup but not usable for ordering. I will delete mine after about 2 weeks of testing my root one.

I followed the States guideline above but I still got the dreaded "No Carrier Available To Deliver to that address". My "mistake" was I reused the included USPS profiles. Although I spent hours setting up weight ranges and zones for my USPS carriers since I edited the existing profiles THEY WON"T WORK. I noticed in small grey print on the USPS carrier screens the words: "- This carrier is bound to this module => uspscarrier - The shipping costs are calculated outside of your shop - This carrier uses PrestaShop range to calculate shipping costs" Well, I cannot find any such module but I can tell you all the time you spent setting zone prices by weight for them was a waste. You need to DELETE the existing USPS carrier profiles and make new ones with slightly altered names and CREATE them as a brand new to Presta carrier profile - then populate the weight ranges and then the zone prices. I lost a ton of time but doing the above made all my shipping charges work now.

If you are using the cool sliding menu module addon called Menu DHTML by Tom06 v1.1 "Add a dhtml menu in your site" I just figured out it was the last item to cause the Security warning for my site. I disabled it and all messages went away. I had to add more pages than: ....but through testing managed to stop all the warning boxes. The downside is this excludes the slider menu from all those pages so if you hope to have a Categories menu beyond the home page I suggest you use the default Categories Block that the original install comes with.

Errrmmm, That is "A" reason one can get a cert warning, yes. But I and I bet most posters here have a real cert installed and we are addressing specific issues with Presta and how it handles mixed content calls. Thanks for the fixes some of you posted above. I am off to see if I can resolve mine now. And as one poster pointed out, this IS a serious issue for an ecommerce site. The last thing I want is to lose a customer over something like this!