Jump to content

Module: Blog


Recommended Posts

We are talking about two different things here then. You said templates (blog-post) but it seems you mean template files (blog-post.php)? What do you mean by layout? Do you mean the HTML markup or the layout of fields in the template? If HTML, Blog will not get in your way. You can use whatever template file you like but you need to associate your blog posts with the template blog-post. I don't know how much you've read up on the separation of these two concepts but you can have your posts use the template blog-post with a totally differently named template file or none at all. In a nutshell, Blog doesn't care about template files - just the templates. Btw, a couple of posts up I have provided a Gist of the method renderPosts() whose markup you can modify to suit your needs (if you are referring to the markup renderPosts() generates) and use that instead of Blog's renderPosts(). That will not stop you from using Blog's other methods, e.g. renderTags().

Link to comment
Share on other sites

@Peter Knight I can confirm that Kongondo's example gist works no problem. Can easily add mark up to the necessary parts of the function. In my case I've added divs to suit bootstrap. No problem. And if you wanted to create separate markup for a single post you could either do it with a separate function or with a conditional statement within the renderPosts() function.

  • Like 2
Link to comment
Share on other sites

Peter, I've added a lot of custom fields to my blog-post template, so my template file for the blog post itself is going to have a lot of calls to the fields listed for the template so that I can't rely on the module to output everything I want in the way that I want. It should be totally possible, and the module has a lot of other features that make it worth my while (multiple authors, the dashboard, etc). Unless you're stripping even more off the blog than just the template output for the individual posts, I think I'd stick with using it. My 2¢!

  • Like 2
Link to comment
Share on other sites

@kongondo is the total blog-post count for the user stored anywhere?

I'm trying to list my authors (in a custom admin page) in order of post count (greatest to least). Anything you can think of that would do it? Thanks again!

I see "$authorPublishedCnt = count(wire('pages')->find("template=blog-post, created_users_id={$author->id}"));" in ProcessBlog.module line 1840, which seems about what I'm looking for... though I'd like to subtract unpublished posts (which I can do with math in a later line if necessary). Is there a way for me to access created_users_id in admin? I tried that and createdUser but they both threw errors.

I love how typing out a question to you almost always helps me think through it. Sometimes I'm lucky enough to be inspired to try something before I post the question. Other times, not so much.

So the call I ended up using was:

$points = count(wire('pages')->find("template=blog-post, created_users_id=$mobster->id"));

The trouble I was having was that I was comparing the user id to the page name. Doink!

Edited by creativejay
Link to comment
Share on other sites

Cool. But that will just show the number of posts they have but not (necessarily) sorted according to their individual posts count. For that you would need something like this...

$posts = $pages->find("template=blog-post, sort=created_users_id.count");//you might want to limit results depending on use case

