[Pro] Problem splitting large site

I just split this site into two freeway documents – one for the paid members area and another for the public area. The problem is, the links don’t seem to be transferring properly between the two FW documents. FW says the upload is complete for both files, but the links in the CSS menu header don’t work.

If you navigate into the members area, and from there click on the home button, the browser says “The system cannon find the file specified.”

This is how I split the site. I duplicated my FW file and deleted all the pages that didn’t belong to that file. So one file has all the /membersonly pages and the other file has everything else. When FW asked, I clicked the “replace with links” button before deleting the pages.

Also, everything in the /membersonly directory should be password protected. But, at the moment it is wide open. I don’t know if this happened on upload or something in the cpanel protected folder area.

Please help! (And thank you…)

Doty

http://www.plasticvilleusa.org/


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I’m double checking all my links in both FW documents. (Everything was perfectly fine before I split the file!) What do I do with a link that shows up like this in the “edit hyperlink” dialog: …/index.html

I’ve never known what the two dots mean and I’m thinking it’s time I learn!

Doty


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

This may be a clue, but I’m not sure what to do with it. What is FW trying to tell me w/ the double dot preceding the file path?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

It indicates a relative path vs. an absolute path. In this case it’s pointing to the index file one level above the current folder.

Todd
https://xiiro.com

What do I do with a link that shows up like this in the “edit hyperlink” dialog: …/index.html


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks Todd. I should have mentioned, I get that part. I’m just not sure what to do to fix the problem!

Is the path relative to the FW document or relative to the file/folder structure on the server???

relative path vs. an absolute path


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Assuming you’re using FW to upload then the path should be relative to exactly the same structure, local and remote. Unless you are messing around with remote site’s folder structure.

Todd
https://xiiro.com

Thanks Todd. I should have mentioned, I get that part. I’m just not sure what to do to fix the problem!

Is the path relative to the FW document or relative to the file/folder structure on the server???


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

The key to getting this right, in my experience, is to make sure that your sub-documents all publish into the same site folder as the master document. Then you also MUST “Publish Everything” (control key plus File / Publish) at least twice per document after you make the split. Many missing resources unless you follow that step.

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).

The reason for this wrinkle is that if you leave all of the sub-documents to create the same root folder, they may take a short-cut and reference resources and other items from the top level folder’s Resources folder, and that way lies madness. Wrong resources, non-protected pages referencing resources from the protected folder, it can go so horribly wrong, so many different ways.

Walter

On Apr 22, 2015, at 1:13 PM, Todd email@hidden wrote:

Assuming you’re using FW to upload then the path should be relative to exactly the same structure, local and remote. Unless you are messing around with remote site’s folder structure.

Todd
https://xiiro.com

Thanks Todd. I should have mentioned, I get that part. I’m just not sure what to do to fix the problem!

Is the path relative to the FW document or relative to the file/folder structure on the server???


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

Walter,

Thank you. I will follow your steps very carefully and get back with you.

Could any of this explain why the /membersonly folder is no longer asking for a password?

Doty


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

That could be explained if one of your documents deleted that folder, and you published that document. If it deleted the folder from your server, it would also delete the .htaccess file along with it. Once you have everything publishing the way you need, add that back through your cPanel.

Walter

On Apr 22, 2015, at 2:20 PM, Doty email@hidden wrote:

Walter,

Thank you. I will follow your steps very carefully and get back with you.

Could any of this explain why the /membersonly folder is no longer asking for a password?

Doty


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

All of this begs the question — is splitting this site necessary? My preference was to keep the site in one document. But I ran into a problem with the way the FW uses shared resources. It kept asking for a password to get into the non-protected areas to access images that should be uploaded both places. (protected and non-protected areas of the site).


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

This is the definitive way to solve that problem. Because your “protected” Freeway document believes that it is saving all its files in the root folder, and the “public” document believes that the private directory is empty, you don’t end up with these kinds of mixups.

Walter

On Apr 22, 2015, at 2:54 PM, Doty email@hidden wrote:

All of this begs the question — is splitting this site necessary? My preference was to keep the site in one document. But I ran into a problem with the way the FW uses shared resources. It kept asking for a password to get into the non-protected areas to access images that should be uploaded both places. (protected and non-protected areas of the site).


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

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?

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

http://www.plasticvilleusa.org/index.html

And, can I assume I need to do this for all the subsequent pages… so /blog /contact etc. Etc.?

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

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

