Forum Replies Created
just for information, I’ve had the bug fixed in he w3 validator and the blog template also validates %100 now.
perfect this makes sense, so it actually takes the slide images from the posts, this was the clarification I was looking for.
just checked with a logo – much closer to validation, however one failure with the logo.
Validation Output: 1 Error
Error Line 147, Column 125: Bad value category for attribute rel on element a: The string category is not a registered keyword or absolute URL.
…posts in Uncategorized” rel=”category”>Uncategorized</div> <div class=”tag…
Syntax of link type valid for and <area>:
A whitespace-separated list of link types, with no duplicate keywords in the list. Each link type must be listed as allowed on and <area> in the HTML specification, or must be listed as allowed on and <area> on the Microformats wiki, or must be an absolute URL. You can register link types on the Microformats wiki yourself.
Changing the page to the “full page” template, gets validation %100 – nice job, but the side bar has the one failure error listed above.
I’ve not had change to test the portfolio pages yet.
no complaint, apologies if it came across like that.
I’ll try it with the logo, see what difference it makes.
thank you for exceptionally quick feedback
thank you very much
what is the ubuntu font used for ?
great information that’s very very useful to know.
this is not for an external client, however if any external work is done, on this theme or any other themonic themes I will %100 purchase a developer license, I’m keen to stay within any licenses, hence checking before doing any changes.
this is for an internal project that will be externally facing, and hiding things like theme names to internal project names for security and internal modification tracking is something that I am trying to put in place for all projects.
upgrading should not be a problem as I use version control and keep a copy of the modified version, unmodified and potential “new” versions so tracking changes and merging legacy customiztion into current code based should be tested before releasing. Appreciate the thought though.
superb fix, thank you