I hope there is a simple path specification to take me where I need to go.
I am “user1” on the system. If I use an FTP client, it reasonably enough dumps me into
/home/user1/
Where all my site files are is
/var/www/html/
What path specification should I use for FWP to have it find the right spot?
Thank you.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi,
Please create a file named “path.php” with the following code included and upload it to your main website folder. Access the file via your browser and it should spit out the exact path you will wish to use with FWP to have it find your files.
<?php print_r($_SERVER['DOCUMENT_ROOT']); exit(); ?>freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Alec —
Thank you. Unfortunately, I need just a tad more info…
Like where to put the code.
Thanks.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi Ted,
I’m not sure I follow? If you put the code provided within a .php file (ex: path.php) and upload it to the main folder of your hosting account you should be able to then go to the following address to view the path:
http://www.youdomain.com/path.php
Or are you asking what you then need to do with that path?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Ted,
He just means put the code in a text file. You do that with a plain text editor. Then save the text file with the name exactly as path.php and upload that text file to your main folder.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thank you gentlemen.
A first problem was faulty memory as I substituted “web“ for “www” in my experiments before asking.
A second problem came from me trying to handle Alec’s guidance within FWP.
All seems well now. Thank you.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
A second problem came from me trying to handle Alec’s guidance within FWP.
Actually, that is still possible to do in FWP. In Freeway you would create a new page and name it path.php. Then you would add a single markup item to the page, and nothing else, and insert the code into that. As long as you don’t do anything else to the page (including making sure there is no styled Master page assigned to it) then the only thing that will publish on that page is the markup text you inserted.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
That’s good point, but not quite true. If you make a page in Freeway,
there will be some HTML code generated, and it’s not removable
entirely without Actions.
For this application, I don’t think there would be any issue, but for
some PHP, you really need to control what gets output to the browser,
because you can’t send headers after content has been sent, for example.
In that case, you could still get away with this trick by putting all
of your code inside the Before HTML slot of the Page / HTML Markup
dialog. That would put your code outside of the bare-bones HTML page
skeleton, and if your PHP ended with the function exit;, then that
vestigial page code would be ignored entirely and never output.
Walter
On Jul 22, 2010, at 2:36 AM, chuckamuck wrote:
A second problem came from me trying to handle Alec’s guidance
within FWP.Actually, that is still possible to do in FWP. In Freeway you would
create a new page and name it path.php. Then you would add a single
markup item to the page, and nothing else, and insert the code into
that. As long as you don’t do anything else to the page (including
making sure there is no styled Master page assigned to it) then the
only thing that will publish on that page is the markup text you
inserted.
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
… because you can’t send headers after content has been sent, for example.
Yep, hadn’t considered the page would still have a header on output. For a pure unformatted page that wouldn’t work without some action trickery. I had thought of mentioning your suggestion but wasn’t sure where in the page markup it would need to go (before/after head) and didn’t have time to test.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yeah, this has tripped me up in the past, and it can be a royal pain
to debug. One trailing space after a tag can be enough to send the 200
header to the browser, and after than, you have no right to send a
301/2 to redirect the browser to a different URL.
Walter
On Jul 22, 2010, at 12:10 PM, chuckamuck wrote:
… because you can’t send headers after content has been sent, for
example.Yep, hadn’t considered the page would still have a header on output.
For a pure unformatted page that wouldn’t work without some action
trickery. I had thought of mentioning your suggestion but wasn’t
sure where in the page markup it would need to go (before/after
head) and didn’t have time to test.
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