Managing Blog Posts in CRM
For CRM users, Blog Posts can be managed by launching the editor for the desired Blog, and then navigating to its related Blog Posts (Figure 1.1).
Managing Blogs Posts on a Portal
For portal users with blog author permissions (see Blogs), blog posts can be managed using the portal inline editing interface. If your user account has been assigned the necessary permissions, the inline editing interface will appear automatically when you sign in to the portal and navigate to the blog.
To create a new blog post, navigate to the blog home page, and click New > Blog post on the edit toolbar. The blog post editor dialog will appear (Figure 2.1). Make any edits desired, then click Save to save your changes.
To edit a blog post, navigate to the blog post's page, and click the Edit button on the edit toolbar. The blog post editor dialog will appear (Figure 2.1). Make any edits desired, then click Save to save your changes.
When creating or editing a blog post, if the Partial URL field is left blank, one will be generated automatically. The auto-generated Partial URL will have the format
yyyy-mm-dd is the year, month, and day of the post's Date, and the remainder is the post Title, tranformed into a URL-appropriate form.
The Tags field of the post editor (Figure 2.2) provides autocomplete of tag names, to associated posts with existing tags. It is also possible to simply type the name of a new tag. To end a tag name and start a new one, type
,. To remove a tag, click the
x beside the tag name, or type
To delete the blog post, click the Delete button, and click Yes on the confirmation dialog.
Warning! Deleting a blog post will also delete its associated comments.
Only the author of a blog post can edit or delete that post, through the front-side portal editing interface. The author of a post can also see their own unpublished posts, but not those of other authors.
Blog Post Attributes & Relationships
The table below explains the standard attributes & relationships of the Blog Post entity.
It is important to note that the way in which many of the content/display-oriented attributes are rendered is controlled by the Page Templates used, and thus ultimately by the portal developer.
The title of the blog post.
The Blog to which the post belongs.
The URL path segment used to build the portal URL of the blog post.
Partial URL values are used as URL path segments. As such, they should not contain illegal URL path characters, such as "?", "#", "!", "%". Since Adxstudio Portals URLs are generated by joining together Partial URL values with slashes ("/"), they should also not generally contain slashes.
Recommended practice would be to restrict Partial URL values to letters, numbers, and hyphens or underscores. For example: "press-releases", "Users_Guide", "product1".
The author of the post, represented by a Contact record.
The pubishing date for the post, to be displayed on a portal. This value determines how posts are sorted for display in views that display posts from newest to oldest. This value does not control when or if the post is actually made visible on a portal.
HTML content providing a short summary or excerpt of the post. If present, this should be used by the blog templates and syndication feeds as the content of the post, with the full content only being available at the post URL.
The full HTML content of the post.
Determines whether or not a post will be visible on a portal. If checked, the post is visible to all users that have read access to the blog. If not checked, only the author of the post will be able to preview the post on a portal.
An option that specifies how comments on the post should be handled.
|Blog Posts Comments||
All comments associated with the post.
All files assocaited with the post.
All tags associated with the post.