> > ---------------------------------------------------------------------- > > Date: Thu, 16 Aug 2018 11:08:50 +0000 > From: Bruce Coyne <nyjester@live.com> > Subject: [FreeHelp]Re: Editing and Testing Webpages > To: "freepages-help@rootsweb.com" <freepages-help@rootsweb.com> > Message-ID: <BN6PR15MB1876590CFE81900F9F12D891AB3E0@BN6PR15MB1876.namp > rd15.prod.outlook.com> > Content-Type: text/plain; charset="utf-8" > > 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 > > > > I certainly agree that testing html files locally with browsers is a good idea, and with several different major browsers as well. With some packages such as Expression Web there is even a built in "pseudo browser" you can use to test a lot things, though not everything. I was though trying to minimize the number of steps that Neil has to cope with just now. Once he gets a basic procedure working for him, then he can branch out and try other techniques. Best regards, -- Charlie Carothers http://www.freebiblecommentary.org <http://freebiblecommentary.org>