post_parent; // test to see if this it a parent
$postID = $post->ID; // get this post’s ID
$ancestors = get_post_ancestors($post);
$top = end($ancestors);

if($isparent == ‘0’) { // if there is no parent, grab this page’s name
$getname = get_post($postID);
} else {
$getname = get_post($top);
}
$toplevel = ’ id=”’ . $getname->post_name . ‘” class=”page”’;
} else if(is_category()) { // if we’re on a category listing
$cat = get_query_var(‘cat’);
$parents = get_category_parents($cat,FALSE,’^’,TRUE);
$get_parent = explode(‘^’,$parents);
$toplevel = ’ id=”’ . $get_parent[0] . ‘” class=”category”‘;
} else if(is_single()) { // if this is a single post page
$toplevel = ‘ id=”single”‘;
}
echo $toplevel;
} ?>

I’ve gotten your code to work just fine when on a page.

However, I’m attempting to stick this in my index.php file… and obviously its not working because there is an issue with the url of the form action.

what do you suggest i use for that form action url?

On click it says “thanks” etc etc, but its really not working because it wont send. (but it does send when in a page)

I have made a tutorial about how to code cross-browser sliding door input button. This means that we could use this way to display our button clear for now.

Here it is: http://www.manakor.org/xhtml/cross-browser-sliding-door-input-button/

But, of course, I’d like to say thanks to you, because, to be true, I used to you method on my site before.

$(“.addressDiv span”).live(“mouseover”, function(){
//clickable function here……
————————————
});

I have used the above live() event to trigger the function on mouseover in the dynamically added elements. But the problem i got is that once the live event is called it takes the class of the element and stores. And when the class of that particular element is changed dynamically the live() event does not detect the new class added dynamically, instead it takes the former class. Live() event does not update the class. How can I solve this problem?

could you please show me how can i add a text field that will validate an URL?

thanks

However, we must realize that everyone goes through a different timeline of learning. Some people are just wrapping their head around CSS and just finding out about how IE6’s market share and the faulty ways it interprets the elements. So while I agree, we need to keep in mind that at some point when "we" began moaning, someone somewhere was probably rolling their eyes saying, "Here we go again".

@Steve Rydz-
I think it was perfectly ok to complain about it for a while, but now that newer versions have been released, they need to stop wasting their breath.

@Nate-
Absolutely IE6 compliance has hampered the web, but I think we are beyond that. There is virtually no reason that you should spend a significant amount of time trying to make IE6 look exactly like more standards compliant browsers.

Instead of using that PNG, just use a GIF. No user is ever going to pull up the site in another browser and compare it, so they won’t even know the difference.

While absolutely I do still spent time supporting IE6, I am just making sure that it doesn’t look broken. I can deal with doubled margins here or squared corners there. I have learned to embrace that it’s inefficient to spend time trying to make sure that pixels match up in all browsers, and I laugh at job descriptions that have “pixel perfect slicing” in them. Clearly they don’t understand the current state of the web.

I’ll admit that I’ve sometimes made it a point of pride that I seldom have to use IE-specific hacks, or that I could make something look as good in IE6 as in other browsers. But those days have gotten old.

IE6 compliance has forced us to keep too many features from web pages, and—Microsoft’s fault or not—people are right to begin agitating for something like a final push to drop the browser.

Most solutions for IE6’s fundamental faults are partial. As you well know, Dean Edwards script has problems. A script I use for PNG replacement, DD belatedPNG caused conflicts with SWFAddress in the last site I worked on.

And for most people, unless they’re willing to go the route of the suggested Universal Stylesheet (a decision most developers don’t get to make for the sites they work on), they’re stuck spending a disproportionate amount of their time fiddling to make stuff work on the problem child of browsers, or not implementing the quickest, most efficient CSS or Javascript because IE6 has to be provided for.

Surely you can bear a bit of complaining.

In my experience as long as you adhere to web standards IE6 isn’t too bad. OK, the sidebar might not line up as you wanted or that transparent PNG has a funny outline on it but at least the content is accessible.

As you say, if the amount of effort required to make IE6 play ball is not equal to the number of people actually visiting your site in that browser then Andy Clarke’s Universal IE6 Stylesheet is perfect for the job. Failing that the Dean Edwards script is also pretty useful.

Sorry for the overlong comment mate, it’s just nice to hear a voice of reason ;-)

But, I agree with you - I feel like people either whine about IE6 because a) they’re a newb, b) not talented as you hint, or c) looking for blog readers.

$('input[title]').each(function() {
    var qinp = $(this), title = qinp.attr('title');
    if(qinp.val() === '') qinp.val(title);

    qinp.focus(function() {
        if(qinp.val() === title)
            qinp.val('').addClass('focused');
    });

    qinp.blur(function() {
        if(qinp.val() === '')
            qinp.val(title).removeClass('focused');
    });
});

You will need to concatenate the item.title and item.description strings into one string and add that as the title attribute.

Sorry having trouble adding code here with: pre>YOUR CODE HERE

Meant to say all that is supported is the title attribure in lightbox, my implemented code is:

.wrap(‘’)

Ok I have the title pulled in now, but as far as I can gather there is no tag in lightbox that supports the description all that’s available is:

.wrap('')

Hi Trevor, Thanks for your help on this, ok so I have tried to add item.title and item.description to the each statement but all it gives me is an error… Help LOL

I thought these might work, but I havetried them everywhere and I can’t get it going…

$(“#title”).html(data.title);
$(“#description”).html(data.description);

Sorry to be a pain but could you show me how in the code below… I’m still a newbe on this and it took me long enough to figure this out.

$(document).ready(function() {
$.getJSON("http://api.flickr.com/services/feeds/photos_public.gne?id=39724364@N04&lang=en-us&format=json&jsoncallback=?", function(data){
$.each(data.items, function(i,item){
if(i<=11){
$("").attr("src", item.media.m).appendTo("#FlickrImages ul")
.wrap('<a>')
.wrap("")
}
});
$('a[@rel*=lightbox]').lightBox();
});
});

So if you just include the title and description from the JSON call as the title attribute, you should be good.

This is the code I have implemented so far… Hope you can help

$(document).ready(function() {
$.getJSON("http://api.flickr.com/services/feeds/photos_public.gne?id=39724364@N04&lang=en-us&format=json&jsoncallback=?", function(data){
$.each(data.items, function(i,item){
if(i<=11){
$("").attr("src", item.media.m).appendTo("#FlickrImages ul")
.wrap('<a>')
.wrap("")
}
});
$('a[@rel*=lightbox]').lightBox();
});
});

I know you said to Jules that we’ll need to change our JavaScript validation rules to cater for this stuff. That’s not a problem, but really we need to modify our server side validation as well, which makes it a little more complicated.

I’m thinking about clever ways to do this - perhaps assign the descriptions to variables, then use them in both processing the _POST values and in generating the form…

Anyway, thanks!

<input type=”text” value=”value that will erase on focus />

$(‘input’).get(0).defaultValue

I am also on 1and1, using Mimbo Pro 1.5 (Wordpress 2.7).

I am thinking that 1and 1 might be blocking access to some of my files- that is why I am posting here. I have tried everything else. Anyone have an idea?
THanks.

That way, I can strip off the values of any element with class ‘inlinetip’ at submission (and immediately re-add it if it’s an AJAX submit).