Blog Revolution: setup and help

Upload and install mprblogrevolution, then click Configure or open Blog > Settings > Configuration. The Blog menu contains Dashboard, Posts, Categories, Tags, Comments, Authors, Import / Export and Settings. Settings contains Configuration, Integrity, License, Support and Update.

Create an author and a category, then open Blog > Posts. Add a post with Title, Content, URL slug, Category, Author, Status and Publish date. Fill translated content for each language you publish. Set Status = Published and a current publish date for your first test. Open the public post from the Back Office and check it before linking it in navigation.

A published post becomes public only when its publish date has arrived according to the database clock and it is active in the requested shop. For a future publication, use Published with a future Publish date. The separate Scheduled status does not automatically change to Published.

Open Blog > Settings > Configuration. In the General group:

• Posts per page. Controls how many posts appear on blog listing pages; default: 12.
• List layout. Controls listing style: grid, list, masonry, cover, or compact; default: grid.
• Grid columns. Controls the number of columns in grid layouts: 2, 3, or 4; default: 3.
• Show author. Shows the author name in blog listings and widgets; default: 1.
• Show date. Shows the publish date in blog listings and widgets; default: 1.
• Show view count. Shows post view counts; default: 1.
• Show comment count. Shows comment counts; default: 1.
• Show rating. Shows post ratings where the template supports them; default: 1.
• Show excerpt. Shows excerpts on post cards; default: 1.
• Excerpt length. Sets the maximum length for auto-generated excerpts; default: 200.
• Enable likes. Allows visitors to like posts; default: 1.
• Show like count. Shows the number of likes next to the like control; default: 1.
• Date format. Uses a PHP date() format string for blog dates; default: M d, Y.
• Timezone. Uses an IANA timezone such as Europe/Warsaw; default: '' to use the shop default.

Blog index cards defaults to overlay. Use this to choose the card presentation on the main blog index. Review it together with List layout and Grid columns. Enable only the card metadata you want visitors to see. GDPR compliance defaults on and enables the module's comment export/delete hooks.

The Timezone preference controls date presentation. Publication still follows the database clock. If a future post appears at the wrong time, compare its saved Publish date with the shop database time.

Comments

• Enable comments. Enables the native comment form on posts; default: 1.
• Allow guest comments. Lets non-logged-in visitors comment with a name and email address; default: 1.
• Auto-approve comments. Publishes new comments immediately instead of leaving them pending; default: 0.
• Notification email. Sends new comment notifications to this address when filled; default: ''.
• Privacy policy URL. Sets the link used by the comment consent checkbox; default: '', which falls back to /privacy-policy.
• Enable ratings. Allows 1-5 star ratings with comments and AJAX rating actions; default: 1.
• Comment system. Selects native, native_disqus, native_facebook, native_social, disqus, or facebook; default: native.
• Disqus shortname. Required for Disqus-only or native-plus-Disqus modes; default: ''.
• Facebook App ID. Required for Facebook Comments modes; default: ''.
• Enable reCAPTCHA. Protects the comment form with Google reCAPTCHA v2; default: 0.
• reCAPTCHA site key. Public key used by the comment form widget; default: ''.
• reCAPTCHA secret key. Server-side key used to verify comment submissions; default: ''.
• Staff highlight emails. Comma-separated emails whose comments are highlighted as staff comments; default: ''.

Use Blog > Comments to review pending comments. Auto-approve comments = No is the default. New guest comments need a name, valid email, comment text and privacy consent. Comment text must contain 3 to 5000 characters. Native post-level Allow comments also affects the public form.

Choose the native comment system for the initial test. For Disqus modes, set Disqus shortname. For Facebook modes, set Facebook App ID. Mixed native/social modes retain the native form alongside the selected social system. Google reCAPTCHA v2 needs both keys before it can protect native submissions.

Comment moderation and reply notifications are on by default, with no separate fields in the current form. Auto-approval controls publication. Reply notifications depend on the configured shop mail delivery. Set Notification email to receive new-comment notifications.

Social

• Enable social sharing. Shows the sharing block on post pages; default: 1.
• Facebook. Shows the Facebook share button; default: 1.
• Twitter/X. Shows the X/Twitter share button; default: 1.
• Pinterest. Shows the Pinterest share button; default: 1.
• LinkedIn. Shows the LinkedIn share button; default: 1.
• WhatsApp. Shows the WhatsApp share button; default: 1.
• Email. Shows the email share button; default: 1.

The native share block also supports copying the post link. Check the generated title, image and URL in a public post before sharing it.

