JustinS Posted March 27, 2013 Posted March 27, 2013 I have a site under construction and I want to make the front page password protected so that nobody can view what the store actually looks like unless they have the log in info. How is this achieved? I assume something with htaccess?
JustinS Posted March 27, 2013 Author Posted March 27, 2013 by front page i mean the catalog by the way. still searching for a solution. google hasn't turned anything up yet.
♥altoid Posted March 27, 2013 Posted March 27, 2013 @@JustinS You should be able to do this using your host cPanel. Look under security and something like password protect directories. The cPanel should also offer you a tool that let's you undo that when you want to remove the protection. I am not a professional webmaster or PHP coder by background or training but I will try to help as best I can. I remember what it was like when I first started with osC. It can be overwhelming. However, I strongly recommend considering hiring a professional for extensive site modifications, site cleaning, etc. There are several good pros here on osCommerce. Look around, you'll figure out who they are.
Bob Terveuren Posted March 27, 2013 Posted March 27, 2013 Hi if all else fails something like http://tools.dynamicdrive.com/password/
JustinS Posted March 27, 2013 Author Posted March 27, 2013 @@altoid I have GoDaddy hosting and I unfortunately do not see that feature. Going to try the addon atomic posted I guess, I had already found that one but just wasn't quite sure if it was the correct one. I thought there was a code you could simply put in to htaccess to block access to the catalog without a login/password. Thanks everyone.
MrPhil Posted March 27, 2013 Posted March 27, 2013 You can deny access to the whole store the same way you will deny access to just the admin/ section (once the store is live). Usually it's easiest if your hosting control panel provides some sort of "password protected directory". It's a lot harder (and varies from host to host) if you have to set up the files manually).
Bob Terveuren Posted March 27, 2013 Posted March 27, 2013 Hi Oooh GoDaddy - no cPanel try my previous link plus http://support.godaddy.com/help/article/1641/using-htpasswd-with-your-linux-shared-hosting-account?pc_split_value=3
JustinS Posted March 27, 2013 Author Posted March 27, 2013 Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. ---------- @@Bob Terveuren Ok I followed the godaddy one, got my path and everything... it asks for the login/password but then when i log in it gives me that message. Any idea what I'd be doing wrong?
JustinS Posted March 28, 2013 Author Posted March 28, 2013 Ahhh I just want to password protect this so I can start adding products! This shouldn't be taking so long, why isn't it working =X Now it won't even give me the prompt to put in a login/password
♥14steve14 Posted March 28, 2013 Posted March 28, 2013 If you have access to your htaccess file and can find your ip address you could try adding order deny, allow deny from all allow from YOUR IP ADDRESS Replace YOUR IP ADDRESS with your actual ip address. This should block everyone apart from you. You could also add a redirect to a maintenance page for all other users which may make things a bit better. REMEMBER BACKUP, BACKUP AND BACKUP
JustinS Posted March 28, 2013 Author Posted March 28, 2013 That sounds like it'd work just fine, but unsure how to redirect to a different page though - having the catalog unavailable would really be nice so google can't index any funky things while I'm adding/changing... but think I'm just giving up on it so I can go ahead and get the catalog built.
♥joli1811 Posted March 28, 2013 Posted March 28, 2013 That sounds like it'd work just fine, but unsure how to redirect to a different page though - having the catalog unavailable would really be nice so google can't index any funky things while I'm adding/changing... but think I'm just giving up on it so I can go ahead and get the catalog built. Why not just use a no index robots text User-agent: * Disallow: / will prevent google from indexing and thus preventing links appearing in google It is unlikely with a new site that there will be new serious visitors / customers takes a bit of work to seo the site and get customers I would disable the payment options just in case Regards Joli To improve is to change; to be perfect is to change often.
♥joli1811 Posted March 28, 2013 Posted March 28, 2013 Sorry the forum prevented me from finishing probably timed out!! That sounds like it'd work just fine, but unsure how to redirect to a different page though - having the catalog unavailable would really be nice so google can't index any funky things while I'm adding/changing... but think I'm just giving up on it so I can go ahead and get the catalog built. Why not just use a no index robots text User-agent: * Disallow: / will prevent Google from indexing and thus preventing links appearing in google It is unlikely with a new site that there will be new serious visitors / customers it does take a bit of work to win customers and Seo the site. so unlikely that with a new site it would appear high enough in google to matter ( unless really a niche as regards product / search term etc) would disable the payment options just in case If that did not suit would just upload a .htaccess with below in red # php_value session.use_trans_sid 0 # php_value register_globals 1 deny from all This denys access to everybody so when you need to work just put a # deny from all in front and this will cancel the command Regards Joli PPS: pps : just love the the term KISS means Keep It Simple Stupid! Thanks FWR Media :D To improve is to change; to be perfect is to change often.
MrPhil Posted March 28, 2013 Posted March 28, 2013 Sooner or later, for security purposes, you're going to have to figure out how to password protect your "admin" directory (which of course, you've changed the name of). That same method can be applied to the top directory of your work-in-progress, and when you go live, it's removed from the top directory and installed on the "admin" directory. Some of these other methods (IP blocking, etc.) might work for you (in protecting "admin", instead of the recommended password protection), but probably are not as trustworthy as password protection. It's up to you.
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.