No worries on the getting confused. It's difficult to convey some things via text. :)
I wanted to respond to your points - but, didn't want to make the situation more confusing. So, the part in the blockquote is the important bit - and I could/should start a new thread using just that.
http://joshbruce.com/tag_url/
Changed Permalink structure as mentioned. And, unfortunately it doesn't work the way it should/would (considering the other bits work). the_permalink(), as suspected, uses the root category "photography" - not the tags "blog/news" - which it would if "%tag%" were being sanitized properly. As I said before I'm trying to avoid having a complex category structure - the way I would have to set up the categories to get this permalink structure to create the URLs desired would be:
That's bad UX for the admins. Using this method the author will have to check the news/blog category, then check whatever is appropriate under that tree - not idiot proof. What I want are two separate lists (which, with the introduction of tags - I should be able to do):
Tags:
Categories:
Which drastically reduces the complexity for the Admin/Author. They choose the type of post (news/blog) - then the content type (photography/wedding/flowers).
I'm stuck on using tags partially because it makes for a much more elegant Authoring experience in this case. And, because WordPress says it can be used. But, WordPress is not sanitizing the "%tag%" in some cases.
have_comments() - was introduced in 2.7 to begin the new comment display loop. It is a binary (true/false) function - which determines if the post has comments associated with it (this is now working properly).
comments_number() - is a template tag - which is used in the default theme's comments.php file (version 2.7+) - also works properly.
wp_list_comments() - I don't want it to return category stuff. I want it too read the URL - get the appropriate comments - and display them. And, as of now, it does that properly - but, it didn't when I initially posted.
The form doesn't redirect to the proper post - because WordPress is creating a URL for the post based on incorrect sanitation of the permalink structure - hence %tag% not being removed. Which can be hacked by adding the following to the comment form:
<input type="hidden" name="redirect_to" value="<?php print($_SERVER['SCRIPT_URI']); ?>" />
However, if WordPress were sanitizing the %tag% properly - based on the personalized permalink structure - it wouldn't be needed.
Thinking of the recipe book analogy. Categories are hierarchical - macro to micro. Tags are independent of hierarchy. Therefore, let's use an apple pie as an example. This method would Tag the pie as "dessert". Category = pie. Pie could then have subcategories for type: Pie->apple. Another root category: Ingredients. With subcategories: Ingredients->apples, Ingredients->flour, Ingredients->eggs, etc. Therefore, when a user put in the URL:
domain.com/dessert - this recipe would appear.
Or:
domain.com/category/pie - this recipe would, again, appear.
Or:
domain.com/category/ingredients/apples
Regarding the tag cloud - I don't want to list the tags. This issue is all about URLs - not data display.
Having said all that.
The problem still remains. If I, as the admin set the permalinks to use tags in the permalink structure. Then use get_permalink() or the_permalink() - %tag% is not sanitized, which according to the ducumentation, it should be.
All other aspects pertaining to Friendly-URLs work fine and as expected.
Thanks again, really appreciate it.