FutureQuest, Inc. FutureQuest, Inc. FutureQuest, Inc.

FutureQuest, Inc.
Go Back   FutureQuest Community > General Site Owner Support (All may read/respond) > E-Commerce
User Name
Password  Lost PW

Reply
 
Thread Tools Search this Thread Display Modes
Old 08-05-2011, 07:04 PM   Postid: 180294
sliksock
Registered User

Forum Notability:
0 pts: Even-handed
[Post Feedback]
 
Join Date: Aug 2011
Posts: 1
Prestashop and Shared SSL

In the last few days I have been trying to install Prestashop (www.prestashop.com) on a secure server using a shared certificate. In researching this I have come to the conclusion that this is widely considered either not possible or extremely difficult. Those who say it is extremely difficult do not explain how it can be done and say you should simply spring for a full certificate and be done with it.

Only wanting to use my shared certificate (hell, I'd paid www.futurequest.net for it, I'm **** well going to use it).

Anyway, I couldn't get Prestashop to work correctly with my shared certificate and I didn't like any of the other options, most of which seemed to be just as unlikely to work on a shared certificate as Prestashop, according to the information I would read about each one.

What was I to do?

I had given up on Prestashop and was turning my attention to Zen Cart as that had proven to be usable with a shared cert according to what I had read. However, upon reading the explanation for how to install Zen Cart using a shared cert on futurequest, I began to wonder if the same technique could be used to install Prestashop on the cert.

Long story short, it looks like I did it. I've been playing with it for almost a full day and it seems to work flawlessly with my shared cert. Perhaps I am missing something of which I am not yet aware, but I thought I would post the technique I used so others could do the same and we could all compare notes.

Ok. Before I lay it all out I should point out that this technique was first posted as a way to install Zen Cart at futurequest's community website at the following url:

http://www.futurequest.net/forums/sh...light=zen+cart

It was posted by a user named Matt. If this technique ends up working for you (and the rest of us) we should all go to his house and throw him a surprise party, he will have earned it.

Anyway, here are the steps I followed based on his original post:

Futurequest creates a folder in your webspace called Secure_Server for SSL. All of these steps were used on futurequest, I cannot vouch for how they will work on other servers.

Step 1: Create a folder in Secure_Server called shop (or anything you want).

Step 2: Copy the Prestashop install to this folder.

Step 3: Download Putty from http://www.chiark.greenend.org.uk/~s.../download.html

Step 4: Run Putty and log into your main www.website.com address (do not log into the secure server) using SSH.

Step 5: Type (without the quotes): "cd .."

Step 6: Then type (without the quotes): "cd www"

Step 7: The type (without the quotes): "ln -s Secure_Server/shop shop"

Step 8: Go to your web browser https://xyourdomain.merchantquest.net/shop/zc_install and install Prestashop normally.

Step 9: Using FTP (I use filezilla http://filezilla-project.org/) go into your Secure_Server/shop folder and delete zc_install and rename admin to whatever you want just like normal.

Step 10: Navigate in FTP to your root directory (on futurequest it's www) and delete your shop folder that was created by putty (in filezilla there will be a little arrow on it). You can close the ftp program now.

Step 11: Run Putty again and redo steps 4 to 7.

This is how I did it. Some of these steps may not be necessary, however, better safe than sorry.

Now, here I paraphrase Matt from his original post:

Note: Any changes you make to Prestashop, templates you install, etc. should be uploaded to the Secure_Server directory, NOT the www directory. The symlinks will take care of the rest and you don't have to worry about maintaining two copies of the same file or whether Prestashop expects a secure or unsecure path.

That's it. So far, it's working like a charm for me, all the problems I had have vanished. I haven't come across any new problems.

I hope many of you will try this and let's see if it works for everyone and if there are any pitfalls I have not yet come across.

Thanks for reading and let me know how it goes for you if you try it.

Alex
sliksock is offline   Reply With Quote
Old 08-06-2011, 04:59 PM   Postid: 180299
sheila
Site Owner
 
sheila's Avatar

Forum Notability:
0 pts: Even-handed
[Post Feedback]
 
Join Date: Aug 1999
Location: Metro Los Angeles Area
Posts: 7,398
Re: Prestashop and Shared SSL

Thanks for posting these instructions, Alex. Hopefully it will help someone else with the same situation as you had.
__________________
sheila
http://www.thinkspot.net/sheilaruns/
sheila is offline   Reply With Quote
Old 08-08-2011, 12:16 AM   Postid: 180300
Matt
Site Owner
 
Matt's Avatar

Forum Notability:
671 pts: Dignified Competence!
[Post Feedback]
 
Join Date: Nov 2000
Location: Birmingham, AL, US
Posts: 1,231
Re: Prestashop and Shared SSL

Hello Alex,

I'm glad this was helpful for you. In reality, the general concept is applicable to ANY application at FutureQuest that requires both secure and non-secure access. To take some of the mystery away, you're really just creating a folder alias (symlink) so that you do not have to maintain 2 separate copies of the script. A few comments:

1. Doesn't matter whether you have shared SSL or dedicated SSL, the procedure is the same. In fact, dedicated SSL is so cheap (as little as $20/yr) that I recommend going this route. Buy 5 an SSL cert for 5 years and be done with it Note: you wouldn't need to reinstall Prestashop, just change the secure path in your configuration file.

2. I'm not sure why you performed steps 10 & 11, but I don't believe they're necessary. If I read this correctly, you're creating the symlink to run the install, deleting the symlink after the install, then recreating the symlink. A symlink is just a pointer and the process of deleting and recreating it doesn't trigger an action (such as reloading files).

3. Step 8 & 9 reference zc_install. I'm guessing that's an artifact from my tutorial and not reflective of Presta's naming convention.

Best of luck with your new store. Post back in a few months to let us know how Prestashop is working for you.

-Matt
__________________
Webspace Creations
Matt is offline   Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 visitors)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -4. The time now is 12:25 AM.


Running on vBulletin®
Copyright © 2000 - 2019, Jelsoft Enterprises Ltd.
Hosted & Administrated by FutureQuest, Inc.
Images & content copyright © 1998-2019 FutureQuest, Inc.
FutureQuest, Inc.