Re: where have my family_html pages gone?

11 views
Skip to first unread message

the cohens

unread,
Nov 27, 2024, 8:18:55 PM11/27/24
to rw-webs...@googlegroups.com

Folks,

Happy Thanksgiving!

As I mentioned before, something seems to have happened when I added an SSI to almost all of my family_html pages, that is resulting in 403 Errors.  I thought I had checked to make sure that the pages were accessible after I ftp'd the revised pages to Rootsweb, but that was last December or January and I cannot be sure I did at this point.  Sometimes when I would edit files and then upload them, they became inaccessible until I run a chmod on the server.

So it is possible that happened - I was much too ill after that, to have time to carefully  check things up until now, when it is too late as we no longer have ftp access.

But another possibility is that my adding the following line to the pages that are now 403's somehow messed the pages up, although I recall testing and thinking they worked.  But I was not able test every single page.  They gave us plenty of warning, but I was just too ill.  Here is the code I added:

<!--#include file="freepages-top.txt" -->

That "freepages-top.txt" file just said the site was becoming read-only, and gave links to my alternate genealogy sites.

But I believe a 403 error means there is a permission thing, making me think it is more likely to be that the pages turned inaccessible when I uploaded the revised versions.

And I found a page which I did not revise with the others.  And that page is still accessible.  It has an SSI error, but is still online:

http://freepages.rootsweb.com/~thecohens/family/kaminskymarriages.html

It is too bad that what I did to make my work more findable, actually may have taken it beyond reach!  It is possible I put the revised files in a wrong directory, I don't think so, but certainly possible although unlikely.  Since I use command line ftp, my control of where my files go when I upload is much better than it would be if I used a GUI ftp client.

All I can do is shake my head, it has to be I did not check and correct the permissions.  Unfortunately, I was unable to do so before our sites went read-only.

Thanks to all who tried to help with this.

Barry Carlson

unread,
Nov 27, 2024, 11:53:28 PM11/27/24
to rw-webs...@googlegroups.com

I've had a look at - 

https://freepages.rootsweb.com/~thecohens/family/kaminskymarriages.html

- and [an error occurred while processing this directive] is displayed below the headings on the page.  This leads me to believe that the freepages-top.txt file is actually missing, or the link to it is incorrect.  Otherwise, if the current server didn't have  SSI activated, the SSI mark-up would have been treated as a comment and not displayed by the browser, though visible in the mark-up rendered by the server.

Barry

On 28/11/2024 2:18 pm, the cohens wrote:
<!--#include file="freepages-top.txt" -->

Pat Asher

unread,
Nov 30, 2024, 5:37:53 PM11/30/24
to rw-webs...@googlegroups.com
According to my no longer reliable memory, RootsWeb/Ancestry removed support for SSI (Server Side Includes) many years ago -- perhaps around the time Ancestry purchased Rootsweb in late 2002 or shortly therafter. Regardless of my faulty memory as to when, it is obvious SSI is no longer supported. I also used to use SSI files, but have now switched to Javascript for those types of file inserts. However, since files on the Rootsweb Server(s) can no longer be updated, I can't offer a solution to the problem.

Pat

Barry Carlson

unread,
Nov 30, 2024, 7:24:07 PM11/30/24
to rw-webs...@googlegroups.com

Pat,

The mark-up in https://freepages.rootsweb.com/~thecohens/family/kaminskymarriages.html below the Headings was

<!--#include file="freepages-top.txt" -->

which would still be there in the mark-up as a <!--comment--> if SSI wasn't activated on the server.  It has been replaced by the [an error occurred while processing this directive] because SSI is activated on the server.

Changing the subject; I note that Freepages-Help archive has been removed from the server.  Check using the link shown near top of page in this file:-

https://freepages.rootsweb.com/~bristowe/misc/ssi/ 

Which leads me to stating that I removed all my RW files from the server, except one family in ~bristowe/genealogy/ and another file in ~bristowe/nostalgia/.  I now find that all of them have been restored - not by me!  The SSI link in the misc/ssi directory was recovered from Pat Geary's website.  I can now find any file I originally loaded to server by checking for them in the files I downloaded, then 'deleted' from the server. 

Apologies to Pat Geary; I never thought to check with her before removing everything. My mistake has obviously been corrected. 

Happy Anniversary,

Barry

-------------------------

Barry Carlson

unread,
Dec 1, 2024, 6:24:29 PM12/1/24
to rw-webs...@googlegroups.com

Pat A.

Apologies; I must have been 'away with the fairies.'

I really meant to write - Happy Thanksgiving.

Barry

---------------------

On 1/12/2024 1:23 pm, Barry Carlson wrote:

Happy Anniversary

Pat Asher

unread,
Dec 2, 2024, 4:39:33 PM12/2/24
to rw-webs...@googlegroups.com
The fairies were right. I actually had an anniversary on the 29th. But there may be something wrong with your computer clock. You posted anniversary wishes on 11/30/2024 EST, not 11 months ago on 1/12/2024 😉

Pat

Barry Carlson

unread,
Dec 3, 2024, 3:28:34 PM12/3/24
to rw-webs...@googlegroups.com

Yep, looks like it's rather slow, like me.😳

Just one of the problems of living in a world that runs on time, yet we can't agree on how to communicate it.

Here's an image of the front page of the New Zealand Herald published on Monday 17 February 1986.

https://www.unicornbooks.co.nz/uploads/photos/95666.jpg

Yes, you'll recognise /recognize the date format - Monday, February 17, 1986.  When it comes to newspapers, somethings never change.

BTW, the leading article - the sinking of the "Mikail Lermontov", reminds me that "somebody's friend", Vladimir Putin was the Political Commissar onboard the vessel.

