On Apr 22, 2015, at 4:53 PM, Doty email@hidden wrote:
Walter,
I’m a little confused about this:
Only the master document should create the subfolders
Which file is the “master?” The public one, or the members (restricted) one? What if I want to add subfolders in the future?
The master is the one that creates the outer shell. So it should have empty /private and /blog folders in it (basically, anything that is covered by another application or a different document). It creates the one and only domain-level index.html.
Then each child document will publish its content into just the /private or /blog folder, as if it was the root. You may have done this already if you created a subdomain site on one of those servers that generates a folder-name subdomain for you automagically. From that child document’s perspective, the root of the site is /private or /blog, and it should never try to post anything higher than that point in the filesystem.
From the master document’s perspective, there is nothing inside the /private folder, so it shouldn’t try to hide any files in there.
and each child document should publish INTO those subfolders (one per) as if that was their top-level directory.
I’m hoping this makes sense after you answer my question about which file is the “master”
Any links to the main home page should be re-written to be manual /index.html (with the leading slash) and then they will work consistently.
Do you mean links from the restricted FW file to the public FW file? If so, is there and advantage/disadvantage of
/index.html
Verses
Plasticville Collectors Association
either /index.html or …/index.html will work identically to the fully-qualified URL, but …/index.html will have the added benefit of also working on your local Mac if you preview the master document and then navigate into the blog or private content and then back out of there. Relative is always preferred, even though it takes a bit of head-scratching sometimes. You can alway do a root-relative link, which is what the leading slash gives you. That is unambiguous as it always means “go to the site root and start there”. But it will fail utterly on your local Mac.
And, can I assume I need to do this for all the subsequent pages… so /blog /contact etc. Etc.?
Probably. If you are inside the protected folder, or any other sub-folder that has its own separate document, then within that separate document, you would need to make manual links of one sort or another to get back to a level above that document’s personal idea of what constitutes the site root. You’re doing this so that those child documents don’t suddenly place their resources above the level of their own folder, so they can be neatly isolated from one another.
Walter
Now if you are locking one of the subfolders to be members-only, you must follow this additional wrinkle: Only the master document should create the subfolders, and each child document should publish INTO those subfolders (one per) as if that was their top-level directory. Any links to the main home page should be re-written to be manual /index.html (with the leading slash) and then they will work consistently. Either that or you can use the leading two dots if you are sure of your location in the hierarchy (one set of dots and a slash per upwards directory level).
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options