• hi everyone,
    I’ve put my current page design for download (my first theme btw).
    It’s called “iRoybots SlatyStain” and can be found at the Demonstration Page.

    I highly recommend to install the “Revised-Image-Headlines” Plugin before activating the theme which adds a PNG image (based on a ttf-font of your choice) to a posts’ title.
    The whole Stylesheet is placed in Stylesheet.php in order to use php-compression. (server-side caching via gzip)
    Several alternate Sidebar Images are included in the Zip (headlines) as well as a blank header.jpg
    hmm, whatelse? A mimetype-switch decides to send XHTML 1.1 (application/xhtml+xml) or HTML 4.01 (sgml) depending on the browser the visitor uses…

    One Question:
    Would be nice if someone knows a way to avoid the code, that is necessary to put directly into posts to display the thumbnails (the thumbholder consists if several divs – take a look at demo-page for example code). I’ve thought of an additional tag <fancythumb><img src="bla.bla" /></fancythumb> something like that, that was more theme-switch-friendly…
    any ideas on this issue?
    if you find any errors or bugs, please report them in order to fix.

Viewing 15 replies - 1 through 15 (of 45 total)
  • I like the design. One thing though, your content negotiation isn’t working as it should, since my firefox is being served xhtml as text/html. Or did is misunderstand something here?

    Very impressive theme. I love that look.

    Thread Starter _erik_

    (@_erik_)

    eridan,
    the pages should be send to your browser as “application/xhtml+xml” (Response Header) that doesn’t influence the meta-tag “Content Type” that still says “text/html” because thats what the content is written in.
    If you watch the pages source you’ll see <?xml version=”1.0″ encoding=”utf-8″ ?> in the first line (not in IE because that would cause quirks-mode), what declares the doc to be xml.

    if you dont believe it, go to http://www.web-sniffer.net and type in my URL πŸ™‚ or if you are using the Web-Developer Extension (FF) go to Information->Show Response Header. There you should read “application/xhtml+xml” if not you’re right and somethings going wrong… :-/ [edit] you need the trailing slash because contact-sheet.de/blog is redirected to contact-sheet.de/blog/[/edit]

    eragle, thanks πŸ™‚ compliments are appreciated πŸ˜‰

    That’s a really interesting theme. Simple, but lots of visual interest in the details. I like the colour scheme as well. Good work!

    I’m not sure what attacts me to this theme. The colors are one thing but it may be that “aged” look given to the graphics. How did you do the header logo erik?

    Thread Starter _erik_

    (@_erik_)

    hoopla, thanks!

    eragle, funny you like especially the header because thats the part that IMHO needs correction (i think its too dark for the first thing to be recognized)
    all you need is a photo (a nice flower for example :-)) preferably photoshop, some additional brushes and a tutorial like this one (that is written in german) paperFX
    for that customizing-purpose is the blank_header.jpg

    That’s a beautiful theme!

    I myself have found though that sending as application/xhtml+xml often produces problems because WordPress does not check/correct for well-formedness, leading to broken pages when clueless authors and plugin writers generate broken code. You should make the mime-type switch optional for those who want to take the extra effort themselves, and not bother most of the WordPress users who just want to use your beautiful theme.

    (see also my article Markup in the Real World)

    What a beautifully presented Theme.

    Good work!

    i get the following errors when attempting to apply theme….

    Warning: file(/usr/home/makki/htdocs/blog/wp-content/themes/slaty/style.css): failed to open stream: Permission denied in /usr/home/makki/htdocs/blog/wp-includes/functions.php on line 1434

    Warning: implode(): Bad arguments. in /usr/home/makki/htdocs/blog/wp-includes/functions.php on line 1434

    Warning: main(): Failed opening ‘/usr/home/makki/htdocs/blog/wp-content/themes/slaty/index.php’ for inclusion (include_path=’.:’) in /usr/home/makki/htdocs/blog/wp-blog-header.php on line 221

    I dunno how to fix this

    Thread Starter _erik_

    (@_erik_)

    makki,
    ok here’s a short workaround (terrible word) for the mimetype-thing (in order not to do it my own – maybe laters)
    would you please edit header.php?
    remove the line saying: include ('mimetype.php');
    this is at the very beginning of that file and replace it with this instead:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">

    thanks yngwin, for now i just added some info on the demo page, but thanks for that hint will be considered for the next update of the zip file. but theres also a plugin out there called xvalid, that does the mentioned check of at least the comments i think. but true, wrong code -> no page, hmm… i’ll defenitely check comments and keep an eye on this…

    dss, thank you πŸ™‚ “beatifully presented” you talking about the demo-page? or theme itself? hmm…

    _erik_ thanks man ill do that let ya know

    i still get this errors…

    Warning: main(): Failed opening ‘/usr/home/makki/htdocs/blog/wp-content/themes/slaty/index.php’ for inclusion (include_path=’.:’) in /usr/home/makki/htdocs/blog/wp-blog-header.php on line 221

    Thread Starter _erik_

    (@_erik_)

    I’m not sure where the error comes from, but a site that doesn’t validate as xhtml 1.0 transitional won’t validate (or even show up) as xhtml 1.1 (as xml)
    so better replace the doctype with the one you have right now (xhtml 1.0 transitional – saying: !DOCTYPE and html both two tags)
    just pick the ones you got in your current theme, ok?
    hope that helps πŸ™‚

    ok will do

    made no difference at all sorry i did it twice no effect

Viewing 15 replies - 1 through 15 (of 45 total)
  • The topic ‘new Theme: iRoybots SlatyStain’ is closed to new replies.