The beta WorldConnect displays names and information about LIVING people!

I am also lucky enough that one of my trees has been imported to the new system, but the results are scarey. A bunch of people with dates of death on the old worldconnect are marked as "Person not viewable", and the following are missing from those who are viewable: - occupations - aliases - notes - sources there may be more types of data missing, I have not had a chance to check things like Residence and other sorts of tags, the above items were just what I discovered were missing quickly and easily. I hope they are not going to do away with the above forever. If they do, then all the fantatic transcriptions people have posted at worldconnect in the old version will be gone forever. And source references. There are other problems as well, such as descendancy charts not displaying properly (at least not in Firefox or text browsers), but I think the above missing data types are the most critical issue. On 4/3/19, Patricia Geary <pat@the-gearys.com> wrote: > Just posted in the Facebook group by Anne. > > ... > We are still importing all of the old GEDCOMs to the new system, and that > will take weeks. You can test out the new upload capability and please let > me know if it isn't working. > > > > https://wcbeta.rootsweb.com/

Apparently not. -----Original Message----- From: Pat Asher [mailto:pjroots@att.net] Sent: Wednesday, April 3, 2019 4:55 PM To: Freepages Web Sites <freepages-help@rootsweb.com> Subject: [FreeHelp]Re: RootsWeb World Connect At 01:24 PM 4/3/2019, Patricia Geary wrote: >Just posted in the Facebook group by Anne. > >I know, you thought we'd never get here, but we have the new version of >WorldConnect Beta ready for you to take a test drive. > >We are still importing all of the old GEDCOMs to the new system, and >that will take weeks. You can test out the new upload capability and >please let me know if it isn't working. > >https://wcbeta.rootsweb.com/ > > From Me. Only two of mine are available so be patient. Upload was easy. Does the upload for your available usercodes appear online at wc.rootsweb.com? Pat Asher _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/freepages-help@rootsweb.com 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

At 01:24 PM 4/3/2019, Patricia Geary wrote: >Just posted in the Facebook group by Anne. > >I know, you thought we'd never get here, but we have the new version of >WorldConnect Beta ready for you to take a test drive. > >We are still importing all of the old GEDCOMs to the new system, and that >will take weeks. You can test out the new upload capability and please let >me know if it isn't working. > >https://wcbeta.rootsweb.com/ > > From Me. Only two of mine are available so be patient. Upload was easy. Does the upload for your available usercodes appear online at wc.rootsweb.com? Pat Asher

A bit more information on the beta WorldConnect. You cannot replace your old tree with a new one as yet. You can set up your account and new password and upload a new tree to play with. Migration of old accounts will probably take 8-12 weeks according to Anne. Pat G

Just posted in the Facebook group by Anne. I know, you thought we'd never get here, but we have the new version of WorldConnect Beta ready for you to take a test drive. We are still importing all of the old GEDCOMs to the new system, and that will take weeks. You can test out the new upload capability and please let me know if it isn't working. https://wcbeta.rootsweb.com/ From Me. Only two of mine are available so be patient. Upload was easy. Pat G

Just posted in the Facebook group by Anne. I know, you thought we'd never get here, but we have the new version of WorldConnect Beta ready for you to take a test drive. We are still importing all of the old GEDCOMs to the new system, and that will take weeks. You can test out the new upload capability and please let me know if it isn't working. https://wcbeta.rootsweb.com/ From Me. Only two of mine are available so be patient. Upload was easy. Pat G

Thanks Charlie, As per my post to Vanessa, I'll do a write up and describe the best way of implementing it in a few days. Barry On 25/03/2019 07:18, Charlie Carothers wrote: > That is really cool Barry!!! >

Vanessa, Just give me a few days to put an understandable description together, and I'll post it here. Barry On 25/03/2019 01:47, vrstern@earthlink.net wrote: > Barry, > > I would really appreciate these instructions as I have several galleries to build. > > Vanessa > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/freepages-help@rootsweb.com > 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

That is really cool Barry!!! -- Charlie Carothers https://www.freebiblecommentary.org <http://www.freebiblecommentary.org> <http://freebiblecommentary.org>

Barry, I would really appreciate these instructions as I have several galleries to build. Vanessa

