UPDATE:

I now see that the XML files for the two themes I mentioned above,
"Tea House" and "Solar System", now have no mention of CSS, although
I'm sure it was there yesterday — perhaps I'm losing the plot!

So the question now is, how do I submit XML files using the same
attribute (header.height) as these two popular themes without the
submission being rejected with the error message "Unknown Attribute
name: header.height"?



On Oct 31, 8:35 am, BlueQuoll <bluequ...@gmail.com> wrote:
> After posting this in the iGoogle section of the Web Search Help Forum
> where there's a lot more useful activity, and getting no answer there,
> I'm posting back here in the forlorn hope that there may be someone
> drop by here who can answer.
>
> Now that Google has seen fit to obscure the header images in iGoogle
> themes with a larger search box and buttons, I've had to revamp the
> header images in some of my themes.
>
> In my XML files I've tried using the old attribute "header.height" to
> increase the height of the header so it can accommodate the higher
> image I need to use. While this displays perfectly in test mode (?
> skin=URL), I can't submit the updated XML to Google because I get an
> "unknown attribute" error.
>
> Can someone please advise what is the new accepted method for
> producing headers such as "Tea House" and "Solar System" which differ
> in height from the normal 175px. The XML code for such themes
> previously used the "header.height" attribute, but now appear to be
> using CSS.  If this is the way themes development is going, when will
> the Themes API Developer's Guide be updated?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Themes API" group.
To post to this group, send email to google-themes-api@googlegroups.com
To unsubscribe from this group, send email to 
google-themes-api+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-themes-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to