Still very frustrated. The more information posted here, all the blogs,etc. and I get more and more confused. My sites, one for my local Genealogical Society, and one for my county Cemetery Preservation Group, have been up for quite some time. I have had passwords for both sites approved, and I still get message that I am not authorized to access them. What gives? For some of us old fogies, we were very spoiled by using the defunct on line editor, and when those went away, tried learning the ftp protocols, and even with personal local webpage techs help, could not even get file zilla to work. Then the sites were down for almost 7 months, and now downloading the latest updated file zilla, still stuck. Surely there is a better online file manage that could be part of rootsweb again. Seems even the techy people are having difficulty with their websites, and they know way more than I do! What IS the problem???? Sent from my iPhone

On 16/08/2018 13:34, JFlorian wrote: > I had tried the clear but text was still wonky in Normal View in > Frontpage2000. Same when I tried it again after you both posted. Judy, As you well know, when you are using tables, the vertical alignment of text in a cell is an easy feat, i.e. <!--// <td> some text...</td> //--> ...and the text will be in the "middle" of the cell.  However, it can also be aligned using - style="vertical-align:middle" This simplicity is lost when using divs, other than when using -  div {     height: 200px;     display: table-cell;     vertical-align: middle;         } When you are floating a div, it doesn't want to be told to also display: table-cell, so that functionality is not available. The next method is to wrap your text in a <p> tag and use the following styles - div p {     position: relative;     top: 50%;     } ... which pushes the top of the text to 50% of the height in the div; still not vertically aligned in the middle. The trick that will make it do what you want is the following:- div {     float: right;     width: 400px;     height: 200px;     } div p {     position: relative;     top: 50%;     transform: translateY(-50%);     } .... which calculates the height of the contents in the <p> tag and moves the text upward by 50% of that height, i.e. the text is vertically aligned in the "middle". Now, this wont show correctly in Frontpage, but in any modern browser it will. The following example will also show you - check the source code. http://countjustonce.com/test/florian-test-float.html Barry

At 09:34 PM 8/15/2018, JFlorian wrote: >Pat A. & Barry, > >I had tried the clear but text was still wonky in Normal View in >Frontpage2000. Same when I tried it again after you both posted. For the paragraph, you need to over ride the alignment for class .imglft by adding a local vertical-align, i.e. <.p> <.img class="imglft" src="../../general-info/5ws.jpg" width="323" height="156" ALT="5 Ws Who What When Where Why" style="vertical-align: middle;"> General Information<./p> That is assuming you use class .imglft on various pages for various content sizes. <.div class="clear"> has no effect because the image float was already cleared when you closed the block-level paragraph element. Remember however, that you should design to the small display, rather than a big computer screen. If you vertically align text in your column layouts, they may create awkward spacing on a small screen when associated columns float below rather than side by side. Pat A. >Put the page through validator. No errors. > >As well, though, a simple header using img float left is also off. The >words beside the pic won't stay where it belongs, halfway between the >height of the pic. Right now, the words. General Information are hugging >the bottom right corner of the pic, both in Fp and in Browser Preview in >Chrome. > >It's simply: > ><.p><.img class="imglft" src="../../general-info/5ws.jpg" width="323" >height="156" ALT="5 Ws Who What When Where Why">General Information</p> ><.div class="clear:left"></div> > >Maddening!

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

Thanks Anne that all sounds good Can I request this site it had maps that were very good. Like a 1900 London pocket map http://freepages.genealogy.rootsweb.ancestry.com/~nmfa/genealogy.html I tried as http://sites.rootsweb.com/~nmfa but Forbidden came up I did apply for my own site to come back. it was "lankshear" for research into anyone found using that surname and Lankesheer etc I assume I am in your "in-tray" Is it possible to publish a list of sites in progress I used ronlank@yahoo.com.au for my site and had a password for that but I assume I use the new password that the Blog etc said to set up. Can I also have this gmail id as an alternative for the future Thank You from Ron Lankshear Sydney NSW Awaiting Recovery http://sites.rootsweb.com/~lankshear On 17/08/2018 3:50 AM, Anne Mitchell wrote: > I am happy to restore sites upon request. And we are working on restoring > a lot more sites once we've finished sorting out the freepages URLs. > > But again, we can't promise that every will live "forever." > > I don't anyone who can promise that. > > On Wed, Aug 15, 2018 at 6:43 PM JFlorian <cageycat@gmail.com> wrote: > >

