Introducing the Add From Server Plugin

Built by Dion Hulse, the Add From Server is a simple plugin that adds a link in your Media menu for taking any file residing in your uploads folder and adding it to your media manager making it accessible to WordPress. This is a great solution for anyone needing to upload large media files.

Go Get Ya Some!

• Extend.WordPress.Com Plugin Page For “Add From Server”
• Add From Server Homepage
• Author Dion Hulse’s Website

1. $more is Turned Off Almost Anywhere You Might Wish to Use it.

By default $more is only available on the blog page, if you have set your front page to use a page instead of post your blogs as is the default behavior then WordPress is going to ignore your <!– more –> tag.

To turn $more on you first global it and set it to 0 like so:
<?php global $more; $more = 0; ?>
This must be done in The Loop which brings me to my next point.

2. $more Must be defined and Used in The Loop

When you do want to use a teaser and modify how $more works then you must do it within The Loop, if you try to define $more anywhere else and it just won’t work.

3. The More-Link Can Have Any Text

The standard “Read More” link that a teaser article is given can be changed to whatever you want on the theme level and even from the article. To change the text from the theme file use the string parameter of the_content() like so:

<?php the_content('Click Here to Launch Missiles'); ?>

To change the more-link text while authoring the article replace
<!– more –> with <!– whatever you want to say –>

Know your MIME types

Depending on the type of media you want to retrieve you need to know its MIME type. The easiest way to get the MIME type of the file is to go the media manager and click on “edit” for a file of the type in question. After you click “edit” you will see a screen like this:

Find the “File type:” and copy the text to it’s right, in the example above it is “audio/mpeg”, now that we have that string we can move on to the next step.

Generating the Media List

First we need to make some markup for the list to reside in, then we will populate an array by calling the get_children() function making sure to specify the post_type as “attachment” and the post_mime_type as “audio/mpeg” just like i saw it in the media manager under “file type:”

Finally in our loop we will call the wp_get_attachment_link() function with the current attachments ID to print a link to the file in question. It’s actually pretty simply once you see it all in action as below:

<ul>
<?php
$audios =& get_children( 'post_type=attachment&post_mime_type=audio/mpeg' );
foreach ( (array) $audios as $attachment_id => $attachment ) { ?>
<li><?php echo wp_get_attachment_link( $attachment_id ); ?></li>
<?php } ?>
</ul>

IE6 & Grids

The case FOR support: Supporting IE6 grids tend to give beginners a lot of problems but in reality supporting IE6 to a usable level can be passive if you remember a couple simple rules. Getting IE grids to look identical to working browser grids can be tricky but shouldn’t take to much time. One tip here is to make sure your grids work before you have them full of content and design elements. For help with IE6 rendering problems check out this tutorial: 9 Most Common IE Bugs and How to Fix Them.

The case AGAINST support: I can’t really make one, it only takes a couple lines of CSS to make your grids usable and ignoring that is just lazy, plus if you’re using a grid framework like 960 Grid or Blueprint then your grids probably already work. I will say this however, if your IE6 user demographic isn’t high then worrying about aesthetic level problems probably isn’t the best place to spend your valuable time.

Conclusion: Supporting IE6 to the point it can render your site’s structure is to easy not to still do at this point. Don’t waste valuable time on making small aesthetic issues work when you could make things better for compliant browsers.

Conditional IE Style Sheets & Hacks

Conditional style sheet includes Vs Css hacks is an old issue, should I use IE’s conditional statments to include seperate CSS files depending on it’s version or should I use hacks? This isn’t really a case for or against as if you’re doing this then you have decided that you have to support IE6 in some manner and now you need to decide how that support will be implemented. For a while now I had sided with Hacks as they were usually two or three lines in my entire CSS file and they were right there along with everything else about the style. I don’t like having to break up my CSS based on browser detection which shouldn’t even be happening anyway. I believe now though the best solution is outlined by Paul Irish over at his blog PaulIrish.com. What Mr Irish has known for year’s apparently is that it’s a lot easier to use the same IE conditional statements to include a class in your body tag and then simply write CSS selectors for the IE specific body class.

Conclusion: Neither hacks or conditional includes turn out to be the right choice, instead go with the solution outlined here by Paul Irish: conditional-stylesheets-vs-css-hacks-answer-neither.

IE6 PNG-Fix

The case For use: Some designs just can’t be done using opaque JPGs, if you have to support IE6 to this visual level you probably need therapy and if you don’t now, you will later. At any rate a PNG-fix is basically your only option for high color alpha transparency, there are so many options out there for PNG-fixes there’s no point going into it all, use the Google.

The case AGAINST use: Consider what you’re doing with transparency, is there any reason not to achieve the same effect using progressive enhancement in a compliant browser instead of performing black-magic in an antique? I have yet to see a PNG-fix that didn’t mess with complex CSS or add load times and over-head.

Conclusion: I think it’s much better to assume your IE6 users don’t have the extra horsepower for big images and complex solutions. Assuming your compliant users can handle well though out progressive enhancement is probably better and in the end you will be offering a better experience to more people. 8-bit PNGs should also be considered as many times they can accomplish the same effect as their high color counterparts as pointed out by Alex Walker over at Site-Point.

Upgrade Dialogues & Vague Threats

The case FOR harassment: Everyone sane that works in web design hates IE6, it’s punished us all to much and it’s probably the pit-of-despair in your test scenarios. Getting people to stop using IE6 should be encouraged, most of the time this means downloading a non Microsoft browser like Firefox or Opera. By using a pop-up dialogue with download links, instructions and rude comments we can help people make the right decision and help the web move forward.

The case AGAINST harassment: Most people using IE6 have on thing in common, they have no choice. So while you think your doing the right thing by educating people on how old, insecure and broken their browser in reality you are just reminding them of the thing they are by now acutely aware of.

Conclusion: Don’t harass people about using IE6 unless it’s necessary, your clients probably don’t wish to be an active participant in the browser wars unless it’s mandatory the user have a modern browser to get on the ride, and example of this would be something like a bank or online-games site.

Conclusions

Grids:

Take the time to keep them from exploding, don’t waste time on perfection in IE6.

IE conditionals and separate style sheets:

Use conditionals instead of hacks but instead of including separate style sheets use the conditions to modify the class of your body tag.

PNG-Fixes

Think with progressive enhancement in mind rather then making IE6 do things it wasn’t meant to.

Upgrade dialogues

Don’t rub salt in the wounds unless it’s necessary, at this point your users probably can’t upgrade.