All the links on the archive pages were updated to .net in that last move
that was done (by David) to our own, dedicated server. If you find links to
.org pages (except for the Tombstone Transcription pages), they can either
be changed or left alone. All new links should point to the .net server so
we're sure that we're linking to the most updated copy of a file available.
Also, not all of the errors are actually being found in our Archives pages.
Many errors are being generated by other pages that are looking for a file
that is no longer on the server, or is in a different folder. Those we have
no control over, other than being able to write to the owner of the
"referrer" link and ask them to update their link (please give them the
correct URL to the file if you can).
The numbers of errors will be expected to go down as we whittle on them. I
know that dozens of errors have already been solved by my uploading an image
to a folder where pages were looking for it - there may be others like this,
I've not checked through things thoroughly.
I know there are several errors that are being generated by the TP pages.
I'm still making my way through them to update all of the links so they
point to the proper places. I'm working on them, I promise! <g>
Sherri
-----Original Message-----
From: kyarc-bounces(a)rootsweb.com [mailto:kyarc-bounces@rootsweb.com] On
Behalf Of Thomas Hembrey
Sent: Friday, September 19, 2008 8:07 AM
To: KyArc FMs
Subject: [KYARC] Error log Question & Answer
Hi Dana
There are two things I can think of right now that may have an effect on
your situation.
1) The error log will repeat errors if it is parsing daily. I would
probably not check this log so frequently and let it go for at least a week
or two before making correcting to any errors. Then wait at least another
week to see if my edits were updated okay. Also, I would not let the error
log stipulate how I manage my web pages. These are, at the most, simple
simple code or html errors and do not pose any threat to how I maintain my
archives.
2) The FM uploads to the .net server and the public is directed to the .org
server to view our web sites. This is like a shadow of what we manage and
does not necessary show the current or most recent revisions we make. It
takes a few days for the two to synchronize and duplicate each other. Look
at the link for your web page and see if it contains .net or .org. I use
the .net link for everything and do not pay attention to the .org because of
this catch up game they use.
EXAMPLE:
http://www.usgwarchives.org/ky/breckinridge/toc.html - backup server not
current with edits or daily updates
http://www.usgwarchives.net/ky/breckinridge/toc.html - real-time server
shows edits and updates immediately
See if this info will help you manage the errors better???? Excellent
question, too !!! Have fun.
Tom
----- Original Message -----
From: brieskate
To: Thomas Hembrey ; Sherri
Sent: Thursday, September 18, 2008 7:44 PM
Subject: Errorlog Question
Hi Tom and Sherri....
Wanted to ask a quick question regarding the errorlogs I've signed up to
get each day. Do you all know when the errorlogs are generated? I've been
getting them regularly, and each night have been going in to correct the
error.... but I've found I've already corrected it last week or earlier on.
I didn't know if the errorlogs were literally from the same day we received
the email of the log, or if they were from another day (and if so, which day
it was).
I've held off on uploading any files or updates to the pages from work
(the uploading/updates are of the DC project the transcribers and I are
working on), but it's only now that I've been able to email and ask about it
due to a massive windstorm that knocked out power to 60% of the people in
Louisville. With things starting to settle down somewhat, I'm moving more
into a "work" mode and wanted to make sure all my ducks were in a row.
Y'all have a good one!
Dana
-------------------------------
To unsubscribe from the list, please send an email to
KYARC-request(a)rootsweb.com with the word 'unsubscribe' without the quotes in
the subject and the body of the message