datdesignguy

ghp, see my earlier post… is_tag() is not intended to be used in the way you are looking for, that’s why you’re only getting the “else” response.

you’ll need to use something like this:

<?php
$post_tags = get_the_tags();
$tag_array = array();
foreach($post_tags as $tag) {
  $tag_array[] = $tag->name;
}
if(in_array('dog',$tag_array) !== FALSE) {
//show dog tag related code
} else if(in_array('cat',$tag_array) !== FALSE) {
//show cat tag related code
} else if(in_array('pig',$tag_array) !== FALSE) {
//show pig tag related code
} else {
//none of your special tags were found
}
?>

I haven’t had a chance to test this code as I’ve written it, but that should get you rolling in the right direction. I’ve used this before to show tag-specific opt-in forms to readers on a clients blog…
I hope this helps!

-greg

Hi ghp,

I think the reason is_tag does not work for you is because that function is intended to detect whether or not the page being viewed is an archive page for a specific tag/all-tags…

In order to achieve what you’re wanting to do, you’ll need to use the get_the_tags() function and then evaluate whether the desired term is contained in the list of returned tags.

You might want to write a custom function in your theme’s functions.php file to handle this. Here is the func ref for get_the_tags():
http://codex.wordpress.org/Function_Reference/get_the_tags

I don’t see anything wrong with your code at first glance. Is this being used with a custom post type in a post-type-specific template?

If so, you can try visiting the permalinks page in your admin, clicking save/update (you don’t need to make any changes) this forces wordpress to look for newly created templates for custom post types and rebuild rewrite and template rules. It seems to me like wordpress might not be using the template you want it to.

That’s just a guess, though. Good luck! I’ll be watching this thread to see how this turns out.

– Greg

Hi Vinoth,

I had a quick look at your site. Perhaps you have some plugins running that have something to do with user logins? You might try following the instructions here to temporarily disable all plugins and login:
http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F

If this works, and you are able to login, you can then delete the empty plugins folder you created and rename “plugins.hold” folder. Then you should proceed to your plugins page, open a different browser (i.e. if logged in in firefox, open your login page in chrome while still logged in on Firefox.)

Using browser 1, deactivate all currently active plugins,
Then attempt to login in browser 2. If browser 2 logs in successfully, log back out on browser 2, then activate a plugin and repeat the process until you find the offending plugin or successfully re-activate all plugins.

I hope this makes sense and helps you solve your problem.

– Greg

Hi Colin, have you edited any of WordPress’ core files? If not then your manual upgrade should go quite smoothly.

After you back up your database AND files, the manual upgrade is pretty simple and should not affect any of your wordpress settings unless you have made edits to wordpress core files.

The manual upgrade basically boils down to these steps:

1. backup db AND files
2. De-activate all plugins (I have a lot of plugins on some sites, not all of which are active all the time, so common sense, write down the ones that are active)
3. Delete the wp-admin and wp-include folders on your server. DO NOT DELETE YOUR WP-CONTENT FOLDER.
4. Delete all files wp-*.php files in the top level of your wordpress folder EXCEPT wp-config.php.
5. Upload all wordpress 3.1.2 files to your server except wp-config-sample.php
6. After upload is completed visit the following url:
http://YOURWPSITE.COM/wp-admin/upgrade.php
and follow the steps there.

And you should be all good to go. I hope! 🙂

– Greg

Hi Colin,

What version were you upgrading from?

The is_network_admin() function was added in WP v3.1.0, so if you look on your server in the wp-includes/load.php file, you should see around line #614 the definition of this function. If it’s not there, you can probably fix your WP installation by following the instructions here for a manual upgrade: http://codex.wordpress.org/Upgrading_WordPress#Manual_Update

It seems possible that for some reason, during your upgrade the load.php file is not getting updated with the new file, so you may want to take a backup and then attempt a manual upgrade.

Hope this helps!

– Greg

While I haven’t found a solution to this problem yet, I do know that wordpress 2.9.1 seems to have broken post image uploads. Not sure what the deal is with that. Until 2.9.2 though, if you’re an avid image uploader and can’t wait, I’d recommend you roll back your wordpress install to wordpress version 2.9. You can find tons of tutorials on how to do this with a quick google of “downgrade wordpress”