I whole heartedly agree. While I can understand a priority being sites with active web-builders adding, changing, improving, I think once the restore requests die down, the remaining sites must be restored. Cecil -----Original Message----- Subject: [FreeHelp]Re: Thanks for Restoring Tom Pick's Website Susan wrote: This site http://sites.rootsweb.com/~pick/ is the perfect example of the value of restoring all sites even if no one claims them for editing. All the links (including in Ancestry databases) would work again, and the effort that went into the sites would continue to be appreciated and used. --- Well said! I firmly believe all sites should be restored. Period. IF not for RW's ancient coding, the "security breach" would never have been a breach, and all the people who died believing their sites would live on would not now have their sites potentially "killed". If RW won't restore everyone's, what will happen to ours when we die? Why am I doing all this work if it'll all just get dumped? Judy ------------------------------ --- This email has been checked for viruses by AVG. https://www.avg.com

If you subscribe to Ancestry, see also https://search.ancestry.com/search/db.aspx?dbid=3693. At 03:39 PM 8/16/2018, Susan W Pieroth wrote: >https://ssdmf.info/ - currently up to 2013. > >There is a note at the top of the page that states: > >Google jinxed this website, and it won't even come up when you enter >the domain name into the Google search bar. You must enter the >domain name into your browser's location window at the top of the screen.

https://ssdmf.info/ - currently up to 2013. There is a note at the top of the page that states: Google jinxed this website, and it won’t even come up when you enter the domain name into the Google search bar. You must enter the domain name into your browser’s location window at the top of the screen. Susan

I am happy to restore sites upon request. And we are working on restoring a lot more sites once we've finished sorting out the freepages URLs. But again, we can't promise that every will live "forever." I don't anyone who can promise that. On Wed, Aug 15, 2018 at 6:43 PM JFlorian <cageycat@gmail.com> wrote: > Susan wrote: > This site http://sites.rootsweb.com/~pick/ is the perfect example of the > value of restoring all sites even if no one claims them for editing. All > the links (including in Ancestry databases) would work again, and the > effort that went into the sites would continue to be appreciated and used. > --- > > Well said! I firmly believe all sites should be restored. Period. IF > not for RW's ancient coding, the "security breach" would never have been a > breach, and all the people who died believing their sites would live on > would not now have their sites potentially "killed". > > If RW won't restore everyone's, what will happen to ours when we die? Why > am I doing all this work if it'll all just get dumped? > > Judy > > _______________________________________________ > 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 >

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

Susan wrote: This site http://sites.rootsweb.com/~pick/ is the perfect example of the value of restoring all sites even if no one claims them for editing. All the links (including in Ancestry databases) would work again, and the effort that went into the sites would continue to be appreciated and used. --- Well said! I firmly believe all sites should be restored. Period. IF not for RW's ancient coding, the "security breach" would never have been a breach, and all the people who died believing their sites would live on would not now have their sites potentially "killed". If RW won't restore everyone's, what will happen to ours when we die? Why am I doing all this work if it'll all just get dumped? Judy

Pat A. & Barry, I had tried the clear but text was still wonky in Normal View in Frontpage2000. Same when I tried it again after you both posted. Put the page through validator. No errors. As well, though, a simple header using img float left is also off. The words beside the pic won't stay where it belongs, halfway between the height of the pic. Right now, the words. General Information are hugging the bottom right corner of the pic, both in Fp and in Browser Preview in Chrome. It's simply: <.p><.img class="imglft" src="../../general-info/5ws.jpg" width="323" height="156" ALT="5 Ws Who What When Where Why">General Information</p> <.div class="clear:left"></div> Maddening!

This site http://sites.rootsweb.com/~pick/ is the perfect example of the value of restoring all sites even if no one claims them for editing. All the links (including in Ancestry databases) would work again, and the effort that went into the sites would continue to be appreciated and used. Susan On 8/15/2018 7:37 PM, Dave Hein via FREEPAGES-HELP wrote: > I would like to thank the RootsWeb staff for restoring Tom Pick's website on births and marriages in the Eifel region.  All the links in the website seem to be working correctly, and even my links to the site work.  I thought that I may have to modify my freepages.genealogy.rootsweb.com links to sites.rootsweb.com, but it appears that the server automatically converts them when they are referenced.  Great work by the RootsWeb team.

