Blog pages in CS 2007

What happens with them? I created four of them in a blog, and exspected to see them in the this blog sidebar, but they just aren't there. Is this a bug, or are the pages just there for content and should I link manually to them with a list?

Hi WTR,

You are correct. Blog pages differ from blog posts in that they're not aggregated or listed. You'll need to manually link to them. Either within some other content or in a list of links.

Thanks... 

Jose Lema:

Hi WTR,

You are correct. Blog pages differ from blog posts in that they're not aggregated or listed. You'll need to manually link to them. Either within some other content or in a list of links.

Thanks... 

Ok, thanks for clearing that up.

Howdy,

I just wanted to add that there is one place that links to blog pages do appear automatically.  When you are browsing the tag cloud, any pages that have the tag you are looking at will apear in the list along with regular posts.  If you don't want this to happen, then do not tag your pages.

You could create a new tag and use it on just blog pages to have a simple way to view all of the pages in your blog.  For example, the Microsoft Exchange Team blog uses pages for team bios, and tags each one with the "Team Bios" tag. So clicking that tag gives you a list of all the team bios pages. (http://msexchangeteam.com/archive/category/3078.aspx)

Mostly Useless Trivia:  Blog pages used to be called articles before CS 2.1, for those who have been using CS for a while.  We renamed them to "pages" to prevent confusion with content articles (the Manage Articles page in the Tools Control Panel section).

Hmmm. That's very interesting. While on the subject, I came across a few more questions: is there any way to add an editable region to an article (not a page!) like the welcome article? Cause right now, the lay-out just seems to disappear completely. Second, is there a way to disable tagging of posts, except for certain roles? EDIT: Forget about the question about lay-out for articles, I just notice Opera stripped all TinyMCE options, and wouldn't accept lay-out, while firefox and ie work fine with them. This also happens when creating a blog. I hope it's just my browser and not a global thing.

Tagging of blog posts is dependent on the "Manage Content" permission.  It is not a seperate permission from creating/editing posts.

You could add code to the blog post editor that could hide the tag editing controls for certain roles -- if this is what you would like to do, I can provide a code sample.

Ben Tiedt:

Tagging of blog posts is dependent on the "Manage Content" permission.  It is not a seperate permission from creating/editing posts.

You could add code to the blog post editor that could hide the tag editing controls for certain roles -- if this is what you would like to do, I can provide a code sample.

That would be great! Thanks a lot!

WTR:

That would be great! Thanks a lot!

1.  Open the web/ControlPanel/Blogs/CreateEditBlogPost.ascx user control.

2.  Locate the tags controls and wrap them in a <asp:PlaceHolder /> control, so the change would look like:

<asp:PlaceHolder ID="TagsArea" runat="server">
    <div class="CommonFormFieldName">
     <cp:helpicon id="Helpicon1" runat="Server" resourcename="Weblog_CreateEditBlogPost_Categories_Sub" />
     <cp:formlabel id="Formlabel3" runat="Server" resourcename="Weblog_CreateEditBlogPost_Categories" />
    </div>
    <div class="CommonFormField">
     <cp:TagEditor runat="server" id="Tags">
         <SkinTemplate>
    <table cellpadding="0" cellspacing="0" border="0">
    <tr valign="top">
    <td>
            <asp:TextBox Columns="70" ID="Tags" runat="server" />
    </td>
    <td>
            <CP:Modal modaltype="Button" width="400" height="300" runat="Server" id="SelectTags" ResourceName="TagEditor_SelectTags" />
    </td>
    </tr>
    </table>
         </SkinTemplate>
     </cp:TagEditor>
    </div>
    <p id="DefaultTagsContainer" runat="server">
     <cp:resourcecontrol runat="server" resourcename="CP_Blogs_CreateEditBlogPost_DefaultTagsNotice" /><br />
     <asp:literal id="DefaultTags" runat="server" />
    </p>
</asp:PlaceHolder>

3.  Add the following into the OnLoad method defined at the top of the page (if you have beta-2):

if (!CSContext.Current.User.IsInRoles(new string[] { "RoleName" }))
{
    TagsArea.Visible = false;
}

This will hide the tags form when the user is not a member of the RoleName role.  You can change this role name to match the role you want to *allow* to enter/edit tags.

Great stuff! Thanks for sharing this.

 I'm having some strange behavior with this.  When I create and tag a new Blog page, it shows up under the "What's New" community aggregation on the default home page, and I'm able to use the home page's tag cloud to navigate to those pages.  However, if I go directly to my blog, the tags show up in the tag clouds, but navigating through them never produces a blog page in the search results.

I'm trying to find the difference between [root]/tags and [root]/blogs/[blogname]/archive/tags as to why one would show blog pages, and the other not.

And whats the deal with the "archive" directory anyway (total aside really, I'll look around for the answer... the previous issue is more important).
 

/tags/ uses the search index to show posts whereas /blogs/[blog name]/archive/tags/ uses a direct query against blog posts.

The direct query within the blog-specific tags browser, by default, only shows posts and not posts + pages.  To show posts *and* pages, you can add

BlogPostType="Post,Article"

on the <QueryOverrides /> of the <CSBlog:WeblogPostList /> control in the taglist.aspx page within the blog theme.

You may go by Ben Tiedt, but I call you Ben Pwns. 

Thanks a ton, it worked like a champ.  I'm going to have to futz with the source code to get a handle on all my options.

Kevin Harder:

Howdy,

I just wanted to add that there is one place that links to blog pages do appear automatically.  When you are browsing the tag cloud, any pages that have the tag you are looking at will apear in the list along with regular posts.  If you don't want this to happen, then do not tag your pages.

You could create a new tag and use it on just blog pages to have a simple way to view all of the pages in your blog.  For example, the Microsoft Exchange Team blog uses pages for team bios, and tags each one with the "Team Bios" tag. So clicking that tag gives you a list of all the team bios pages. (http://msexchangeteam.com/archive/category/3078.aspx)

Mostly Useless Trivia:  Blog pages used to be called articles before CS 2.1, for those who have been using CS for a while.  We renamed them to "pages" to prevent confusion with content articles (the Manage Articles page in the Tools Control Panel section).

thx