Jump to content

Module: Blog


Recommended Posts

Hi all....

Apologies...I think I am now several months behind in respect of all my modules...I am still swamped with other stuff. My "I'll get to this next week.." have come and gone. I'am desisting from uttering such words for now... :). I am hoping to get to things as soon as I can....This may take a while...


Thanks for using the module. About the main dashboard timing out, as you can see here (my bad) that has been on my to do list for a while. The other dashboards all have a limit (default = 10 if not set per user), hence don't time out (e.g. here....for Posts dashboard). For now, a quick solution for you would be to place a limit on that line...Of course that would mean it won't reflect a true count...but you could change the line as well to only display the latest posts. Eventually, I will address this more elegantly but unfortunately I don't have a firm time scale right now...


Thanks for reminding me about this..

Link to comment
Share on other sites

Hi  When installing ProcessBlog & MarkupBlog I selected the blogstyle 4 (add post as child of 'Home').   I rearranged my pages and now it should be blogstyle 1.  Add post is still as child of 'Home'!   How can I change the blogstyle from 4 to 1 ?


Apologies for the delay in getting back to you. The easiest way is to use the 'Cleanup Utility' to uninstall the Blog components (pages, fields, templates) and run the install wizard again (i.e. the second part of the install). Otherwise, you would have to fiddle with raw database values to change a whole lot of things. It can be done, but you need to know what you are doing.

Thanks for using Blog.. :)  

Any plans to add gravatar or avatar to comments and if not, am looking to implement one for my website, you don't mind pull-requests ?

Apologies for the delay in getting back to you. Blog utilises the (core) Comments Module that ships with PW. You'd have to direct this request to Ryan.

Link to comment
Share on other sites

I belie


Thanks for using the module. About the main dashboard timing out, as you can see here (my bad) that has been on my to do list for a while. The other dashboards all have a limit (default = 10 if not set per user), hence don't time out (e.g. here....for Posts dashboard). For now, a quick solution for you would be to place a limit on that line...Of course that would mean it won't reflect a true count...but you could change the line as well to only display the latest posts. Eventually, I will address this more elegantly but unfortunately I don't have a firm time scale right now...

Unfortunately he already tried that based on my suggestion here: https://processwire.com/talk/topic/10609-processwire-site-header-and-footer-used-in-wordpress-blog/?p=100209

Are there any other places I have missed where adding a limit might help?

Link to comment
Share on other sites

I have enabled tags for blog_images field to use the featured image feature, but the tags are not saving. What could be the reason for tags not saving? I am using the latest dev version 2.6.4.

Are referring to the tags of an image field? If so, this is a question for Ryan really since it is outside the Blog Module's control. If you are still experiencing this problem, please file your question in the general support forum or if you've confirmed it is a bug, in GitHub (PW-dev).

Link to comment
Share on other sites

Unfortunately he already tried that based on my suggestion here: https://processwire.com/talk/topic/10609-processwire-site-header-and-footer-used-in-wordpress-blog/?p=100209

Are there any other places I have missed where adding a limit might help?

Ah, I missed that. Lines #818 and #821 also need limits (or some other filter)....(sloppy coding!!! Will optimise all three [eventually]....)....

Link to comment
Share on other sites

Ah, I missed that. Lines #818 and #821 also need limits (or some other filter)....(sloppy coding!!! Will optimise all three [eventually]....)....

I saw those two, but figured that since they are $pages->count() calls they wouldn't be a problem as they are not loading those page into memory - right ?

Oops, they are count($pages....), rather than $pages->count(). Maybe that simple change would make a big difference.

  • Like 1
Link to comment
Share on other sites

@ kongondo @adrian - Unfortunately, even adding the limit=10 to all three areas, still loads very slowly. What I don't get is why /admin/blog/posts/ loads so fast and displays all post quickly? Also an FYI, i have 420 posts at the moment. 

Link to comment
Share on other sites

Yeah, will revisit this when I can find some time...For now, alternatively, you can skip the dashboard by making it redirect to posts....(so posts dashboard will be the landing page...)

This at the top of the function blogDashboard should do it (i.e., insert as line #799):

$this->session->redirect(wire('page')->url . "posts/");//redirect to posts dashboard
Edited by kongondo
added code
Link to comment
Share on other sites

@Kongondo -  Okay, cool. I will have to use this for now. I don't think the rest of the module is broken or anything. I think just the loading of the dashboard is buggy. Unless you think I shouldn't run the module on a site that is going to grow at 3-4 posts per week?

Link to comment
Share on other sites


Found a bit of time to work on this. The Authors' Dashboard was also relatively slow. Worked on that as well. Using a combination of $pages->count() (thanks @adrian) and raw SQL queries (as explained here) and testing using 10,011 posts, the main Dashboard loads in 0.3 seconds on my machine. I think that's an acceptable time :) (given the 10+ seconds it took me to load main Dashboard with 5K posts). Although I tested with a minimal comments count, I don't think this will make much difference where there's lots of comments (using SQL for the counts). I will also look at Categories and Tags (in cases where these could run into thousands) just to be sure. Posts Dashboard loads fast as usual. Unfortunately, I still don't have time to merge the new changes any time soon.


  • Like 2
Link to comment
Share on other sites