Native comment data requests

With GDPR compliance enabled, the module registers native comment-data disclosure, export and deletion hooks. Native comments can contain a name, email address and IP address. The export and deletion hooks locate local records by customer ID, or by guest email when no customer ID is supplied. Deletion recalculates ratings for affected posts.

These hooks operate on Blog Revolution's own comment table. They do not export or erase comments held by Disqus or Facebook. Handle those records through the selected provider's tools.

In the SEO group:

• URL prefix. Sets the base blog URL segment, for example /blog or /guides; default: blog.

• Schema.org markup. Adds native BlogPosting schema on post pages and CollectionPage schema on first listing pages; default: 1.

• OpenGraph tags. Adds social preview meta tags on blog pages; default: 1.

• Category URLs. Default: segment. Use /blog/category/category-slug, or choose the flat mode /blog/category-slug. Flat mode shares the slug namespace with posts. Existing category addresses are handled when switching styles.

• Category pages robots directive. Default: noindex,follow.

• Paginated blog listing robots directive. Default: noindex,nofollow after the first main listing page.

• Blog search robots directive. Default: noindex,nofollow.

In inherited shop contexts, the robots fields may offer Inherit with the effective parent directive. Set these deliberately for the intended shop.

The native output includes BlogPosting data on public posts and listing schema where supported. Hreflang alternates follow the module's public-page integration; there is no separate Hreflang alternates field in this form. When another SEO module owns these tags, inspect the final page source for duplicates.

The default blog title is Blog, and the blog meta description is empty. The default meta title pattern is {title} - {shop_name} and the default meta description pattern is {excerpt}. These defaults have no separate fields in the current configuration form. Use the post's Meta title, Meta description, Meta keywords and optional Canonical URL for individual metadata. No legacy X/Twitter handle is set.

In the RSS group:

• Enable RSS feed. Enables the RSS endpoint at the configured prefix plus /rss; default: 1.
• RSS items. Sets the number of posts included in the feed; default: 20.
• RSS content. Chooses excerpt or full content in RSS descriptions; default: excerpt.

After changing URL prefix to guides, check these example paths:

/guides
/guides/my-post-slug
/guides/category/category-slug
/guides/tag/tag-slug
/guides/author/author-slug
/guides/archive/2026/6
/guides/search
/guides/rss

Use the shop-generated links when your shop adds a language prefix or subdirectory. Authors also have a listing page. Open RSS and inspect its title, author/category data, publish dates, chosen excerpt/full content and image enclosures.

Sidebar

• Enable sidebar. Enables blog sidebar rendering on left and right column hooks; default: 1.
• Recent posts widget. Shows recent posts in the sidebar; default: 1.
• Recent posts count. Sets how many recent posts appear in the sidebar; default: 5.
• Popular posts widget. Shows popular posts in the sidebar; default: 1.
• Popular posts count. Sets how many popular posts appear in the sidebar; default: 5.
• Categories widget. Shows blog categories in the sidebar; default: 1.
• Tags cloud widget. Shows a tag cloud in the sidebar; default: 1.
• Max tags in cloud. Sets the maximum number of tags shown; default: 20.
• Archive widget. Shows archive links in the sidebar; default: 1.
• Featured posts widget. Shows featured posts in the sidebar; default: 1.
• Featured posts count. Sets how many featured posts appear in the sidebar; default: 3.
• Show category bar. Shows horizontal category navigation on blog listing pages; default: 1.

Latest Articles widget style defaults to banner-dark. Change it when you need another available sidebar card treatment. Widgets depend on the left/right column and other hook positions rendered by your theme.

Images

• Large image width. Sets generated large image width; default: 800.
• Large image height. Sets generated large image height; default: 450.
• Medium image width. Sets generated medium image width; default: 400.
• Medium image height. Sets generated medium image height; default: 225.
• Thumbnail width. Sets generated thumbnail width; default: 200.
• Thumbnail height. Sets generated thumbnail height; default: 112.
• Image quality. Sets JPEG quality from 1 to 100; default: 85.

Images are stored under /img/mprblogrevolution/ by default. The storage path is not a visible editable field in the current Images group. After changing dimensions, use Thumbnail maintenance > Regenerate Thumbnails to rebuild post, category and author variants. Ensure the PHP process can write to the image folders. Images remain after uninstall regardless of Delete images on uninstall, which defaults off.

Assets and theme styles

