[theme-reviewers] Something we need to check for 3.4 appearance -> background

Philip M. Hofer (Frumph) philip at frumph.net
Mon Jun 11 23:06:15 UTC 2012

Maybe you're not seeing the 'added problems' that it will be given.  I see 
them because I'm out there, in the field working with clients 7/24 and know 
what they are capable of.   As are you in some respects.

If I add the functionality of the arguments into one of my themes and it's 
still your method.   This is what will happen.

1) End user upgrades their theme (cause well hey it's a good idea)
2) End user promptly sends me an email saying his Child Theme no longer 
works.  Ya know, that one I wrote for him that cost him hundreds of dollars 
of time involved.
3) A bit of time each one telling them how to "fix" it by going to the 
appearance -> backgrounds and put in a temporary background until I can get 
the correct url for the one his child theme has.
4) Moaning about how WordPress messed up and me spending 1/2 hour explaining 
it wasn't a mess up but it's implemented cause someone wanted to have a one 
click turn off of the background image in the back end.

-----Original Message----- 
From: Otto
Sent: Monday, June 11, 2012 3:57 PM
To: theme-reviewers at lists.wordpress.org
Subject: Re: [theme-reviewers] Something we need to check for 3.4 
appearance -> background

On Mon, Jun 11, 2012 at 5:54 PM, Philip M. Hofer (Frumph)
<philip at frumph.net> wrote:
> As it should be.   If the appearance -> background image isn't set, there
> should not be a custom-background code or body class.

RIght, and that's fine, but you're then going to have to make sure
theme authors don't put background images into their stylesheets

> You want to add steps the end user will not be familiar with *no* 
> fallback.

I fail to see how "adding steps" is the case when it's one button to click.

> Just for a single quick-option to remove all backgrounds.   While the end
> user has been for years now been familiar with editing the style.css
> making/modifying a child theme or using a plugin.

For years, people have been editing their websites using Dreamweaver
and making hand-coded HTML. So why would one need a Content Management
System? End users can code too, you know.

Let's not be silly.

> Instead of keeping the status quo the implementation of it doesn't warrant
> the difficulty in providing support for it.   It's basically like telling
> people to user newheader.php instead of header.php from now on.

No, it's like telling people "hey, if you want no background image,
click the Remove Background Image button, unless your theme was
written in a non-compatible and stupid way, in which case you need to
learn CSS and then go manually change things".

theme-reviewers mailing list
theme-reviewers at lists.wordpress.org

More information about the theme-reviewers mailing list