I would like to thank the RootsWeb staff for restoring Tom Pick's website on births and marriages in the Eifel region.  All the links in the website seem to be working correctly, and even my links to the site work.  I thought that I may have to modify my freepages.genealogy.rootsweb.com links to sites.rootsweb.com, but it appears that the server automatically converts them when they are referenced.  Great work by the RootsWeb team.

At 03:41 PM 8/15/2018, JFlorian wrote: >Pat A., > >Regarding the floats, such as: >.column2a {width: 50%; float: left;} >.column2b {width: 50%; float: left;} > > >How do I push content below to stay down (rather than floating to the >right)? Judy, you have to insert a block level element that fills the width of the page to prevent subsequent floats from sliding up to fill the empty space. You could use <.hr style="width: 100%; clear: both;"> choosing a background color so it shows or does not; but my preference is to insert a div with a class that I have defined in my style sheet as .clear {clear: both;} At the end of the column2a and column2b sections (or any number of columns), insert <div class="clear"></div> That stops a subsequent float from floating up where you don't want it, is easy to remember, and does not affect established line/paragraph spacing. Pat A.

Judy, I'm obviously not Pat A, but you require to clear the floats as per:- https://www.w3schools.com/css/css_float.asp Barry On 16/08/2018 07:41, JFlorian wrote: > Pat A., > > Regarding the floats, such as: > .column2a {width: 50%; float: left;} > .column2b {width: 50%; float: left;} > > > How do I push content below to stay down (rather than floating to the > right)? > > Having to use 50 some paragraph tags ... because multiple br tags won't > keep the rest of the page down. > > Tried clear but not sure I used the right wording. > > Ideas? > > Judy >

Pat A., Regarding the floats, such as: .column2a {width: 50%; float: left;} .column2b {width: 50%; float: left;} How do I push content below to stay down (rather than floating to the right)? Having to use 50 some paragraph tags ... because multiple br tags won't keep the rest of the page down. Tried clear but not sure I used the right wording. Ideas? Judy

Hi Eve, I'm the one you need to give evidence to :-) Yours was more than convincing and the old address was obviously yours. I've updated your account. Here are the instructions. First, you will need to reset your password. Go to: https://useraccount.rootsweb.com/websites/requestChangePassword And enter the email address you believe is connected to the account. If you don't receive the email, check your spam folder. Click on the link and follow the steps to reset your password. Passwords must be between 10 and 32 characters long, and must contain at least one uppercase letter, one lowercase letter, one number, and one of the following special characters: _ ! @ # ( ) DO NOT use the * or & characters!!! You must click the box to accept the Terms and Conditions and Privacy Statement. Once you have done that, you can access your site. We do not support fileman any longer, and will not be bringing it back. You may use any FTP client to access the site that supports the current version of SFTP. This short video will show you how to use FileZilla to access your site. https://www.ancestry.com/academy/course/connect-rootsweb-filezilla The host you will be connecting to is: sftp://sitesuser.rootsweb.com You can find your site using two different URLs https://www.rootsweb.com/~sitename or https://sites.rootsweb.com/~sitename Your RootsWeb Team On Wed, Aug 15, 2018 at 8:57 AM, Eve Gregory <pgva368@hotmail.com> wrote: > Hi everyone, > > I just found one of my sites up on Rootsweb. I was glad to see it, so I > went to the reclaim page and gave it my current email address. But it > is not the same email address that I had when I created the page in > 1999. The page is for the Surry County, Virginia, Historical Society & > Museums, Inc., an all-volunteer charity. The web site is quite large, > consisting mostly of historical and genealogical information about Surry > County, VA that I have added over the last 19 years. > > http://sites.rootsweb.com/~vaschsm/ > > I've been the web master since 1999. I have the original email with > original password, host name, etc. and my email address at that time. My > email addresses have changed many times since then. I'm afraid the > regular system for reclaiming web pages might not work for this one, as > it is so old and so many things have changed over the years. And to add > to the difficulties, my house was struck by lightning in July, toasting > my main computer, so I've lost some emails. > > At this point, I need guidance about what evidence I need to provide, > and how to provide it, to reclaim the web site for the Surry County, VA > Historical Society. The Officers and Board of Trustees of the Society > can provide verification, if that is needed. Frankly, I don't know what > to do. Can someone help me? > > Eve S. Gregory > > Webmaster, Surry County, Virginia, Historical Society and Museums, Inc. > > On 8/15/2018 4:00 AM, freepages-help-request@rootsweb.com wrote: > > Send FREEPAGES-HELP mailing list submissions to > > freepages-help@rootsweb.com > > > > To subscribe via email send a message with subject subscribe and body > > subscribe to freepages-help-request@rootsweb.com > > > > To unsubscribe via email send a message with subject unsubscribe and > > body unsubscribe to freepages-help-request@rootsweb.com > > > > You can reach the person managing the list at > > freepages-help-owner@rootsweb.com > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of FREEPAGES-HELP digest..." > > > > When replying to a digest message, quote only the specific message to > which you are replying, removing the rest of the digest from your reply. > Remember to change the subject of your reply so that it coincides with the > message subject to which you are replying. > > ***FREEPAGES HELP & FAQ*** > > <http://helpdesk.rootsweb.com/FAQ/fpindex.html> > > > > Today's Topics: > > > > 1. Notes to Neil (Charles Carothers) > > 2. Re: Kompozer (Billie Walsh) > > > > > > ---------------------------------------------------------------------- > > > > Date: Tue, 14 Aug 2018 21:46:49 -0500 > > From: Charles Carothers <csquared71@gmail.com> > > Subject: [FreeHelp]Notes to Neil > > To: Freepages Help <freepages-help@rootsweb.com> > > Message-ID: > > <CAGmaTgzUBYX=BXWsCcKUN12M8bZV=xQJijgZA2uF4Y > mYF9QK_g@mail.gmail.com> > > Content-Type: text/plain; charset="UTF-8" > > > > 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, > > > > > > -- > Eve S. Gregory, Webmaster > Prince George County, Virginia > VAGenweb > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > > _______________________________________________ > 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 >