I have some trouble with the blog-author role. 

 I have also an editor role which can edit and add the pages. 


       - editor-role


but only superuser can edit the Pages. How I can handle this problem ? 


The module only creates the role 'blog-author'. You have to assign the right permissions to that role yourself (when editing the role itself) and check and edit the respective blog templates' access controls (i.e. the 'what roles can access the pages using this template' setting in a template's access tab).

Link to comment
Share on other sites

Good afternoon, fellas,

sooo I installed the blog module, and it works totally fine, kicking ass and everything, I love it.

I'm currently working on a site which is not a blog, but has a blog- subpage, which I got rolling. But what happens, or more like what do I do, if I want a second Subpage on my site which uses the blog - functionality? is there a way to achieve this?

consider the following page tree:


stuff -> regular  content

stuff2-> Blog 1

stuff3 -> Blog 2


.. and so on.

so basically I would want two subpages on my site on which I would be able to publish blog posts independent from each other, which (in my opinion) would mean that I could tell the blog module at a certain point to publish a post on either one of these two pages.

Help would be much appreciated.

Best regards, 



so I kinda had an idea for an approach to a solution to my problem, my thought was, that I could use two templates, which output blog posts by category, so basically I'm looking for a function which outputs posts with category "blog1" on the first page and in a second php script, one that outputs posts with category "blog2" on a separate page.

so far though, I couldn't find anything about that in the documentation, I only found output filtered by post author, does the same apply to post category?

//edit 2: I managed to do that, just had to change a few lines in one of the php files. Finally, everything works, and I have to admit, I am totally impressed. this module kicks ass in any way imaginable. Thank you so much Kongondo.

Greetings from Germany,



Glad you got it sorted. As you noticed, what you wanted was not available right out the box. 

Link to comment
Share on other sites

  • 2 weeks later...

Hi Guys,

I was wondering whether there is an option to change the language of the publishing date of each post and also the archives from English to German.

So far though, I was unable to find a solution to this. Is this possible?

To elaborate: I want individual posts and the archive to say :



rather than



I tried changing the locale in my header.inc but that didn't help. So is there a way to achieve this?

Greetings from Germany


Link to comment
Share on other sites

So back again,

get some sparetime to contribute to this one.

It's a real beast now with many strings to translate....and i added a few one, too..... ;)


But here we are.

Complete DE translation for the actual Blog version 2.3.4 (and it's comming pullrequests with additional strings for archive, and pages).

+ Translated SchedulePages module to use both combined.

Important Notice on the main translation thing with the blogmodule:

- Some Strings are taken from the pagetitels of the autogenerated pages for eg. "cathegories" or "archive" so please use the installation step with renaming the parents correct or rename the titels later.....but not the names... ;)

- CleanUp Ultility is not complete translated because it's only a superuser thing wich should be used with care and knowlegde so don't see a real effort to translate this rarely used function...

-Some Strings are not translateable since the where automatic generated on templates and fields so please translate these, too - if needed...

Have fun - Thanks again to kongondo

So take a look at the generated template labels and field labels...to get everthing translated.

I've you have some special things that are not work please give the exact explanation where the phrase is located may put a screenshot in the post....for me i've all translated in german lang...so feel free to ask.

But i need the exact place where i've to look...since i'll glad to help you but at the other side i am lazy, too :P

Link to comment
Share on other sites

Hi Guys,

I've just deployed my first site built with the Blog Module and on the surface all is well. However, when ProCache is turned off, the blog summary page loads awfully slowly despite there only being ten or so short blog summaries displayed (at this moment in time). It would be unacceptable performance if it weren't for ProCache.

I looked into what the bottleneck was and the Blog pages are being returned by ProcessWire in an instant so, it's not data retrieval. When I stepped into the MarkupBlog.module, renderPosts method with small set true, around line #746 there is the following line:

$summary = strip_tags(substr($page->blog_body, 0, $summaryLimit), $options['post_small_allowable_tags']);

With summary limit set at 450, I noticed that the PHP strip_tags() function takes an absolute age to run! As far as I can see, this is the line of code that creates the bottleneck I am seeing without ProCache.

Has anyone else come up against this as a performance bottleneck?

Look forward to hearing from you.

Cheers and thanks! :)

Link to comment
Share on other sites


Must be at your end mate. I haven't encountered this nor read anywhere that strip_tags is slow. As you can see in this demo with +10K posts, showing 20 posts per summary page with a summary limit of around 500 words each and WITHOUT ProCache, PW loads the page in about 2 seconds..


And with shorter summaries: http://demo.kongondo.com/blog/posts/

  • Like 1
Link to comment
Share on other sites


Many thanks for looking into this! So, I looked at my blog_body field's text formatters. I had three specified in the following order:

Hanna Code Text Formatter


Profield: Autolinks <-- This guy hurts!

When I removed "Profield: Autolinks", the whole page load speeded up to something like I would have expected to see. So, the culprit here is Autolinks -- go figure? I wouldn't have expected that but with Autolinks, it takes an absolute age for the $page->blog_body to be rendered before it is passed into the strip_tags() function.

I guess you don't notice this when rendering a single page but when on a tight'ish loop, you clearly see the performance hit caused by Autolinks. Wow.


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