| Author |
 Topic  |
|
adamch25
Starting Member
USA
22 Posts |
 Posted - 11 June 2003 : 08:38:36
|
A folder structuring is needed for Snitz. Place the images in a folder, include files in a folder, admin files in a folder, etc. I've actually been waiting patiently for this for over 2 years now. It seems to get overlooked every release. I am hoping and praying that it will make the cut for version 4. I manually do this myself after every release and it has gotten very tiresome. Doing this would make upgrading to newer releases much easier for me. Read the topic below... even Huwr agrees! 
http://forum.snitz.com/forum/topic.asp?ARCHIVE=true&TOPIC_ID=2567 |
Adam |
Edited by - Davio on 11 June 2003 12:59:30 |
|
|
Hamlin
Advanced Member
United Kingdom
2386 Posts |
Posted - 11 June 2003 : 08:44:47
|
| You can already specify an image folder. |
 |
|
|
Nikkol
Forum Moderator
USA
6907 Posts |
|
|
Gremlin
General Help Moderator
New Zealand
7528 Posts |
Posted - 11 June 2003 : 09:11:13
|
| I'm one that does the same too, I like to have various files such as includes, admin pages etc each in their own directory. I don't think though that it warrants being added as a feature to the next version becuase most likely only a handful of people would ever actually want or use it. |
Kiwihosting.Net - The Forum Hosting Specialists
|
|
|
|
adamch25
Starting Member
USA
22 Posts |
Posted - 11 June 2003 : 09:23:08
|
quote:
Originally posted by Nikkol
Why do you need separate folders for the other files?
Its good practice to keep things separated and clean. I personally like to know exactly where to look if I want to modify an admin file or includes file. Its especially nice for those of us who have control over our servers to be able to add additional security to the admin folder. I've tested a few other message board software apps and they all seem to use a common folder structure. |
Adam |
|
|
|
adamch25
Starting Member
USA
22 Posts |
Posted - 11 June 2003 : 09:32:17
|
quote:
Originally posted by Gremlin
I don't think though that it warrants being added as a feature to the next version becuase most likely only a handful of people would ever actually want or use it.
I think you'd be surprised... there are a lot of closet folder structurers out there! Actually, I think there are a ton of features that most people don't necessarily use but certainly add to the foundation of the app. I think this is one of those subtle features that would only improve the app. Sure, most people probably wont even notice or care but it will be welcomed by those that do. |
Adam |
|
|
|
davemaxwell
Access 2000 Support Moderator
USA
3020 Posts |
Posted - 11 June 2003 : 10:13:59
|
| Actually, back in the dark ages of early Snitz development(I think this changed in the 2.8 range but it could have been before then), the admin stuff at the very least was split into a separate folder. And people hated it because it required more effort on install plus the theory then (which I still tend to agree with) was that the files were already named meaningfully so they would be easy to identify (all admin pages start with admin_, all popup forms start with pop_, all include files start with inc_, all images start with icon_, etc. So on general consensus, the folders were combined all into one to make it as easy as possible to install to your host. |
Dave Maxwell
Barbershop Harmony Freak |
|
|
|
snaayk
Senior Member
USA
1061 Posts |
Posted - 11 June 2003 : 11:02:40
|
| I also separate all my files into neat little folders. All forum files are in the forum folders I do howevermove the admin files to a admin folder for all site administration. I then do a find and replace. PITA, but worth it, I think. |
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 11 June 2003 : 14:14:36
|
| I'm not sure if this'll work with the forums, but if you create a site in DreamWeaver MX, and you move the files from one directory to another, the includes automagically get changed. Homesite 5 has a feature called "extended find & replace" that'll let you find & replace in entire folders, so it shouldn't be that much work to move files and get the include codes correctly. |
|
|
|
Reinsnitz
Snitz Forums Admin
USA
3545 Posts |
Posted - 11 June 2003 : 15:10:11
|
Yup... Huw was talking about the Images file only in that post dude.
The rest is logicaly named to allow for easy finding and editing. There are hosts out there that don't allow sub folders (probably very few now). The ability to have images in a sub folder was done as described as above. The ability to have admin stuff in a sub folder was canned caus it realy doesn't add any security or have any plausable use for most of the user community. |
Reinsnitz (Mike) |
|
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 11 June 2003 : 23:49:24
|
| I'm of the opinion the admin pages should be in a separate folder. With IIS and windows it makes it easy to add OS authentication protection to the admin pages. As it is now you have to go through each file & change permissions. |
======
Doug G
======
Computer history and help at www.dougscode.com |
|
|
|
Reinsnitz
Snitz Forums Admin
USA
3545 Posts |
Posted - 12 June 2003 : 15:43:22
|
| oh... and includes... forgot about those... can you tell an include to relatively include? ../inc_header.asp (or does it have to be rooted? /forum/admin/inc_header.asp) |
Reinsnitz (Mike) |
|
|
|
Gremlin
General Help Moderator
New Zealand
7528 Posts |
Posted - 12 June 2003 : 18:13:47
|
| You can use relative Mike. include has two options include file= and include virtual= |
Kiwihosting.Net - The Forum Hosting Specialists
|
|
|
|
MasterOfTheCats
Junior Member
103 Posts |
Posted - 13 June 2003 : 02:04:08
|
This will cause problems with MODs, problems in upgrading, etc... Also if "Enable Parent Paths" in IIS is turned off, you will have problems with admin pages. So it would be wiser to leave it as is.
Include virtual is not useful in PWS like development environments, where you put everything under localhost (w98 and w2k pro)...
|
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 16 June 2003 : 11:48:26
|
quote:
Originally posted by FrutZle
Homesite 5 has a feature called "extended find & replace" that'll let you find & replace in entire folders, so it shouldn't be that much work to move files and get the include codes correctly.
I have to admit that after having tried doing this, I gave up because it's still a lot of work and needs some kind of schedule or plan on what to do first and what should be found and replaced. I had neither time nor did I feel like doing that much work.
Next up is a test to see if Dreamweaver MX can help, but I'm not exactly confident that it'll work. If it works without problems, I'll post about it so perhaps it'll be of use to someone. |
|
|
|
MasterOfTheCats
Junior Member
103 Posts |
Posted - 05 July 2003 : 07:46:29
|
I did this on a local test forum but ran into some problems. I created "admin", "inc" and "img" directories. Here are what I faced in addition to simple INCLUDE directive changes:
- Link references: Some must be made dynamic. Anything linking to another admin file from another admin file can stay as is, but links in include files (e.g. inc_header.asp) need sometimes to point to (say) "active.asp", sometimes to "../active.asp".
- Image references: Same problem. They are sometimes in "img/icon.gif" style, sometimes in "../img/icon.gif" style. This is simpler because most images come from getCurrentIcon function.
- Application related: As far as I know, an ASP application starts with the execution of first ASP script and it cannot go upper levels in directory. If someone starts with setup.asp or admin_home.asp, there can be a problem. Also "strCookieURL" calculation must be changed.
All necessary calculations can be made in config.asp. What I did is (same order):
- Replaced most strImageURL's with another variable "strCorrectedImageUrl". The value of it is either equal to strImageURL or equal to "../" & strImageURL.
- Defined strURLCorrectionPrefix which is either "" or "../". I replaced all links of style
response.write "<a href=""default.asp"">"
With
response.write "<a href=""" & strURLCorrectionPrefix & "default.asp"">"
You should only use it in include files. Other changes to the links:
* From main files to main files stay as is
* From admin files to admin files stay as is
* From main files to admin files hardcoded like "admin/admin_home.asp"
* From admin files to main files hardcoded like "../default.asp"
I actually defined a constant for admin directory and used strAdminDirectory & "admin_home.asp" style to cope with the "Enable Parent Paths" problem.
- strCookieURL related one is easy:
strCookieURL = Left(strPathInfo, InstrRev(strPathInfo, "/"))
strCookieURL = replace(strCookieURL,"/admin/","/")
BUT, I'm not sure about the application start point.
I think it will be a good point to make these changes to the base code with v4. It seems from the stuff I read here that changes in v4 is already very much and all mods etc must already be re-written. This is why I tried this and shared what I faced.
I'll also thank anybody who shares his/her opinions/knowledge on these (especially #3).
|
|
|
|
Topic |
|
Topic Locked
