The Upendo Blog Viewer module displays public blog content to website visitors. It can show article lists, a single article, search, search results, categories, tags, authors, popular posts, recent posts, and related posts. Blog Manager creates and maintains the content. Blog Viewer displays it.
This guide is for Site Admins, Administrators, Upendo Clients, Superusers, and content staff who have website permission to edit this module. Visitors do not need Blog Manager permission to read public articles.
What visitors see
The selected Widget View controls what the module shows:
- Blog Article List: A list of published articles.
- Blog Article: One article selected by its URL slug.
- Blog Search: A search box for blog content.
- Blog Search Results: Matching published articles.
- Blog Categories: Category navigation.
- Blog Tags: Tag navigation.
- Blog Authors: Author navigation.
- Most Popular Posts: Articles with the most views.
- Most Recent Posts: Newest published articles.
- Related Posts: Articles related to the current article.
Visitors see only public content. Drafts, future articles, archived articles, and deleted articles are not shown in normal public views.
The module uses normal website page and module permissions.
- Anonymous visitors can use the viewer when the page is public.
- Signed-in visitors may be able to comment when comments are enabled.
- General content editors can configure the viewer only when they have website Edit permission for the page or module.
- Site Admins, Administrators, and Upendo Clients can usually configure it when their website permissions allow page and module editing.
- Superusers can manage it through website administration.
Blog Publisher Roles control Blog Manager writing access. They do not automatically grant permission to change Blog Viewer settings.
Open Blog Viewer settings
- Sign in to the website.
- Open the page that contains Blog Viewer.
- Use the page or module menu to choose Settings.
- Open the Blog Viewer settings.
- Save the settings through the normal website module settings controls.
The settings are a mix of page-level and module-instance values. This matters when several Blog Viewer modules are placed on the same page.
Page-level settings
These values are saved for the whole page:
Blog Title
This is the visitor-facing title for the blog area. Use a clear name such as Company News, Resources, or The Upendo Blog.
Blog Description
This is a short description used by list views and as a fallback for page information. Explain what visitors can find in the blog.
Template
The selected template controls the file-based presentation used by Blog Viewer modules on the same page. If several viewer modules share the page, changing the template can affect them together.
Review every viewer on the page after changing this value.
Module-instance settings
Root Path
This is the friendly URL root for the blog, such as:
~/blog/
~/news/
~/press/
~/jobs/
The module adds an article slug after this path. A root path is automatically cleaned so it starts with a website path and ends with a slash.
Use one clear root path for the blog area. Avoid changing it after articles are public unless you have a redirect and link plan.
Search Results Path
This is the page where the Blog Search widget sends visitors. Put a Blog Search Results widget on that page.
Do not use a /search path segment for the search results URL. The module has special handling for search routes, and a clear page path avoids confusing links.
If this setting is empty, Blog Viewer uses the root path.
Choose the purpose of this module instance. Use a separate viewer module when a page needs more than one purpose. For example:
- Use Blog Article List on a news landing page.
- Use Blog Article on the page that displays one article.
- Use Blog Search in a search area.
- Use Blog Categories or Blog Tags in a sidebar.
- Use Most Recent Posts on a home page.
List Layout
Choose Horizontal for a wide content area. Choose Vertical for a sidebar or narrow column.
Check both desktop and mobile views after changing the layout.
Page Size
This is the maximum number of articles shown in list-style views. Blog Viewer accepts values from 1 to 50. A smaller value can make a page easier to scan and faster to read.
Turn this on when visitors should be able to add comments to articles. Comments are available in the article view, not every widget view.
Comments add moderation and privacy work. Decide who will review them before enabling this option.
When enabled, visitors must sign in before they can comment. Requiring login usually improves moderation quality and reduces unwanted submissions.
Enter comma-separated email addresses for comment notices. Notifications include a link to the comment rather than placing the full comment text in the email.
Use monitored staff addresses. Remove old addresses when staff responsibilities change.
Quick setup from the page
Some Blog Viewer pages provide a quick setup panel. It can help finish the first setup without leaving the page. Page-level title and description values may be saved for the whole page, so check whether another Blog Viewer instance already uses them before saving.
Set up a normal blog
- Create or select a public page for the blog.
- Add Blog Viewer and choose Blog Article List.
- Set the Blog Title and Blog Description.
- Set the Root Path, such as
~/blog/.
- Set the Blog Article Path in the companion Blog Article List module to the page that will show one article.
- Add a second Blog Viewer instance for Blog Article if the site uses a dedicated article view page.
- Set the Search Results Path and add a Blog Search Results instance to that page.
- Choose the template and list layout.
- Enable comments only after deciding how they will be moderated.
- Save the settings.
- Open a published article, test search, and test the main navigation links.
Search behavior
Blog Viewer searches published blog content. A search with no matches shows a message asking the visitor to try another term. Search results include a count and paging when more results exist.
Test common words, a title phrase, and a term that should return no results. Confirm that the search form sends visitors to the configured Search Results Path.
Friendly article URLs
Blog Viewer supports readable article URLs based on the Root Path and article slug. The URL provider only changes blog paths on pages that host Blog Viewer. This prevents unrelated pages that use similar URL parameters from being changed.
After changing a root path or article path, test:
- A direct article link.
- A link from an Article List module.
- A category or tag link when available.
- Search and search results.
- An old article link if the site has existing traffic.
If comments are enabled:
- Confirm who can comment.
- Confirm who receives notices.
- Decide how quickly staff will review comments.
- Remove or change notification addresses that are no longer monitored.
- Test the comment form as a normal visitor.
Do not enable comments on a page unless someone owns the moderation task.
Common problems
The page is blank
Check the widget view, Root Path, page permissions, and whether Blog Manager contains published articles. Also check that the selected template exists in the installed module files.
Search returns no results
Check the search term, confirm that matching articles are published, and make sure the Search Results Path points to a page containing Blog Search Results.
Article links open the wrong page
Check the Root Path in Blog Viewer and the Blog Article Path in Blog Article List. The article page must contain a Blog Viewer instance using the Blog Article view.
Check that Enable Comments is on, that the current widget view is Blog Article, and that Require Login for Comments matches the visitor's sign-in state.
A content editor cannot change settings
Give the person the needed website Edit permission for the correct page or module. Adding a Blog Publisher Role changes Blog Manager access, not website page configuration access.
Before you finish
- Visitors can open the page without an error.
- The correct widget view is selected.
- The title and description fit the page.
- Root Path and Search Results Path are correct.
- Article links open the intended article page.
- Search results work.
- Comments are enabled only when they will be moderated.
- Notification email addresses are monitored.
- The page works on desktop and mobile.