Recently when looking at a problem Vanessa had when floating thumb-nail images with a description in a photo gallery, I thought that there may be another method that could cater for portrait and landscape images while keeping a symmetrical layout. The result uses an unordered list and the magic of CSS to provide something that is functional in desktop / laptop and mobile devices. http://freepages.rootsweb.com/~bristowe/misc/thumbs-trial/ The images used represent objects and / or persons from 250 years old through to the present day. The last image in the gallery has, as well as the thumb-nail link, another link in the description. Portrait thumbs have their description with the text to their right, but oriented bottom to top. Hovering over the text will rotate everything plus 90 degrees for easy reading, and on a mobile, touching the description near the bottom right (orange star) will do the same thing. Resizing the browser width will allow the images to stack as required and likewise they will present in a single column for a mobile device. If there is any interest, I'll write up a description on how to do it. Barry

At 04:53 PM 3/22/2019, JFlorian wrote: >I haven't changed it. > >I like those columns. But I often have to use the clear both code before >and after. Yep, that is so whatever comes after is not affected by the specifications for a particular section. Ain't it fun -- not always! Pat

I haven't changed it. I like those columns. But I often have to use the clear both code before and after.

At 01:29 PM 3/22/2019, JFlorian wrote: >So on those column3a, 3b, 3c you gave me, are they responsive so they'd >shift to be a lego tower? As I recall, I suggested they all have the float: left; attribute, so yes they will shift based on the size of the screen. Pat Asher

So on those column3a, 3b, 3c you gave me, are they responsive so they'd shift to be a lego tower?

I have two Rootsweb websites.  One was a homepage and the second was a freepage.   They both would have had the same email address. I was able to successfully authenticate/connect to my homepage site, although I had to make 3 attempts in setting a password that was finally accepted. This password does not work on my freepages site -> http://freepages.rootsweb.com/~mollers/genealogy/ I'm very hesitant to attempt another password change as I don't want to lose access to my homepage site. What are my options here in creating a password that will work with my freepages site? thanks, Bonnie

At 01:10 PM 3/21/2019, Billie Walsh wrote: >I have some pages with very large graphics. With the tag I posted in >the header everything scales perfectly all the way down to vertical cell phone. > >That tag is also what Google wants to see in a pages hearer to >determine if the page is small device compatible. Billie, it depends on your layout. Suppose you have a division containing three columns you have displayed side by side on a full screen device. On a small screen device, the text in those columns could wrap to one word or less per line, or the text could be too small to read without zooming. A media query can instruct the device to display the columns one below the other on a small screen so the text remains intelligible. And check out the navigation menu (in red) in the header at usgenweb.org. On a large screen, the navigation links display side by side. But they wouldn't all fit that way on a small screen. Narrow a full size browser window and watch that navigation menu change to a drop-down menu where the links are listed below each other as in a standard List. Also watch the title area as you narrow the window. The USGenWeb logo shrinks until the screen reaches about 800 pixels, then it disappears entirely. As you make the window narrower yet, the Search box drops below the page title so both remain full size. Media queries can make your page look good on any size device, regardless of your original page layout. Pat Asher

On 03/21/2019 11:43 AM, Pat Asher wrote: > At 11:18 PM 3/20/2019, Billie Walsh wrote: >> Put this tag in the header >> >> <meta name="viewport" content="width=device-width, >> initial-scale=0.86, maximum-scale=3.0, minimum-scale=0.86"> > > Maximum and minimum scale define the maximum and minimum zoom allowed > on mobile devices. "initial-scale=0.86" sets the initial zoom level at > 86%. > > To deliver the page on any device at a scale of 1 CSS pixel being > equal to 1 viewport pixel, use > <meta content="width=device-width; initial-scale=1.0" name="viewport"> > > Adding this meta tag is a start will not make your site completely > mobile friendly unless everything on your pages will wrap or collapse > to the width of the viewing device. Media queries are usually needed > to rearrange elements for small screens. > > Pat Asher I have some pages with very large graphics. With the tag I posted in the header everything scales perfectly all the way down to vertical cell phone. That tag is also what Google wants to see in a pages hearer to determine if the page is small device compatible. -- "The dog is a gentleman. I hope to go to his heaven, not man's." Mark Twain

At 11:18 PM 3/20/2019, Billie Walsh wrote: >Put this tag in the header > ><meta name="viewport" content="width=device-width, >initial-scale=0.86, maximum-scale=3.0, minimum-scale=0.86"> Maximum and minimum scale define the maximum and minimum zoom allowed on mobile devices. "initial-scale=0.86" sets the initial zoom level at 86%. To deliver the page on any device at a scale of 1 CSS pixel being equal to 1 viewport pixel, use <meta content="width=device-width; initial-scale=1.0" name="viewport"> Adding this meta tag is a start will not make your site completely mobile friendly unless everything on your pages will wrap or collapse to the width of the viewing device. Media queries are usually needed to rearrange elements for small screens. Pat Asher