//test it....it should output the list in DESC order...
foreach ($posts as $post) {

  echo $post->createdUser->title . ' - ' . $post->title . '<br>';

Count selectors – finding matches by quantity


  • Like 1
Link to comment
Share on other sites

Hey, look at that! I stepped away before tackling the sort order and you did the work for me!

I have to add some posts for the other users to test this, since for now post count order is the same as the default. I'll report back in a few minutes. Just wanted to say my thanks!

Link to comment
Share on other sites

Okay, I see your query was looking at blog-post, so the created_users_id.count applies to the field created_users_id which is part of a blog-post page.

What I'm actually looking to do is sort the user list by the total (published) posts attributed to the user.. so I need to build that attribution somehow (before the query).

What would you do? My brain keeps telling me I should create a new field for template user called user_post_count, and write a hook for each post save that would assign the value of created_users_id.count to that field. Is that too convoluted?

Link to comment
Share on other sites

That's exactly what that code does :-). Did you try it? Or am I missing something here? What do you want your list to show? Authors only? Or authors + their count of posts? e.g. John - 35, Mary 23, Simpson 5?

Edited by kongondo
Link to comment
Share on other sites

It didn't quite work as-is. The list it output was the top user and the title of a post, one line for each post. Then it sorted the next user's single post.

So it did sort correctly, but it didn't display the number of posts for that user and I only wanted one result per user.

So I attempted to use the sort filter but of course since I was still searching users, not posts, it wouldn't work.

In the screen below you see the table with the correct information but the wrong order. Beneath that is the order and information from your code.


Link to comment
Share on other sites

I see. The following should do it. It could probably be made simpler but can't think straight this late hour :D

//find blog authors
$authors = $users->find('roles=blog-author|superuser, sort=title');
//array to hold author TITLES and their posts' count
$authorsList = array();

foreach ($authors as $author) {
    //count number of posts by this author
    $authorPublishedCnt = count($pages->find("template=blog-post, created_users_id={$author->id}"));

    //we assume no two authors with identical TITLES, otherwise older will be overwritten
    //author title is $key and their post count $value
    $authorsList[$author->title] = $authorPublishedCnt;


//sort the associative array $authorsList by posts count ($value), DESC

//rest of your code here to loop through the sorted array above
Link to comment
Share on other sites

You have the author title in the array keys...But you have to first make sure that you have entered the 'titles' of your authors in their user pages, i.e. the 'Display name (first and last name) field that Blog adds to user pages otherwise the array keys will be empty :-). Again, we are using their 'titles' not their 'names'. However, if you want to use their names instead, just modify the code above like so...(but I prefer title :-))

//find blog authors
$authors = $users->find('roles=blog-author|superuser, sort=title');//sort doesn't matter here, so can remove
//array to hold author NAMES and their posts' count
$authorsList = array();

foreach ($authors as $author) {
    //count number of posts by this author
    $authorPublishedCnt = count($pages->find("template=blog-post, created_users_id={$author->id}"));

    //we assume no two authors with identical NAMES, otherwise older will be overwritten
    //author NAME is $key and their post count $value
    $authorsList[$author->name] = $authorPublishedCnt;


//sort the associative array $authorsList by posts count ($value), DESC

//output the author list and post counts
foreach ($authorsList as $key => $value) {
    #this is just for testing. Use your own markup of course
    echo 'Author Title: ' . $key . ' - Author Post Count: ' . $value . '<br>';
  • Like 2
Link to comment
Share on other sites

Thank you kongondo! As usual I can go to sleep trusting that the ProcessBlog Fairy will leave working PHP code underneath my pillow...

This seems to be the line that made the difference "foreach ($authorsList as $key => $value) {"

Got that working now! I'm sure I'll be back with something else soon! ;) Thanks again!

Link to comment
Share on other sites

Great Module! Thanks!

I miss one litte functionality - display related posts (or did I miss something?).

Maybe someone else needs this, so here is the code (I use this in a TemplateDataProvider):

  public function populate() {
    $limit = 3;
    $selector = array(
      'template' => 'template=blog-post',
      'id' => 'id!=' . $this->post->id,
      'categories' => 'blog_categories=' . $this->post->blog_categories,
      'tags' => 'blog_tags=' . $this->post->blog_tags

    // find posts same tag AND category
    $related = wire('pages')->find(implode(', ', $selector));

    if ($related->getTotal() < $limit) {
      // find posts same category
      $related = $this->getRelated($related, $selector, 'tags');

      if ($related->getTotal() < $limit) {
        // find posts same tag
        $related = $this->getRelated($related, $selector, 'categories');

    $this->related = $related;

  private function getRelated($related, $selector, $remove) {
    $selector['id'] .= '|' . (string)$related;
    $rel = wire('pages')->find(implode(', ', $selector));

    return $related->import($rel);

  • Like 5
Link to comment
Share on other sites

Regarding "related posts", I also think that it's a pretty important for any blog out there. As a blogger you want readers to stay as long as possible and visit as many posts as possible. A feed of related posts is a great way to achieve that.

Not sure if it's still up-to-date, but I've used this Gist by Soma in some projects a while ago, mainly for the scoring part :)

  • Like 2
Link to comment
Share on other sites

I just noticed that a superuser who created 9 pages that are unpublished OUTSIDE of the blog in the tree has a listing of 9 pages as pending in the Blog / Author dashboard. Not sure why, as the module seems to limit it to the blog-post template. I thought I'd mention it.

Well that's just plain impossible unless you changed something :D. Just to be sure, I've just tested it...

  • Like 1
Link to comment
Share on other sites

Regarding "related posts", I also think that it's a pretty important for any blog out there. As a blogger you want readers to stay as long as possible and visit as many posts as possible. A feed of related posts is a great way to achieve that.

Not sure if it's still up-to-date, but I've used this Gist by Soma in some projects a while ago, mainly for the scoring part :)

Thanks for reminding me about this one (I actually forked it a long time ago and forgot about it!! Never thought to use it). Interesting approach Soma uses  - raw MySQL (although I don't think I'll have to hook into anything if I adopt this). I'll compare it more closely to justb3a's plus any other ideas I might have and make a decision...

Link to comment
Share on other sites

Also wondering whether to define a 'related post' as only one that has this matching 'tag' AND this matching 'category' to the exclusion of also has either this matching 'tag' OR has this matching 'category'...Hmm, maybe let the dev decide...


Also wondering if can/should use or-groups here? Just my loud musings here in case I forget...ignore me :-)

Edited by kongondo
Link to comment
Share on other sites

Well that's just plain impossible unless you changed something :D. Just to be sure, I've just tested it...

I agree, I'm looking at line 1841 in my (untouched) ProcessBlog.module. I see no reason that pages with template 'form-builder', 'blog', 'blog-widgets', 'swmb_error', or 'admin' should show up in that list. However, when I add 'parent=/blog-posts/' to the filter, the pending count returns to 0.

I'm just the black child fluke-finder. ;)

Link to comment
Share on other sites

I'm searching back through this discussion and not finding if anyone ever came up with a solution that prevented blog-author from editing other users' posts (other than their own).

Was anything ever worked up or around to limit people to editing just their own content?

EDITED TO ADD: Okay, I found this which blocks the users from editing other people's content:


I'm getting there!

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