I would add one thing to Charlie's suggestions. It is much simpler to test the effect of changes in coding by running it first in a browser offline. I use Notepad++ for all my editing and after every change I will run the local, edited copy of the file in my browser in offline mode. Only when I am satisfied that everything is okay do I open up Filezilla and upload the file to the website. This keeps the website clean and free of any trials and I need to connect with the internet only once. In fact when I am doing something new, I will usually test the local program on a variety of browsers to see if any of them have an effect -- Chrome, Opera, Safari, Firefox, SeaMonkey, Edge, etc. Bill Gentry At 04:00 AM 8/15/2018, you wrote: >Hi Neil, > >Just a few random thoughts that might be helpful. > >There may be a way inside Filezilla to launch Kompozer for a file (or with >any editor of choice), but I never do it that way. I use the editor to edit >and Filezilla to upload. Period. They are two separate software packages >and are not related in any way I am aware of. Keeping that concept in mind >is important. > >The left pane in Filezilla represents your local copy of your site >directories and files on your local hard drive on your local computer. Left >== Local. That's really important too. Always, always, always edit only >your local files. If you don't know where they are, but can open them in >Kompozer I understand that it will show you where they are. Make a note of >that so you will always know where they are. If you can open them with >Kompozer, then you are ready to edit them as you desire. If not, find them >first. Once you find them, drawing a macro level sketch of your local >directory structure is not a bad idea. You could note the entire path to >your highest level directory on that same piece of paper - surely wouldn't >hurt. At the risk of confusing you further, here is the entire path to the >highest level directory where I work most of the time. >D:\0ACCStuff\CCDoc\BLITestWebSite\public_html. Please remember that is only >an example. Your path will definitely be different!!! It will start with a >drive letter, usually C: or D: are the two most likely values I think. The >most important thing to note about that path is that public_html is the >name of the highest level directory on both my local hard drive and the >remote host. Making that so has saved me no end of confusion. > >File Explorer is a great tool for finding things. I think unfortunately >microsoft does not show it on the home screen by default. (Another of their >poor decisions.) If it is not visible, click on Start and find it. Right >click on it and select Send To Desktop or Pin To Taskbar, whichever is >available. (It's been almost 2 years since I did that, and I've forgotten >the details.) As I sit here looking at my windows-10 screen, the icon for >it is sitting in the taskbar just to the right of the calculator. But your >view will almost certainly be different. Then use it to find the file you >want to edit. Right click on it and select Open With - Kompozer. > >When you are done editing the file and want to send it to your site, save >it, fire up Filezilla, navigate until you an see the file you just edited >in the local pane, make sure the remote/right-hand pane is showing the same >directory, right click on the file in the left pane and select Upload. If >it asks for permission, allow it. > >Open your browser and go to your web site. View the page associated with >the file you just edited and uploaded. If you are me, see what you did >wrong and go back to the edit step to try to correct it. Repeat the entire >edit/save/upload/check process until you are happy with the results. Only >you are the judge of the suitability of your web site. Others may express >differing opinions, but you are The Man as far as your web site is >concerned. And isn't that great! At times, I must confess it seems almost >magical. :-) > >And that, in probably too many words, describes my work flow for >maintaining the site below my signature. Are there exceptions to many of my >statements above? You betcha!!! But from what you've said so far, my >perception is that you need to get this basic sequence ingrained. Once >you've done that, then you can branch out if you so desire. > >And above all, "Never ever quit!" (OK, that's the mantra of my favorite >baseball team.) But I think it's good advice here too. > >Best regards,