Whoops! I might be getting ahead of time! 😎

Barry

------------------------

--
Website FAQs: https://sites.rootsweb.com/~gearyfamily/rootsweb-hosted-web-sites.html
FTP FAQs: https://sites.rootsweb.com/~gearyfamily/publishing-your-sites.html
To contact the owners of this group, write to rw-website-...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "RootsWeb-Website-Help" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rw-website-he...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rw-website-help/87c0597e-a925-4b1d-835b-f36f71358c88%40att.net.

Pat Asher

unread,
Dec 3, 2024, 4:55:19 PM12/3/24
to rw-webs...@googlegroups.com
Paper newspapers are almost an anachronism any more, but since the digital versions still use the same date format, there must be a reason -- which brings up an interesting question about date formats -- does anyone know why the genealogy community decided on the DD MMM YYYY format instead of the MMM DD, YYYY format as their standard?

After many years doing genealogy research, I tend to use the DD MMM YYYY format almost automatically, which can create a problem when writing checks, or dating any legal document. Strange world we live in, lol

Pat A.

jecr...@twc.com

unread,
Dec 3, 2024, 5:10:44 PM12/3/24
to rw-webs...@googlegroups.com

It may be that in the United Kingdom and, in fact, most of the rest of the world, today’s date would be indicated 9 April 2012 or 9/4/12. In the U.S., it would be April 9 (or 9th), 2012, or 4/9/12. We tend to think (as in most things) that we are doing it the “normal” way, but, Europe Blog notes, “The only countries that do not share the European date format in fact are the US, Philippines, Palau, the Federated States of Micronesia, Canada and Belize.”    And many of the records from the 1700 Colonial America follow  DD/MM/YYYY format.

Joe C

--

Website FAQs: https://sites.rootsweb.com/~gearyfamily/rootsweb-hosted-web-sites.html
FTP FAQs: https://sites.rootsweb.com/~gearyfamily/publishing-your-sites.html
To contact the owners of this group, write to rw-website-...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "RootsWeb-Website-Help" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rw-website-he...@googlegroups.com.

Mary Richardson

unread,
Dec 3, 2024, 5:30:14 PM12/3/24
to rw-webs...@googlegroups.com
I have used DD-MMM-YYYY for years, especially in my genealogy recordings.  It's so much more logical than the way we express dates here in the U.S.  Even my antiquated Eudora email client has  switched to a day-month-year format.  See the timestamps below:  03-12-24 (Dec 3 2024).  Now, if everyone would just adopt military time, so we don't have to write AM or PM!

Mary Richardson
Virginia, USA


At 05:10 PM 03-12-24, jecr...@twc.com wrote:
It may be that in the United Kingdom and, in fact, most of the rest of the world, today's date would be indicated 9 April 2012 or 9/4/12. In the U.S., it would be April 9 (or 9th), 2012, or 4/9/12. We tend to think (as in most things) that we are doing it the "normal" way, but Europe Blog notes, The only countries that do not share the European date format in fact are the US, Philippines, Palau, the Federated States of Micronesia, Canada and Belize.  And many of the records from the 1700 Colonial America follow DD/MM/YYYY format.

Kerry L. Turley

unread,
Dec 3, 2024, 7:46:00 PM12/3/24
to rw-webs...@googlegroups.com

Interestingly the United States Military uses the format 12 Feb 2024, possibly so there is no misunderstanding with other countries. 

Kerry T.

Barry Carlson

unread,
Dec 3, 2024, 8:55:03 PM12/3/24
to rw-webs...@googlegroups.com

Kerry,

That's a correct assumption. North Atlantic Treaty Organisation (spelt differently to suit, just like time), will cover all that really matters.

Barry

----------------

Barry Carlson

unread,
Dec 3, 2024, 9:53:48 PM12/3/24
to rw-webs...@googlegroups.com

All,

Just a reminder, the International Organisation for Standardisation - ISO, provides -

ISO 8601

When dates are represented with numbers they can be interpreted in different ways. For example, 01/05/22 could mean January 5, 2022, or May 1, 2022. On an individual level this uncertainty can be very frustrating, in a business context it can be very expensive. Organizing meetings and deliveries, writing contracts and buying airplane tickets can be very difficult when the date is unclear.

ISO 8601 tackles this uncertainty by setting out an internationally agreed way to represent dates:

YYYY-MM-DD

Therefore, the order of the elements used to express date and time in ISO 8601 is as follows: year, month, day, hour, minutes, seconds, and milliseconds.

For example, September 27, 2022 at 6 p.m. is represented as 2022-09-27 18:00:00.000.

ISO 8601 can be used by anyone who wants to use a standardized way of presenting:

  • Date
  • Time of day
  • Coordinated Universal Time (UTC)
  • Local time with offset to UTC
  • Date and time
  • Time intervals
  • Recurring time intervals

 ------------------------------

- but, the best laid plans of mice and ....  Though in all matters that include the crossing of international borders, ISO 8601 is accepted.

I'm not surprised that genealogy uses the dd mmm yyyy format; it is a rational means of stating something that relates to everyday living. Newspapers have got a lot to answer for - or is it the Mayfair Pilgrims? 😇

Barry

------------

Charles Dobie

unread,
Dec 3, 2024, 10:13:20 PM12/3/24
to Barry Carlson, 'Carol Regehr' via RootsWeb-Website-Help
I'm glad to see this -- didn't realize it was ISO anything, but that's the date format I always use, mainly because when I have a large text list, with each line starting with a date, the YYYY-MM-DD format makes it dead easy for my text editor to sort.

Chas. Dobie.
Reply all
Reply to author
Forward
0 new messages