Last summer you hooked me up with an action you made the was supper cool. It allowed me to password protect html files. I just went to make an upgrade to our site and wanted to create separate client folders that I could use your Action to access the html page inside. Hers is what I did.
At one level of the directory I made my client login page, super cool and in that Freeway document I created client folder, super cool again. Next I created completely separate Freeway documents complete with recourses and such and pointed them to upload into the folders created by the login freeway document. By adding a forward slash to the password I was able to have the [password look down into the right folder and find the html document, super cool again.
Here is the issue and it makes sense why it is not working. It seems that when the login page ingests the code from the html page inside its own site folder that the login page is not able to look into that folder resource folder.
QUESTION 1: Is there a way this could be modified so the login page could recognize the source resources folder?
QUESTION2: Could you explain how the folder feature of the action works as it does not seem to do anything. Or do the contents of the folder have to be of some special type?
Here is another pass at my main question. Is there a way to use Tim’s Action “Password Protected URL (PHP)” so my clients can enter their password in a field on my home page and it will bring up their specified page which is located in a separate folder containing its own resources, css and such.
I need this as we have several clients all with multiple projects that we create a mini single page site for each one. Below is an example of what my file structure would look like.
Thank you for the suggestion but that would require all the destination links to be visible on the home page or another page where instead of the users password being what directs them to the destination.
You could just email/tell them the direct link to their (protected) Client folder and once they have it they can bookmark it and go straight there. Once in that folder you can then have navigation to the separate projects.
And all would remain out of sight from casual browsers.
Could you explain how the folder feature of the action works as it does not seem to do anything. Or do the contents of the folder have to be of some special type?
Bear in mind that the folder in question will have to contain an index.html file - this page could then have further navigation to specific project folders.
Thank you for your input and I have seen this code before. We may consider it, not sure if the standard version can be used in our setting but there is an advanced set of code that may be a future solution.
Thank you the updated code “Action”. Bellow are a few question.
(1) So does this mean that the Action looks into folders for a specific html document ?
(2) Or does it ingest folders with folder names that match the password that is interred ?
(3) Is the end result that the final target html page is obscured?
(4) SERIOUSLY Tim, are you a mind reader. just noticed your new code has provision for PDF URL obscuring and we ran into a serious need for this last week. Does this mean that when a user loads a page by using the password and on the page is a PDF that when the view online the URL is obscured?
(5) Can the user just click the link to a PDF and view it or is this password protected as well. We just ran into a big issue last week where we need clients to be able to view PDF’s on pages that they got to through the password but we don’t want them to have to enter a password each time they view a PDF on the protected page, just want to obscure the URL
Thank you the updated code “Action”. Bellow are a few question.
(1) So does this mean that the Action looks into folders for a
specific html document ?
No, the action simply redirects to folders or PDFs or ingests HTML
documents in place. If the PHP locates a target (file or folder) with
a matching password/name then the user will be redirected. Otherwise
the user is shown an ‘incorrect password’ error.
(2) Or does it ingest folders with folder names that match the
password that is interred ?
Correct.
(3) Is the end result that the final target html page is obscured?
Yes for HTML files.
(4) SERIOUSLY Tim, are you a mind reader. just noticed your new code
has provision for PDF URL obscuring and we ran into a serious need
for this last week. Does this mean that when a user loads a page by
using the password and on the page is a PDF that when the view
online the URL is obscured?
No. Currently only HTML files are ingested.
(5) Can the user just click the link to a PDF and view it or is this
password protected as well. We just ran into a big issue last week
where we need clients to be able to view PDF’s on pages that they
got to through the password but we don’t want them to have to enter
a password each time they view a PDF on the protected page, just
want to obscure the URL
The PDF will be displayed but, as I say, currently the url is not
obscured.
This action was an extension of the existing JavaScript version as I
was unhappy with the way that incorrectly entered passwords would
throw a 404 error page. although the functionality is almost identical
this version uses PHP to check to see if the file exists before doing
the redirection.
It sounds a lot like you need something that surpasses this simple
action and redirects the user based on an internal lookup table of
usernames, passwords and target files or folders.
Regards,
Tim.
Thank you for the updated action and it seems to behave correct. Let us know if you ever decide to develop an action that does what is listed above as this would be something our company could really use.
Question, the page and PDF features seem to obscure the URL, but the folder does not. Also the only way I was able to get a page within a folder to load was by it being an index.html page. Could you shed some light on this?
I was thinking about all this the other day and your “Remote Resources” action came to mind.
Here is the scenario: I create a login page using your “Password Protected URL (PHP)” and point it to a HTML page in a separate folder. The HTML page has been given a s specific name as well as the the folder, together they will make up the password. To overcome the issue where the target page looses it’s connection to its recourses located in the resources folder with the HTML document I have applied your “Remote Resources” action and gave it the correct path. Upload go to the login page enter foldername/htmlpagename and all seems to be working.
QUESTION: Is the a correct usage of these two actions and should this work or have I come up with some bizarre combo that may work but not be stable across varied browsers and platforms?
No, if you find that it works then go with it. It should be fine.
Regards,
Tim.
On 20 Mar 2010, at 22:47, TeamSDA wrote:
QUESTION: Is the a correct usage of these two actions and should
this work or have I come up with some bizarre combo that may work
but not be stable across varied browsers and platforms?