RootsWeb.com Mailing Lists
Total: 3/3
    1. Re: [ROOTSWEB-HELP] Bad code or bad program?
    2. J.A. Florian
    3. Hi Charles, About the easiest way to fix errors "en mass" is, first, take one item reported as an error. Second, look at the code in several of your pages. See if you can identify something COMMON either right before or right after the place where the code needs changed. For example, I use Frontpage 2000 and it uses charset=windows-1252 in the HEAD. I needed to change it to charset=iso-8859-1 So I opened Edit>Replace and put charset=windows-1252 then in Replace With I put just charset=iso-8859-1 I didn't need to use the entire line of code, just a piece that had the same sequence or placement for the code. I bet many of those 10,000 errors have some "exact" sequence like my example and if you can identify one, it will be easy to do Find>Replace. If possible, stop the "search" after it finds 20 or 30 instances...change those...upload...make sure everything is okay with that change. Then do another set of pages. In Frontpage2000, the user has to click to OK every item changed, but I think someone said EW will do global. If I can sit and hit OK hundreds of times, anyone can do a replace with better software. :-D Don't try to do it in one day, but set smaller goals. Run a validator and copy/print the error list (or just part of it). Look over the list and after looking at the code on a few pages, mark just a few errors on the paper list-- ones you can identify as the easiest to change or that can be an automated Find/Replace task. Think about how many pages you have and set a goal for each day (example: do 20 pages each night to fix JUST ONE error). Then, get a cup of coffee and complete your goal. Don't forget to reward yourself afterwards--- stretch, get a snack, take a walk, watch a TV show, anything to clear your head from all that work. If you have a big site, it will take time but the satisfaction is worth it. When you get 1 error fixed, cross it off the paper list and pick another one to work on. The closing tags will be the worst because it will likely be all manual work. :-( But you can tackle the ones that Find/Replace can fix, and worry about the other errors next. Cheering you on for the work ahead, Judy On Wed, Dec 23, 2009 at 2:16 PM, Charles Barnum <jcnreno@charter.net> wrote: > http://www.rootsweb.ancestry.com/~nma/sierra/tierra_blancacemetery.htm > > I bought Expressions Web 3 as an upgrade to FrontPage2007 with the goal > of changing all of my code from html to xhtml and to change all of my > tables so fire Fox could read them equally as well as a MS Broswer. > I have been working months converting the web site. The more I use EW3 > the more I dislike it and have gone back to FrontPage for most tasks > except for making truly new pages. > EW3 appears to make far more work than I can accomplish. The web page > http://www.rootsweb.ancestry.com/~nma/sierra/tierra_blancacemetery.htm > looks fine on both Fire Fox and MS I.E.8. > But like on so many other pages, I have left in code errors, probably > exceeding 10,000 errors in the web site. > This page of current interest displays code errors from EW3's code > checker. For Instance, it says "the center tag was not closed before > this </boby> tag" And several "the center tag was not closed before > this <tr> tag." > <snipped>

    12/23/2009 11:12:13
    1. Re: [ROOTSWEB-HELP] Bad code or bad program?
    2. Tina Clarke
    3. > The closing tags will be the worst because it will likely be all manual > work. :-( But you can tackle the ones that Find/Replace can fix, and > worry about the other errors next. > > Cheering you on for the work ahead, > > Judy There are quite a few other tools within ew that will do clean up jobs besides find and replace.. also the sequence you do clean up jobs can change the amount of clean up time too..also using fp to remove themes and shared borders is much much quicker. Remove formatting change table to text expression queries are just a few and there are third party tools that help too ... I have the most fun with expresssion queries... http://any-expression.com/expression-web/tutorials/expression-web-querys.htm It also pays to include seo aspects and semantic markup as you clean up a page Tina F ree Expression Web Toolbar - Expression Web and Web Design Resources http://frontpage-to-expression.com/expression-web-community-toolbar.html Just posted new links to the toolbar - Make YOUR suggestions Will work in FireFox IE and Safari

    12/23/2009 07:58:49
    1. Re: [ROOTSWEB-HELP] Bad code or bad program?
    2. Charles Barnum
    3. Tina, I just bookmarked that great link. Thank you. There is far more to ew than I imagined. Lets roll. CB Tina Clarke wrote: >> The closing tags will be the worst because it will likely be all manual >> work. :-( But you can tackle the ones that Find/Replace can fix, and >> worry about the other errors next. >> >> Cheering you on for the work ahead, >> >> Judy >> > > There are quite a few other tools within ew that will do clean up jobs > besides find and replace.. also the sequence you do clean up jobs can change > the amount of clean up time too..also using fp to remove themes and shared > borders is much much quicker. > > Remove formatting > change table to text > expression queries > > are just a few and there are third party tools that help too ... I have the > most fun with expresssion queries... > http://any-expression.com/expression-web/tutorials/expression-web-querys.htm > > It also pays to include seo aspects and semantic markup as you clean up a > page > > Tina > F ree Expression Web Toolbar - Expression Web and Web Design Resources > http://frontpage-to-expression.com/expression-web-community-toolbar.html > Just posted new links to the toolbar - Make YOUR suggestions > Will work in FireFox IE and Safari > > > > > ------------------------------- > To unsubscribe from the list, please send an email to ROOTSWEB-HELP-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.722 / Virus Database: 270.14.118/2584 - Release Date: 12/23/09 11:02:00 > >

    12/24/2009 01:26:29