Okay Walter, I’m making some progress. Here are the steps I’ve followed:

  • I’ve “published everything” multiple times.
  • I’m using one site folder.
  • I’ve duplicated each of the folders in the master document.
  • I’ve removed all relative links in the “members” document w/ absolute links

I think all of this has fixed the missing link issue. It would take a lot to double check each link, but in general everything seems to be working as it should.

What is not fixed is the /membersonly section. This folder is password protected on the server level, but at the moment, the browser is not asking for the login/password. Walter, you said something about htaccess. Do I need to do something with that file? I looked on the server in an FTP program and there is a /membersonly folder, but I do not see an .htaccess file.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

there is a /membersonly folder, but I do not see an .htaccess file.

It should be inside the membersonly folder - but it will be invisible unless you have that feature turned on in your FTP app.

However if you have used FW to upload/create a membersonly folder then your original version may have overwritten it and you may have to apply Protection again.

But if you can access it without being asked it doesn’t mean it is not protected because your Permission to Enter is cached in the Browser.

Get someone else (on another computer) to try accessing its contents and see what they experience.

David


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

  • I turned on invisible files in Transmit and it showed invisible files on my hard drive, but nothing different showed up in the server window.

  • I did indeed use FW to upload/create the membersonly folder. I also looked inside the Site Folder of my old FW document (the one that has password protection enabled) and there is no .htaccess file in there either.

  • The password protection is enabled through the cpanel on the server. As far as FW is concerned, I would think it would treat /membersonly as just another folder.

  • Before, it would ask me to log in again after being away from the site for only a short while, but just to double check, I used a different computer and indeed the /membersonly is wide open to the public. It’s not asking for a login/password at all. For example, this page should be password protected. But I’m guessing you can click on that link and view it without the log/pass dialogue popping up.

However if you have used FW to upload/create a membersonly folder then your original version may have overwritten it and you may have to apply Protection again.

I do I do this? I expected the settings in cpanel to take over and it seems that’s not the case.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Try using the cPanel to remove password protection, then add it back. CPanel may have stored the fact that it was once enabled, even as the local implementation was deleted by Freeway. Maybe.

Walter

On Apr 23, 2015, at 3:17 PM, Doty email@hidden wrote:

  • I turned on invisible files in Transmit and it showed invisible files on my hard drive, but nothing different showed up in the server window.

  • I did indeed use FW to upload/create the membersonly folder. I also looked inside the Site Folder of my old FW document (the one that has password protection enabled) and there is no .htaccess file in there either.

  • The password protection is enabled through the cpanel on the server. As far as FW is concerned, I would think it would treat /membersonly as just another folder.

  • Before, it would ask me to log in again after being away from the site for only a short while, but just to double check, I used a different computer and indeed the /membersonly is wide open to the public. It’s not asking for a login/password at all. For example, this page should be password protected. But I’m guessing you can click on that link and view it without the log/pass dialogue popping up.

However if you have used FW to upload/create a membersonly folder then your original version may have overwritten it and you may have to apply Protection again.

I do I do this? I expected the settings in cpanel to take over and it seems that’s not the case.


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

Walter,

Before I remove and replace the password protection via the cpanel, will it retain the 500 or so member login/password combinations that are stored there?

I’ve never rooted around the cpanel on this particular domain. It is managed by someone else on the committee. But, I’ll see what I can do. I have no idea if someone on the committee has a backup of this info, but I guess this is as good a time as any to ask!

Doty


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Not sure. You may want to experiment on another folder with different users.

Walter

On Apr 23, 2015, at 5:30 PM, Doty email@hidden wrote:

Walter,

Before I remove and replace the password protection via the cpanel, will it retain the 500 or so member login/password combinations that are stored there?

I’ve never rooted around the cpanel on this particular domain. It is managed by someone else on the committee. But, I’ll see what I can do. I have no idea if someone on the committee has a backup of this info, but I guess this is as good a time as any to ask!

Doty


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

Quick update to my broken password issue – it’s been fixed!

Here’s what happened. I went into the cpanel to find that all 500+ members had blanks for their passwords! Horrors!!! Their login name was intact, but the password was missing for every single one. Amazingly, the board member typed in one password (his wife’s) and all of the remaining passwords re-populated automatically with the correct information. I have no idea how this happened. But I’m thankful for the good karma today!

So many thanks to those on this list that have helped along the way. This is a huge project and I’m celebrating tonight! I love the FW community!!!

Doty


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options