Jump to content

Module: Blog


Recommended Posts


A couple of things:

  1. What version of Blog did you install? I don't know if you are aware there are two version 1.3 and 2.0. I speak about the latter in a couple of posts above. It will soon become the main version.
  2. If you installed version 2.0, which 'blog structure/style' did you install?
  3. You want to use the blank profile to test Blog. As for the 'double' rendering issue read this post. You probably did not install the blank profile? What you should see, after also copying the /css/ and /js/ that come with Blog to your templates folder is something like this. I repeat here that what you see is only a demo. It is up to you to design Blog to look just the way you want. If you need something that is (almost) ready out of the box (design-wise), then you are better of with the Blog Profile. If you want to design the look of your Blog from scratch plus get some additional features, then use Blog (module) :-)
  4. If using Blog 2.0, read up on install instructions above
  5. If you want to make best use of Blog, read the docs/tutorials here
Link to comment
Share on other sites

@ kongondo

Thanks for the quick reply.

I did use Blog 2.0

Both sites use style 1

I will follow your advice I will re-read  4 & 5 above.

May-be should learn to 'swim' better before tackling Modules.

Thanks again



I will try other styles and see the difference it makes. Is easy on http://lightning.pw

Link to comment
Share on other sites

I'm embarrassed but I need your help.

I'm willing to go back to another option but I installed option #4 but every quickpost (add) blog post writes itselve in the root of the 'home' directory. How/where do I tell the system to write each blogpost automatically as a child of say 'Home/blog' ?

For sure it's dead simple (and I'll have a red face when I'll read the reply) but I cannot see the tree from the wood right now ..

Thanks in advance,


(pw 2.5.3 - Module-blog 2.0.2)

Link to comment
Share on other sites


Yes it is possible using PW access settings (permissions and roles). However, by removing Authors and Tags, is it really still a Blog? :P. Also, when you render posts in the frontend you won't be able to hide author names attached posts.

Link to comment
Share on other sites

@ Kongondo

Firstly, a big thank you for your help! I switched to option #2 and I feel far more confortable with it. Even though I'm far from finished at least I'm really striding foreward as each Soccer team (They all have the same template) now has a different personal blog-category on it's page where the title of the page = the title of the blog-category and obviously ... a single post can appear in several teampages (blog-categories)

the code I used for this is:

<? $blog = $modules->get("MarkupBlog");
$category = $pages->get("/blog/categorieen/")->children->find("title=$page->title");
$posts = $pages->find("blog_categories=$category");
echo $blog->renderPosts($posts,true); ?>

euh so simple to get going .. 

Now .. before I start digging further and get the blog fully functional (comments, css, etc etc) I first would like to translate all EN words to NL -

Q. 1° Is there a specific place where I can do this?

Q. 2° If so, in case there is an update, will it affect the translated terms?

Many thanks,


Link to comment
Share on other sites


You can change this line:

$category = $pages->get("/blog/categorieen/")->children->find("title=$page->title");

to this:

$category = $pages->get("/blog/categorieen/")->child("title=$page->title");

Refer to $page->child($selector) in the cheatsheet

  • Like 1
Link to comment
Share on other sites

Just installed Kongondo blog module in PW multilanguage. Great concept!

I Just have a small question regarding empty template files. If I would like to display posts under a current category (blog_category) I could go with this:

$posts = $pages->find("template=blog-post, blog_categories={$page}");
$blog = $modules->get("MarkupBlog");
//if Blog Posts found, we render them out
if ($posts) {
echo $blog->renderPosts($posts);

else {
echo '<p>No posts found</p>';

But the haeder and footer are displayed UNDER the post. How do I get posts to be between this?

Link to comment
Share on other sites


Thanks for using Blog.

I moved your thread here since this is the support board for the Blog module. Please note it is not the Blog module profile  :P. OK, back to business.

I Just have a small question regarding empty template files. ......But the haeder and footer are displayed UNDER the post. How do I get posts to be between this?

I honestly do not understand the question :-). If you installed with empty template files, there is no header or footer there at all. Are you talking about your custom header and footer? You render the posts where you want them. Please clarify so I can give you a more definitive answer.

As for your code to display posts under a current category (blog_category) your code will only work if you are rendering those posts in a 'category' page similar to what is discussed a few posts above yours (#161 and #163). There is a related solution here if you want to limit posts of only a certain category but rendering the posts on other pages.

Also had some issues with back end markup...

That is very strange. I have never seen that. Maybe because I have never used the PW multi language site profile. Is that the one you are using? Are you using the stable (2.5.x) or dev version of PW? 

Link to comment
Share on other sites

Hi thanks for the reply.

1A. I installed the latest stable PW and choose multi-language. This is were the header/footer come from (_main / _init).

1B. I then installed your blog module which gave me the empty template files. The blog templates give me blog posts or categories (whatever I put there) and under it: header - content / sidebar - footer.

I have seen native PW currently prepend and append the _init / _main to ALL templates - which is fine. But I am not sure how to proceed. _main works with this part, should I add $posts in there?

<div id='main'>

        <!-- main content -->
        <div id='content'>
            <h1><?php echo $title; ?></h1>
            <?php echo $content; ?>

        <!-- sidebar content -->
        <?php if($sidebar): ?>
        <div id='sidebar'>
            <?php echo $sidebar; ?>
        <?php endif; ?>


2. The image with the back end issue is in the blog dashboard (posts/categories/tags). It does no damage, but it's just strange. Must be a comma or something in the admin tempate files somewere.

Link to comment
Share on other sites

Aah I see..

1B: Blog will actually not give you anything unless you selected it yourself/or let the default stay :-). For template files, I don't know if you realise you could have installed demo template files or none at all?

As for the _main / _init stuff, I think you will have to append renderPosts($posts) to $content. Have a read here where Ryan explains how the various site-profiles work. This other tutorial on structuring your template files is also useful. 

2B. Yes, I understood that bit. I just don't know why you are seeing that and others, including myself are not. I will have to test on a multi-language profile install to see if I get the same problem.

Link to comment
Share on other sites

I  can't get the code to work and hope you can help me.., beginner you know.

On the home page I would like to have the 3 latest posts, only title and the first part of the post. hiding post-byline works fine.

I used the code you advised. Is it possible to get latest posts and not only from a certain category. I have tried to put in my three categories (1042, 1043, 1044) ID's but that doesn't work.

$blog = $modules->get('MarkupBlog');
$category = $pages->get(1043);//This is ID of category'Fanions'. Can also get by other selector, e.g. name, title, etc.
$posts = $pages->find("template=blog-post, blog_categories=$category, limit=3");
echo $blog->renderPosts($posts);

Is it possible to truncate the post length? For example a function from a other post by Ryan.

Link to comment
Share on other sites


I used the code you advised. Is it possible to get latest posts and not only from a certain category. I have tried to put in my three categories (1042, 1043, 1044) ID's but that doesn't work.

Please read the documentation here

Posts are always returned sorted by date, latest first if you pass first parameter of renderPosts($posts) as a string

I used the code you advised. Is it possible to get latest posts and not only from a certain category. I have tried to put in my three categories (1042, 1043, 1044) ID's but that doesn't work.

I am not getting you clearly. Are you saying you want posts from ALL categories or from only THREE (1042, 1043 and 1044). If from only three, you can do the following:

$categories = $pages->find('id=1042|1043|1044');
$blog = $modules->get("MarkupBlog");
$posts = $pages->find("template=blog-post, blog_categories={$categories}, limit=10");

if ($posts) {
    echo $blog->renderPosts($posts, true);//the 'true' truncates posts' length

Read here about ProcessWire OR selectors.

Is it possible to truncate the post length? For example a function from a other post by Ryan.

Yes. This is all documented in the Blog tutorials. The default truncate length is 450 characters. You can set a custom length in your Blog settings page.

  • Like 1
Link to comment
Share on other sites

Reading instructions wrong I guess.

Did a new install. Placed the Blog Master folder in modules and installed with demo template files. But this time css and js is off - I can't see css and js under /site/templates/, I CAN find them under /modules/Blog-master/. Am I installing wrong? or should I disgard multi language?

Link to comment
Share on other sites


What you should do is get some sleep then read the instructions again  :lol:  :P  ;) .

The instructions are very clear. You need to read the ReadMe first in its entirety. The reason you don't see the css and js? Here's a quote from the ReadMe 'How to Install':

If you chose to install the demo Template Files, also manually copy over the /css/ and /js/ folders present in Blog module's folder to your /site/templates/ folder.

Link to comment
Share on other sites

Great! you was right, needed some sleep. lol

After the copy css/js it's good. I then disabled all append and prepend for blog templates. Because:

PW latest use _main to output header/body/footer;

and blog uses blog-main.inc to output header/body/footer.

Kongondo, can you tell me which file is used in back end for the /blog/posts/ - /blog/categories/ - /blog/tags/ ???

It seems in the Edit part is this code displayed as text (image I showed earlier).

Link to comment
Share on other sites

Is it possible to exclude pagination only on the homepage render posts? For example to set  MarkupPagerNav to false.

At the moment no. You would have to use CSS to hide the page navs I am afraid..

Kongondo, can you tell me which file is used in back end for the /blog/posts/ - /blog/categories/ - /blog/tags/ ???

It seems in the Edit part is this code displayed as text (image I showed earlier).

I tested in the multi-language site profile and saw something similar. I will raise the issue with Ryan to try resolve this. I don't know what is causing the problem but it is definitely only happening on the multi-language site profile and not the others.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      Github repository:
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/

    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
      Best regards
  • Create New...