ivovic

http://wordpress.org/support/topic/157064?replies=6

if I had a week to think about it, I would have thought to search 🙂

if you don’t see the relationship between CSS sizing and positioning, and a technology which changes the shape and size of images, then I can’t help you.

until the ability to manipulate element backgrounds is *widely* available, adding a technology like this to browsers will be severely limited in usefulness.

thats what I said 2 days ago, that’s what I say now.

explain to me how I can scale a background image via CSS now, and I’ll agree that the w3c has nothing to do with it.

…and this whole firefox-specific thread of discussion is just pointless.

if you expect me to chill out and believe that you’re not intentionally trying to piss me off, then you’ll have to try and be just a little bit logical about this. Why bust your ass implementing a sizing technology, if it’s only useful half the time?

well, that’s because it’s outside the loop.

in your page template, do something like….

<?php
  global $current_language;
  $current_language = get_post_meta($post->ID, 'language', true);
  echo $current_language;
?>

then in the footer:

<?php
  global $current_language;
  echo $current_langauge;
?>

oh this is going to be fun to sort out.

if you force the include param to be an array as it seems to demand, you get further errors past that point where it screams “string expected”

I’m also only having problems with this on a page template – otherwise it works.

this is definitely one for the devs.

edit: ** note, upon further testing, this bears no relevance

…

I just did the same thing 🙂 … I put the same line into my blog which has been upgraded from previous versions and it works flawlessly…

but in my fresh 2.5.1 blog, it throws out the same error you got… we might be looking at a bug, I suppose.

try deleting your htaccess file, and allowing wordpress to create it… something is rewriting your ugly permalinks into pretty ones for the previous page link only.

this is exactly the point I’m making, which you’re arguing against for some reason.

This document on CSS3 backgrounds has been in development since 2002… that’s 6 years of my life waiting for a bloody web standard… and it aint even done yet.

Where’s the ubiquitous browser support for that, then? Perhaps if it comes in my lifetime, I’ll agree that adding a new image rendering technology is worthwhile.

Seriously dude, what’s your point? You’re talking about CSS3 as if it actually exists. It’s been 6 years or more and barely anything has come of it…. but all of a sudden, that’s as good as done for you?

I get the feeling you’re trying to counter my point just for the sake of argument. It’s annoying and childish, but mainly because you’re wrong.

I said “someone needs to light a fire under the w3c’s ass” and I mean it… its been far too long, and with that kind of standards approval process in place its no wonder browser vendors go out on their own.

Moreover, this discussion isn’t even about firefox, its about mobile browsers more than anything, where screen dimensions and orientation tend to change more dramatically.