I do the same thing. The master copy of the site is in a folder on my computer and the public site is a copy of that.   Notepad++ is a great free editor. Bruce COyne On 8/15/2018 9:55 AM, Bill Gentry wrote: > I would add one thing to Charlie's suggestions.  It is much simpler to > test the effect of changes in coding by running  it first in a browser > offline.  I use Notepad++ for all my editing and after every change I > will run the local, edited copy of the file in my browser in offline > mode.  Only when I am satisfied that everything is okay  do I open up > Filezilla and upload the file to the website. This keeps the website > clean and free of any trials and I need to connect with the internet > only once. In fact when I am doing something new, I will  usually test > the local program on a variety of browsers to see if any of them have > an effect -- Chrome, Opera, Safari, Firefox, SeaMonkey, Edge, etc. > > Bill Gentry > > At 04:00 AM 8/15/2018, you wrote: >> Hi Neil, >> >> Just a few random thoughts that might be helpful. >> >> There may be a way inside Filezilla to launch Kompozer for a file (or >> with >> any editor of choice), but I never do it that way. I use the editor >> to edit >> and Filezilla to upload. Period. They are two separate software packages >> and are not related in any way I am aware of. Keeping that concept in >> mind >> is important. >> >> The left pane in Filezilla represents your local copy of your site >> directories and files on your local hard drive on your local >> computer. Left >> == Local. That's really important too. Always, always, always edit only >> your local files. If you don't know where they are, but can open them in >> Kompozer I understand that it will show you where they are. Make a >> note of >> that so you will always know where they are. If you can open them with >> Kompozer, then you are ready to edit them as you desire. If not, find >> them >> first. Once you find them, drawing a macro level sketch of your local >> directory structure is not a bad idea. You could note the entire path to >> your highest level directory on that same piece of paper - surely >> wouldn't >> hurt. At the risk of confusing you further, here is the entire path >> to the >> highest level directory where I work most of the time. >> D:\0ACCStuff\CCDoc\BLITestWebSite\public_html. Please remember that >> is only >> an example. Your path will definitely be different!!! It will start >> with a >> drive letter, usually C: or D: are the two most likely values I >> think. The >> most important thing to note about that path is that public_html is the >> name of the highest level directory on both my local hard drive and the >> remote host. Making that so has saved me no end of confusion. >> >> File Explorer is a great tool for finding things. I think unfortunately >> microsoft does not show it on the home screen by default. (Another of >> their >> poor decisions.) If it is not visible, click on Start and find it. Right >> click on it and select Send To Desktop or Pin To Taskbar, whichever is >> available. (It's been almost 2 years since I did that, and I've >> forgotten >> the details.) As I sit here looking at my windows-10 screen, the icon >> for >> it is sitting in the taskbar just to the right of the calculator. But >> your >> view will almost certainly be different. Then use it to find the file >> you >> want to edit. Right click on it and select Open With - Kompozer. >> >> When you are done editing the file and want to send it to your site, >> save >> it, fire up Filezilla, navigate until you an see the file you just >> edited >> in the local pane, make sure the remote/right-hand pane is showing >> the same >> directory, right click on the file in the left pane and select >> Upload. If >> it asks for permission, allow it. >> >> Open your browser and go to your web site. View the page associated with >> the file you just edited and uploaded. If you are me, see what you did >> wrong and go back to the edit step to try to correct it. Repeat the >> entire >> edit/save/upload/check process until you are happy with the results. >> Only >> you are the judge of the suitability of your web site. Others may >> express >> differing opinions, but you are The Man as far as your web site is >> concerned. And isn't that great! At times, I must confess it seems >> almost >> magical. :-) >> >> And that, in probably too many words, describes my work flow for >> maintaining the site below my signature. Are there exceptions to many >> of my >> statements above? You betcha!!! But from what you've said so far, my >> perception is that you need to get this basic sequence ingrained. Once >> you've done that, then you can branch out if you so desire. >> >> And above all, "Never ever quit!" (OK, that's the mantra of my favorite >> baseball team.) But I think it's good advice here too. >> >> Best regards, > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe and Archives > https://mailinglists.rootsweb.com/listindexes/search/freepages-help > Privacy Statement: https://ancstry.me/2JWBOdY  Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community