Jump to content

Module: Blog


Recommended Posts

Is it possible to hide the author link shown in the sub-nav sidebar (under the heading See Also)?

I've hidden the author in the post itself from the Settings in the Blog dashboard, but I'd like to do the same in the sidebar (since all posts will be written by the same author so it's rather redundant).

Having looked at the html I see that each sub-nav link is a <li>, but they're not given a unique class or ID so it's hard to target them individually.

All the best,



It seems you are using (or copied from) the demo template files that are optionally installed with Blog. In this particular case we are dealing with blog-post.php. The code that generates that sidebar is found between lines 24 - 35. The method spewing out the markup is renderNav() (line #35).  As a quick btw, the general rule of thumb is rather than using CSS to hide markup, first check if it is possible not to output that markup in the first place :-). In our case, it is possible. Line #31 of the code is what is outputting the Author's name and URL. All you need to do is comment out that line, as well as earlier variables building up towards that code, i.e. lines 25 ($authorsURL), 27 ($authorURL) and line 28 ($authorName).

I'm not sure you've seen my earlier posts about documentation (it is a long thread after all), but I used to have Blog's documentation hosted on my website, which is currently in deep hibernation until I get time to revive it. Thankfully, the good guys over at wayback machine archived my now asleep and offline website including all the Blog tutorials. These can be found here and the documentation for renderNav() is here. As you'll see, you can use renderNav() to output all sorts of stuff.

Hope this helps :-)

  • Like 2
Link to comment
Share on other sites


Sorry this is one of those things that hasn't yet found its way into the documentation. Almost each method in MarkupBlog accepts options to alter its output. For the example you've given, that would be an option in renderComments(CommentArray $comments, $limit = 0, Array $options = null). Within the method, the $defaultOptions are as listed here. The option responsible for 'Post a comment' is 'comments_post_text' => $this->_('Post a comment'), . An example of passing options to the method:

$options = array(
   'comments_post_text' => 'My Text for Post-a-Comment',
   'comments_list_empty' => 'Nobody has dared to comment on this article...yet',
   'comments_empty' => 'Are you sure you want to be the first to comment?'

$blog = $modules->get("MarkupBlog");
$renderComments = $blog->renderComments($page->blog_comments, 0, $options);
$content = $blog->renderPosts($page) . $renderComments; 

echo $content;
Link to comment
Share on other sites

Ok. Get it to work  :lol:

I put it in my blog-post.php and changed something looks now like this:

$options = array(
   'comments_post_text' => 'My Text for Post-a-Comment',
   'comments_list_empty' => 'Nobody has dared to comment on this article...yet',
   'comments_empty' => 'Are you sure you want to be the first to comment?'

$renderComments = $blogConfigs['commentsUse'] == 1 ? $blog->renderComments($page->blog_comments, 0, $options) : '';
Link to comment
Share on other sites

Two things:

  1. You never need to change the code in the module itself! Otherwise, your changes would be overwritten with upgrades
  2. You don't need this code to be like this: 
$renderComments = $blogConfigs['commentsUse'] == 1 ? $blog->renderComments($page->blog_comments, 0, $options) : '';

If you read the comments in the demo blog-post.php template file, it says

for this demo, renderComments() has to adapt to whether blog commenting feature was installed or not whilst remaining blog structure/style-agnostic

 in your own blog install, you would know if you enabled the feature so there would be no need for such a check
in addition, our 'check' code is not code you would normally use in a template file. 
we use such code here to be both foolproof that the commenting feature is installed and blog structure-agnostic 

The blog demo could not know in advance whether you or anybody else was going to install Blog with the comments feature enabled/disabled. Hence, it had to make that check by looking into the module configs ($blogConfigs). In your case , you know if you installed blog with the comments feature or not, so no need to make such a check. Hence, use the other code I provided instead, i.e.

$options = array(
   'comments_post_text' => 'My Text for Post-a-Comment',
   'comments_list_empty' => 'Nobody has dared to comment on this article...yet',
   'comments_empty' => 'Are you sure you want to be the first to comment?'

$blog = $modules->get("MarkupBlog");
// Here, no need to check if blog was installed with comments feature; you should know - you installed it yourself 
$renderComments = $blog->renderComments($page->blog_comments, 0, $options);
Link to comment
Share on other sites

Thank you very much! This helps me a lot.

Another question i have is, can i change classes the same way? I searched this topic but didn't find an answer.

For example:

In my blog overview there is

<ul class="MarkupPagerNav">
	<li class="MarkupPagerNavOn MarkupPagerNavFirst MarkupPagerNavFirstNum"><a href="/blog/"><span>1</span></a></li>
	<li class="MarkupPagerNavLastNum"><a href="/blog/page2"><span>2</span></a></li>
	<li class="MarkupPagerNavNext MarkupPagerNavLast"><a href="/blog/page2"><span>Vorwärts</span></a></li>

how can i give "MarkupPagerNav" a second class like "pagination". I'm working with Zurb's Foundation Framework.

Link to comment
Share on other sites

Update: Version 2.3.7

Following this question, it is now possible to pass MarkupPagerNav options to renderPosts() if you wish to customise your posts' pagination. All the MarkupPagerNav options listed here can be passed as an array within an array to renderPosts() as shown in the example below:

$blog = $modules->get("MarkupBlog");

$paginationOptions = array(
                'nextItemLabel' => "Forth",
                'previousItemLabel' => "Back",
                'listMarkup' => "<ul class='MarkupPagerNav Zurb pagination'>{out}</ul>",
                'itemMarkup' => "<li class='{class} not necessary class'>{out}</li>",
                'numPageLinks' => 5

$options = array(
        'post_pagination' => $paginationOptions,// array of markup pager nav options
        'post_count_text' =>'Article',// other posts options passed as normal

echo $blog->renderPosts("limit=5", true, $options); 
  • Like 3
Link to comment
Share on other sites

Hi kongondo,

that's amazing! Thank you for your help. I tried it and it worked when i copy your code.

But i already hav an array for the defaults options. To translate "more" to "mehr" for example.

$content .= $blog->renderPosts("limit=5", true, $defaultOptions);

How can i put the second array behind the $defaultOptions array? I tried google. Is array_merge an option?

Link to comment
Share on other sites

Just like I've shown you in the example above :-). No need to do merges and such. See below (including the comments in the code); hope this is now clearer.

$paginationOptions = array(
                'nextItemLabel' => "Forth",
                'previousItemLabel' => "Back",
                'listMarkup' => "<ul class='MarkupPagerNav Zurb pagination'>{out}</ul>",
                'itemMarkup' => "<li class='{class} not necessary class'>{out}</li>",
                'numPageLinks' => 5

$defaultOptions = array(
        //  array of MarkupPagerNav options
        //  you have to use the index 'post_pagination' and its value MUST be an array
        //  here, we've passed it the array $paginationOptions that we created above
        'post_pagination' => $paginationOptions,// the value here must be an array; the index must be named 'post_pagination'
        // other stuff you already had in your defaultOptions
        'post_more_text' => 'mehr',
        'post_whatever_option_1' => 'blah blah blah',
        'post_whatever_option_2' => 'foo bar',

$content .= $blog->renderPosts("limit=5", true, $defaultOptions);
Edited by kongondo
  • Like 2
Link to comment
Share on other sites


i have still some things that i needed to change. Maybe someone knows the answers.

1. After i installed the modul upgrade Processwire says that i have more then one of this modules installed and that i have to choose.

Is this normal?

2. It is possible to add a new entry to the shortcut menu (backend) in Processwire? Blog Category and Blog Tag are already there.

How can i add for example Blog Post?

3. In the Comments section the date is still in english. I changed the date value in blog_date field into german

am %A, den %d.%m.%Y

I tried the same in the field blog_comments. But this doesn't work.

Link to comment
Share on other sites

#1: Not normal. PW version? If you ugraded using PW, it should have renamed the older folder as .ProcessBlog or similar


A PW date field has two parts. The output and input formats. Have a look at both (input is in the input tab).

  • In the Details tab (Date/Time Output Format Code), you can use your strftime code: am %A, den %d.%m.%Y. You will see that date in the frontend (in your post)
  • In the Input tab (Date/Time Input Formats -> Date Input Format Code) I think you can only use PHP date. So, something like l, d.m.Y in the date input format code will give you Thursday, 11.08.2016. You will see that when editing your post in the backend. You will not be able to uses 'den' with PHP date 
Edited by kongondo
Link to comment
Share on other sites

The Processwire Version is 2.7.0. I have a folder MarkupBlog and a folder called ProcessBlog. There is no folder .Processblog.

I have show hidden files on.

I already changed the entries in the input tab. The format is changeing. But the month stays in english.

Link to comment
Share on other sites

@congomonster, thanks for catching that. Fixed; in dev branch for now. 


Please note that if you want the method MarkupBlog::formatDate() to output your comments date according to the date field in blog_comments, you just need to pass it a second parameter 2 (integer 2). For instance, in the template file 'blog-recent-comments.php', line #30, we had this:

$date = $blog->formatDate($comment->created); 

...but we now have this:

$date = $blog->formatDate($comment->created, 2); 

Since the second parameter is give a value of 1 by default, this change should be backward compatible. Unless you want the updated feature, you don't need to do anything in your template files.

Edited by kongondo
  • Like 2
Link to comment
Share on other sites

Hi kongondo,

I tried out your huge module and I think would like it, but it doesn't work properly (using PW 3.0.7). I will give you a small bug list.

  1. clicking on Posts results in Error: Call to a member function count() on null (line 1355 of .../site/modules/ProcessBlog/ProcessBlog.module.
    Problem: field blog_files isn't assigned to the blog-post template by default which is the reason for the error above.
    After removing line 1355 the modal for posts doesn't appear after clicking, linked page opened instead
  2. The dropdown function of the tabs in Admin are disabled if blog tab is active
  3. cannot open Settings -> Settings -> Edit
  4. cannot open Tags -> New -> Tags Add
  5. cannot open Categories -> New Categories -> Add
  6. cannot open Posts -> Quick Post -> Add
  7. cannot open Edit Posts -> Actions
  8. Dead link (404) in Module description on processwire.com http://kongondo.com/tutorials/specific-features/creating-a-blog-in-processwire/
    (just realized in the topic of this thread a temporarily link to the tutorial)

A personal wish: Dashboard -> Archives -> month clickable with link to a list of selected items

Link to comment
Share on other sites

Hi @kixe I know @kongondo or others will probably be better able to help you but I just wanted to say that the good news is that:

I think would like it, but it doesn't work properly
is incorrect as far as my experience goes—I just installed it on a fresh PW v2.7.3 and it worked perfectly, no errors.
To begin to help, perhaps, check you have debug turned on in config.php `$config->debug = true;`, then there is this post.
Sorry if you have already done this and good luck; it's worth it, the @kongondo's Module(s) for the blog make a very professional, complete solution. I was greatly impressed when I tried it.
  • Like 1
Link to comment
Share on other sites


Thanks for pointing these out in advance. I am not being naughty but as you can tell from here, Blog is only compatible with ProcessWire 2.4 - 2.7 :P  :-). I have been so busy I haven't even had a chance to install, let alone play with ProcessWire 3.X. 

So for now, I am not able to support Blog for that version of ProcessWire, but I do appreciate people catching such bugs in advance (although, PW 3.X is still an evolving beast) :-)

Edited by kongondo
Link to comment
Share on other sites

Thanks for the quick answer. I am pretty sure your module works proper in 2.7. I am involved in 2 projects both based on 3.0 probably going online in summer. I updated already most of my stuff for 3.0. Ryan is working very very quick and I am pretty sure we will have a stable Version of 3.0 very soon.

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...