Here are some times i made up for ppl with a admin panel set up in there site.
1.) Dont make a folder called /_admin/, /admin/, /admin_/ with ACP in there.
2.) Dont create a file named acp.php, admin.php, _admin.php
I seen many sites like that. Many ppl try those folders / files to get into your site. Just some tips xD
Comments
For example the admin panel for this site is fairly obvious and easy to get to - but in order to get in you muts be logged into this forum with administrator privelages + have an extra password
The Royal Ram
i spend $395.95 on m hosting
i have an Xeon Power dual 80 GB hard drives (160 GB)
and unmetered BW line.
also got 5 cisco redundants if i need them
my site will be very secure, only because i dont look for that server lese where,
i can get that for $169 but it wouldnt be managed and i would only have 2 cisco redundants and it wouldnt be secure.
i can get it for $65 at HiVelocity.
but it would be crap.
Adult Section Leader :cool:
Pimp
Basically, if you've got a site using dynamic content, you'll need to use one of these at some point.
They are mainly used for things like posting content (unless you have another control panel for content addition), editing settings, skins and user managment.
Telling people not to call their directories common names isn't really Earth shattering information if you know how to build a secure control panel, especially if you're using a system like Ruby on Rails or Django, where the admin part of the URL might not relate to a directory, but to an item that would usually appear as part of a query string (Rails allows for URL's such as site.com/admin/edit/123 instead of site.com/admin.php?act=edit&id=123).
Current project: CMS Object.
Most recent change: Theme support is up and running... So long as I use my theme resource loaders instead of that in the Rails plug-in.
Release date: NEVER!!!