Before/After WebsiteBaker...

[styzer]

I love WB for many reasons, and one of them is also this forum which has been a companion to my learning by trial and errors. SO here's my first ever "bakerized" site, only possible thanks to the WB community:

BEFORE: http://www.petitsgroupes.org/dieuenpremier.htm  (the index page don't work, but this will give you an idea)

AFTER: http://www.petitsgroupes.org

Now, unto the next project, learning this: http://www.jamroom.net

Regards and thanks again for all the helpful tips and support!

andre

[doc]

Hello andre,

nice adaption of an existing design layout with WB. Again a demonstration of the ease of bake concept of WebsiteBaker.

Both templates (before and after) have no valid markup (about 30 errors). Check it out with http://validator.w3.org. In addition I would recommend to get rid of font tags and realize that via an external CSS defintion file.

Regards and happy baking
Christian

[styzer]

Hi Doc, sorry it took so long to reply... been busy on other things.

I looked and don't understand what I have to do with that website. It tells me I have errors, but I truly don't know were to go from there, how to fix them!

Cheers,

andre

[doc]

Hello,

the errors are a result of the choosen doctype declaration (first line in the HTML source) and the HTML tags and properties you are using. Some doctype declarations do no longer support e.g. the target attribut in links. So either remove the target attribute or change the doctype in your template. Some modules create invalid markup as they use e.g. CSS definitions in the body which is no longer valied (must be in head). So the list is long, simply follow the instructions in the report.
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.petitsgroupes.org%2F

Regards Christian

[KenZo]

Hi Doc. I'd like to remove the target attributes from the menu but it seems I don't really know enough PHP to let it remove.

I tried erasing the 'target' in MySQL in the pages tab I thought but then I'm having an error.


EDIT: just found the good file.
Search for the line target="'.$page['target'].'"  in the class.frontend.php in the framework directory and delete that line.

[spida]

Great, worked instantly. Thanks for your rec!

@developers: I suggest to give an option "no target" in the backend's file settings which should be the default when a new page is created. Makes XHTML strict validate correctly. Thanks.

Regards,
spida

[DGEC]

Yes that should be selectable, but I think it mostly it depends on the menu system & wysiwyg editor you're using.

HTMLArea is still the default editor and it is not XHTML compliant and it's not maintained any more.

If you have installed FCK or Xina there's different options for links (although I can't recall if no target is one of them), and if you've used show_menu2 in your template, then the menu links can or will be XHTML compliant.  Be aware that old templates may still be using page_menu, not even the new show_menu, which I think is not compliant either.

[spida]

I am actually using FCKeditor. And I am also using show_menu2.

I might have expressed it incorrectly, but I was talking about the target-option of website baker's page creation. That's entirely a wb function as has nothing to do with editing.

Anyway, I will look around for a better place to put my sugestion, it's kind of off topic here anyway