• Load module assets automatically. Lets the module load its CSS and JavaScript through the asset manager; default: 1.
• Use shop defaults. Lets empty module asset settings fall back to shared shop asset settings; default: 1.
• Browser cache refresh. Controls asset versioning: mtime, module_version, or none; default: mtime.
• Use optimized settings file. Writes asset settings to generated cacheable files instead of inline page output; default: 1.
• Generated settings files to keep. Keeps this many generated asset config files; default: 12.
• Generated settings retention days. Keeps generated asset config files for this many days; default: 7.
• Troubleshooting mode. Enables asset debugging output while checking loading problems; default: 0.
• Theme styles. Uses detected shop colors for text, muted text, accent, accent hover, border, backgrounds, danger, and success colors, plus a Blog-only rating star color; default: detected theme values, with star color #e8a838.

Use Troubleshooting mode temporarily when checking asset delivery, then turn it off. The shared asset controls include Asset cache actions. Theme style controls apply detected shop values and a Blog-specific rating star color. Card title size is also available as a Blog-specific style.

The post editor supports Short title, Excerpt, Featured Image, Cover Image, Tags, Featured, Allow comments, Access restriction and product selection as well as the initial fields. One post stores one author ID. Create separate author profiles in Blog > Authors as needed.

Choose Post type standard, gallery, video or link. Set Video embed code for a video post and External URL for a link post. Use only content you intend to publish. Review the rendered result for each type.

Add related products with the post's product selector. To place products inside Content, use these shortcodes:

[products ids="12,34,56,78"]
[products category="3" limit="4"]
[products new limit="4"]
[products bestsellers limit="4"]

The default shortcode limit is 4 and the maximum is 12. Only active products the shop can load are displayed. A shortcode with no valid products is removed from the output.

On a public post, check the title, metadata, images, article content, generated table of contents when enough H2/H3 headings exist, share block, author, related content, related products, comments, ratings and likes. Their visibility depends on your settings and theme.

Open Blog > Import / Export. Back up current data before importing. The WordPress import accepts WXR XML up to 50 MB, subject to your server's upload limits. SimpleBlog imports are also supported. Inspect imported authors, categories, dates, slugs, images, related content and publication state before exposing them.

Export Blog Revolution data as XML or JSON before a migration. Do not assume a data export alone contains all binary image files; back up the image storage too. There is no fixed module count limit for posts, categories, tags or comments. Hosting, database size and Back Office operations still constrain practical volume.

The module can render home, footer, column and product-related widgets. If your theme does not render a position, add it deliberately in the theme template:

{hook h='displayHome' mod='mprblogrevolution'}
{hook h='displayLeftColumn' mod='mprblogrevolution'}
{hook h='displayRightColumn' mod='mprblogrevolution'}
{hook h='displayFooter' mod='mprblogrevolution'}
{hook h='displayFooterProduct' mod='mprblogrevolution' product=$product}

Theme overrides can use these paths:

themes/your_theme/modules/mprblogrevolution/views/templates/front/post.tpl
themes/your_theme/modules/mprblogrevolution/views/templates/front/list.tpl
themes/your_theme/modules/mprblogrevolution/views/templates/front/_partials/_post_card.tpl
themes/your_theme/modules/mprblogrevolution/views/templates/front/_partials/_product_block.tpl

Useful CSS targets include .mprblog-post-title, .mprblog-product-block, .mprblog-comment-form and .mprblog-star. The rating color uses --mprblog-star, with fallback #e8a838.

MPR Search Revolution can receive blog articles through actionMprSearchRevolutionRegisterContentProviders. The blog returns its versioned provider descriptor when that integration hook is called. The blog also has native search/AJAX search and sitemap hooks. Test the installed search and sitemap providers rather than assuming a hook registration alone makes a post appear in every search or sitemap.

Run Blog > Settings > Integrity. Open the blog index, a post, category, tag, author, archive, search and RSS in the intended shop and languages. Submit a guest test comment with consent, approve it, test a reply and check mail delivery. Test a rating and a like separately.

If a post is missing, check Published status, database time, language content, shop activation and access restriction. If images fail, check stored filenames, folder permissions and regenerated variants. If widgets fail, check the theme hooks and sidebar switches. For comments, check global and post controls, moderation, guest permissions, consent and any configured reCAPTCHA or social credentials.

Export data and back up images before uninstalling. Uninstall removes menus, module configuration and module schema. The image folder remains regardless of the delete-images preference. Remove scheduler or navigation integrations you added, and replace inbound blog links. Do not expect posts or comments to remain usable after uninstall.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.