Ultimate Tag Warrior 2.9

New uber-version of UTW!

Beware:
– There are new options which might cause wonky behaviour (mostly just automatically included tags appearing) – go to the Options > Tags page and hit save to make ’em vanish.

New Features:
– If there are database permission issues that prevent the auto-updater from running, you won’t see error messages all over the place (but if you do a force-reinstall they will display)
– Related posts are sorted by most tags in common, then most recent first (previously it was just most tags in common order)
– Tag urls are now url-encoded (duh.) – this allows using umlats and other such things (at least in the way I tried (; including ü in your tags works, using magical characters directly is a bit bung still)
– Lists of posts can now include the date of the post (uses the %postdate% formatting placeholder, and the default date format)
– UTW_Show functions have changed a little – the first parameter still takes the name of a predefined format; but if you pass in custom formatting information, it will be added to the predefined format.
– The Options > Tags page has a whole bunch of embedded help. Yay help.
– The automatically included links can now be placed either before or after the content. There’s also the option to add text before and after the tags (handy for Tag: labels, wrapping tags in spans or divs and wrapping html lists in <ul> tags)
– I’ve fixed an odd bug with feeds (it worked for me, but didn’t for a couple of people.. it’s just one of those bugs, I guess)
– [Wordpress 2 only] On the write post screen, the tag entry and tag suggestion boxes have been shuffled into the right-hand column and put into magical boxes for shuffling and hiding and whatnot.
– There’s a new template function, UTW_ShowRSSFeedIcon(). It displays an RSS icon on tag pages for the current tag set (if you’re viewing /tags/tag1 it’s a link to the tag1 feed. On /tags/tag1+tag2 it’s a link to the feed with posts tagged both tag1 and tag2).
– The UTW_AddTagToCurrentPost() has an extra parameter – it allows specifying the minimum user level that you need in order to add tags. It defaults to 3.

Things I haven’t forgotten:
– The ability to exclude tags from displaying in tag clouds and on posts
– The gadabe issue with … in tag links
– Cobbling together a non-includey version
– Displaying tag clouds for a subset of tags (For facetish purposes)

If there are things I have forgotten, let me know (: I get forgetful sometimes..

Support Forum | Ultimate Tag Warrior 2.9, for WordPress 2.0 | Ultimate Tag Warrior 2.9, for WordPress 1.5

Advertisements

21 thoughts on “Ultimate Tag Warrior 2.9

  1. Hey Christine,

    Found a bug, I think. I have the options set to show an invisible comma-separated tag list, after my content.

    However, it isn’t invisible. It shows up.

    The invisible set worked before I updated to 2.9.

  2. Hello,
    I upgraded to WordPress 2 (Howdy ?) and UTW 2.8.9 and then 2.9. It works except that I can see the tag entry on the write post screen.
    “Show existing tags on post editing page” is on “TagList” I put it off and back, but it doesn’t change anything.
    Thanks
    Bruno

  3. Christine, I need your help! arg!! I have spent the morning trying to figure this out, but no luck.
    I am using front_page_cats to prevent certain categories from showing up on the frontpage. It is a very short script available at the above website.
    However, when I click on the tag cloud and get sent to /wordpress/tag/whatever, if the category is a non-front page category it is not getting displayed. I am assuming that front_page_cats is assuming it is the home page.

    I am not veyr php inclinced, but from what I can gather front_page_cats uses the following to determine whether it is home or not:
    if (! $wp_query->is_home)

    Any ideas?

  4. Going to Options > Tags and hitting ‘Save’ might deal with the double tags thing (The “don’t show any tags” option value changed from ‘no’ to ‘No’; and saving the options page sorts it out. I’ve also changed the code to look for both variations)

    The invisible tags being visible thing, I know about and have written a fix for, so next version it’ll be okey-doke (:

    As for the 404s; on line-ish 28 of ultimate-tag-warrior-actions.php, do the rewrite rules say something like foo=$matches[1] or foo=$1 ?

  5. I guess you could try manually adding the rewrite rules by putting this in your .htaccess file before the wordpress block:

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule ^tag/?(.*)/feed/(feed|rdf|rss|rss2|atom)/?$ /index.php?tag=$matches[1]&feed=$matches[2] [QSA,L]
    RewriteRule ^tag/?(.*)/page/?(.*)/$ /index.php?tag=$matches[1]&paged=$matches[2] [QSA,L]
    RewriteRule ^tag/?(.*)/$ /index.php?tag=$matches[1] [QSA,L]
    RewriteRule ^tag/?(.*)/page/?(.*)$ /index.php?tag=$matches[1]&paged=$matches[2] [QSA,L]
    RewriteRule ^tag/?(.*)$ /index.php?tag=$matches[1] [QSA,L]
    </IfModule>

  6. Thanks : removing the apostrophe in the tag name solved my issue.
    That is support ! I wouldn’t excpect such quick answer. Thanks again.
    Bruno

  7. Arrgh! Gah! Hrm.

    Does the URL rewriting work for anything else in wordpress?

    *smacks forehead*

    Try

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule ^tag/?(.*)/feed/(feed|rdf|rss|rss2|atom)/?$ /index.php?tag=$1&feed=$2 [QSA,L]
    RewriteRule ^tag/?(.*)/page/?(.*)/$ /index.php?tag=$1&paged=$2 [QSA,L]
    RewriteRule ^tag/?(.*)/$ /index.php?tag=$1 [QSA,L]
    RewriteRule ^tag/?(.*)/page/?(.*)$ /index.php?tag=$1&paged=$2 [QSA,L]
    RewriteRule ^tag/?(.*)$ /index.php?tag=$1 [QSA,L]
    </IfModule>

  8. Still getting 404s. Here’s my .htaccess:

    RewriteEngine On
    RewriteBase /

    RewriteRule ^tag/?(.*)/feed/(feed|rdf|rss|rss2|atom)/?$ /index.php?tag=$1&feed=$2 [QSA,L]
    RewriteRule ^tag/?(.*)/page/?(.*)/$ /index.php?tag=$1&paged=$2 [QSA,L]
    RewriteRule ^tag/?(.*)/$ /index.php?tag=$1 [QSA,L]
    RewriteRule ^tag/?(.*)/page/?(.*)$ /index.php?tag=$1&paged=$2 [QSA,L]
    RewriteRule ^tag/?(.*)$ /index.php?tag=$1 [QSA,L]

    RewriteCond %{QUERY_STRING} ^feed=(feed|rdf|rss|rss2|atom)$
    RewriteRule ^(.*)$ http://feeds.feedburner.com/Acid? [R,L]

    RewriteRule ^(feed|rdf|rss|rss2|atom)/?(feed|rdf|rss|rss2|atom)?$ http://feeds.feedburner.com/Acid? [R,L]
    RewriteRule ^feedburner_299313/?$ /wp-rss2.php [QSA,L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php

  9. Gah! I have no idea.

    When I get home from work, I’ll figure out what I did to figure out how to set up the pretty urls (I ended up poking debug information in interesting places, which I can’t remember off hand).

    At least that way we could figure out if there’s something bizarro happening in the pretty-url-matching part of wordpress.

  10. Yep, the rewite for FeedBurner is from the FeedBurner plugin, and works hunky-dory. All generated by “Update Permalinks” then your stuff pasted in above. So, now my .htaccess is:

    # UTW
    <IfModule mod_rewrite.c>
    RewriteRule ^tag/?(.*)/feed/(feed|rdf|rss|rss2|atom)/?$ /index.php?tag=$1&feed=$2 [QSA,L]
    RewriteRule ^tag/?(.*)/page/?(.*)/$ /index.php?tag=$1&paged=$2 [QSA,L]
    RewriteRule ^tag/?(.*)/$ /index.php?tag=$1 [QSA,L]
    RewriteRule ^tag/?(.*)/page/?(.*)$ /index.php?tag=$1&paged=$2 [QSA,L]
    RewriteRule ^tag/?(.*)$ /index.php?tag=$1 [QSA,L]
    </IfModule>

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{QUERY_STRING} ^feed=(feed|rdf|rss|rss2|atom)$
    RewriteRule ^(.*)$ http://feeds.feedburner.com/Acid? [R,L]

    RewriteRule ^(feed|rdf|rss|rss2|atom)/?(feed|rdf|rss|rss2|atom)?$ http://feeds.feedburner.com/Acid? [R,L]
    RewriteRule ^feedburner_299313/?$ /wp-rss2.php [QSA,L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php
    </IfModule>

    # END WordPress

  11. Christine,

    Welcome to the hell of plugin-devs : wp_rewrite looks like a nice headache for ELA too.

    One thing tho : it seems some http headers are not passed properly by wp_rewrite. Not sure if it helps a lot for UTW, but it seems to be solving some issues for the XMLHttpRequest calls in ELA, though to be honest I have no clue as why !

    ANyway, if someone gets to nail this down, I am a buyer for the explanation since I have been fighting with this shit for days…

Comments are closed.