I just installed Zen Grid Framework 1.1.11 on two sites that are built using the Default Template.

As I read in the documentation the fontHeadings validation error was supposed to be fixed in 1.1.11 - however it still seems to exist in this version. Here are links to two sites using 1.1.11 and their validation output:

Site one - validation output here
Site two - validation output here

I'm not sure if I am doing something wrong or if this has been fixed in 1.1.11?

Thanks,
Sascha

Looks like a slightly different issue but one that needs to be fixed all the same. Ill be releasing a small update with the next template so Ill get that covered then.

Cheers Anthony

Hi Anthony,

I just saw that you released Lacuna (which looks awesome btw!) and version 1.1.12 of the framework.

I installed 1.1.12 at both sites, but unfortunately the validation error is still the same, as you can see here and here.

Sascha

Hi Sascha,

If nobody has a look before Anthony wakes up I'll send him a note about 11.30pm GMT to take a look

He's been a bit delayed with the new template

Cheers
Paul

Thanks, Paul!

Ah sorry I missed that Sascha. Will take a look today.

Anthony

Hi there,

I just updated to version 1.1.15 of the framework and also tried 1.1.14 yesterday.

The fontHeadings validation error still seems to exist in 1.1.15, and now there is also an error about fullWrap. The site is built using the default template btw, and here's the validation output.

Any advice on this issue?

Thanks,
Sascha

Hi Sascha,

Try placing an extra </div> at the end of a template override:

zendeafult/layout/bottom.php

You need to ensure the override is activated in the template settings. If you don't already have that file in place, you can copy it from:

zengridframework/assets/layout/

Yes - thank you, Seth!

First the bottom.php override did not seem to work for me - but I added an extra </div> to the footer.php override, and now everything is perfectly valid.

Thanks again,
Sascha

Glad to hear it Sascha, glad I could point you in the right dierction.

Thanks for confirming the fix.

Thanks guys - still need to hunt down the error obviously - glad you got a solution though Sascha.

Anthony