Hi everyone, I just found one of my sites up on Rootsweb.  I was glad to see it, so I went to the reclaim page and gave it my current email address.  But it is not the same email address that I had when I created the page in 1999.  The page is for the Surry County, Virginia, Historical Society & Museums, Inc., an all-volunteer charity. The web site is quite large, consisting mostly of historical and genealogical information about Surry County, VA that I have added over the last 19 years. http://sites.rootsweb.com/~vaschsm/ I've been the web master since 1999.  I have the original email with original password, host name, etc. and my email address at that time. My email addresses have changed many times since then.   I'm afraid the regular system for reclaiming web pages might not work for this one, as it is so old and so many things have changed over the years.  And to add to the difficulties, my house was struck by lightning in July, toasting my main computer, so I've lost some emails. At this point, I need guidance about what evidence I need to provide, and how to provide it, to reclaim the web site for the Surry County, VA Historical Society. The Officers and Board of Trustees of the Society can provide verification, if that is needed.  Frankly, I don't know what to do. Can someone help me? Eve S. Gregory Webmaster, Surry County, Virginia, Historical Society and Museums, Inc. On 8/15/2018 4:00 AM, freepages-help-request@rootsweb.com wrote: > Send FREEPAGES-HELP mailing list submissions to > freepages-help@rootsweb.com > > To subscribe via email send a message with subject subscribe and body > subscribe to freepages-help-request@rootsweb.com > > To unsubscribe via email send a message with subject unsubscribe and > body unsubscribe to freepages-help-request@rootsweb.com > > You can reach the person managing the list at > freepages-help-owner@rootsweb.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of FREEPAGES-HELP digest..." > > When replying to a digest message, quote only the specific message to which you are replying, removing the rest of the digest from your reply. Remember to change the subject of your reply so that it coincides with the message subject to which you are replying. > ***FREEPAGES HELP & FAQ*** > <http://helpdesk.rootsweb.com/FAQ/fpindex.html> > > Today's Topics: > > 1. Notes to Neil (Charles Carothers) > 2. Re: Kompozer (Billie Walsh) > > > ---------------------------------------------------------------------- > > Date: Tue, 14 Aug 2018 21:46:49 -0500 > From: Charles Carothers <csquared71@gmail.com> > Subject: [FreeHelp]Notes to Neil > To: Freepages Help <freepages-help@rootsweb.com> > Message-ID: > <CAGmaTgzUBYX=BXWsCcKUN12M8bZV=xQJijgZA2uF4YmYF9QK_g@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > 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, > > -- Eve S. Gregory, Webmaster Prince George County, Virginia VAGenweb --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

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,