In this article, you'll learn tips to fix problems that may occur when setting up blogs and catalogs in this system. Use the solutions below to address common isssues.
Resolving issues with missing images and styles in blogs or catalogs
If the content in a blog or cataloging is not displaying as expected, it may be due to the path to a CSS style sheet. If the CSS style sheet isn't linked correctly, the blog post or catalog may appear without any CSS rules, which causes it to look broken.
Here's an example of a CSS file not being loaded, which causes the page to ignore formatting rules:
This occurs because catalogs and blog posts are stored at a different level (one folder level up) in the site's directory structure. Ifthe link to CSS files or images do not use the site root relative path (meaning that their paths do not start from root (/) level of the site) they will not be displayed.
Here's some examples of links (to a CSS style sheet and an image) that are document relative, rather than site root relative:
To resolve the broken paths, you simply need to add a forward slash (/) to the beginning of the paths, as shown below:
After adding the forward slash before the links to CSS style sheets and images, and clicking Save and Publish, the catalog or blog post page displays correctly.
Configuring blogs or catalogs to look like the rest of the site
If you are using templates to define the appearance of site pages, you can also use the template to wrap around the blog or catalog content, to create a consistent visual experience for visitors.
Templates also have the added bonus of making a site easy to update, because you can edit a single file to change a large number of pages at once. Follow these steps to apply a template to a blog:
- Choose Website > Blogs.
- In the list that appears, select the name of your blog.
- The Blog Details page appears. Use the Templates menu to select the template you want apply to your blog.
- Scroll to the bottom of the page and click Save to save your work.
Spam content is being submitted into blog posts or comments
Spam is a serious concern for site administrators whenever you provide the general public with a mechanism to upload content. Unfortunately, it has grown worse over the years. If left unchecked, spam submissions can take over a site, causing it to look off topic and unsightly. A site with undeleted spam also looks like it is no longer supported, and may make visitors less likely to participate.
This system includes an image verification feature (known as CAPTCHA) which you can enable in blog posts, comments, web forms and Web Apps to inhibit spambots from spidering your site and circumventing the registration process to publish marketing links and other non-related (or inappropriate) content to a site. While there's nothing you can do to prevent a human from manually registering and uploading this type of content, (except to delete their registration and posts as quickly as possible) you can make it difficult for spambots to automatically enter spam with CAPTCHA.
The CAPTCHA interface requires that a person (not a computer) must read dynamically generated characters in an image file and then enter the matching characters into a form field. If the character values of the generated image file and the characters entered into the field do not match, the system will not enable the form to be submitted (or the comment to be posted).