Hello there all,
As well as I’m working on includes a public and new member area. I’m using a php login script to help enter member spot.
Would I often be better off using a subdomain for that member area or ought to be a just use internet. domainname. com/member_area
I’m not guaranteed what the advantages and disadvantages are of this particular. If it concerns, I will end up being implementing google blog but I should be able to tie this for the domain or subdomain, and it’s also independent of where the member area is actually.
Any help could well be greatly appreciated.
p. ersus. I think here is the correct area due to this thread. If not really, please feel free to transfer
It doesn’t matter.
Your members area will probably be protected by a " user login". It will involve PHP TIME,
and thus, you will command which pages or content influenced by whether a SESSION
exist or not (the customer is logged-in). On most occasions, the very same pages will probably be used
regarding both members along with non-members… it might you need to be the content which changes.
That’s where CSS templates come into use.
Everyone didn’t bring-up every comments about Subject matter Management, MySQL or things like that.
This post is usually not in the PHP part of the forum… perhaps you aren’t sure related to PHP
mlseim – Thanks for that response. I guess the main reason I posted here is that I’m mostly interested in the site organization.
One thought Thought about is a subdomain can be more secure. For instance, if someone were to key in www. domainname. com/member_area, would they be capable of see the directory listing in the folder (even once they can’t access this particular files)
I’m still divided using a CMS. The web-site I’m designing is usually pretty static. Most of the ‘action’ is visiting take place around google apps.
I’m using a members area to help list links in order to google spreadsheets in addition to sites and add some forms as well as graphs. Basically, the same page continuously, just changing links for the appropriate form/graph.
And often tell, I’m just a little new at just about all this so any kind of insight is enormously appreciated.
How might you handle the " member login"
I guess you could potentially put the representative stuff in it really is own directory in addition to use. htaccess/. htpasswd to undertake it… that’s form of awkward though.
Nothing is risk-free from anyone until you have getting some sort of log-in system. That’s my point related to " it isn’t going to matter". Whether you protect by " file" as well as by " directory", it really needs to be done somehow. I guess for anyone who is not using almost any server-side scripting, you can be better off getting all " member" material in it’s personal directory.
Little else I can say about it.
When there is not any index page in the directory, visitors can certainly look and view what’s inside. Some servers are configured to forestall directory browsing like this. If yours is just not, you can arranged it up by putting this within your. htaccess file: Solutions All -Indexes The dash (minus sign) is critical, without it the directory files will present. I do this for all of my web sites – I don’t want people accessing lists belonging to the files on my domain.