Jump to content

Module: Blog


Recommended Posts

In that case there is something else wrong with your setup. It is difficult to tell without seeing/testing on the actual site Any other changes you have made to your template files? Some other modules possibly interfering? What about testing comments + form apart outside of the Blog (non-blog pages)?

Link to comment
Share on other sites

My template files are very different from the default. ;) I haven't touched the module itself, though. I'd be happy to give you access to my admin if you have the time to take a look. I can post any templates here that you think may be causing the issues.

Form Builder works outside of the blog pages. I don't have comments for non-blog pages, though.

Link to comment
Share on other sites

I got another little issue. If someone uses the quickpost function and fills out quickpost_body all line breaks will be removed.

I don't think that is it necessary to use a rich text area here but maybe you can wrap it in a simple nl2br function?

        //@todo - SHOULD THIS BE A RICH TEXT AREA?
-       $p->blog_body = $this->sanitizer->textarea($this->input->post->quickpost_body);
+       $p->blog_body = nl2br($this->sanitizer->textarea($this->input->post->quickpost_body
  • Like 1
Link to comment
Share on other sites

Yeah, this has been brought up before but wasn't really sure how to deal with it. Thanks for reminding me :-).

For now, I have decided to convert and store the line breaks in 'quickpost' to paragraphs (instead of <br>) since I believe that is the intended action by the user when they use a line break in 'quickpost' to space out their text. Besides, that is what CKEditor is going to do when the full post is edited. Using nl2br will result in lots of <br> all of which CKEditor will wrap in one paragraph. But thanks to your idea, I am now using a pre_replace to do the job. It works fine.

Committed to dev for now.

  • Like 1
Link to comment
Share on other sites

For the Categories / Tags and other Page-type fields, the parent of those pages gives blog-author the right to Add Children, and the field has "Allow new pages to be created from field" checked. Anything else I need to check for? I'm able to create new pages as a superuser but my blog-author role users get a little achtung triangle in the AsmSelect field when they type, and nothing is saved. In Select cases, there's no option to add another for blog-author roles. What I glean from this is that there's another permissions setting somewhere, other than the per-template "Add Children" setting for blog-author.

I already started this over once in a new install and ran into the same comments issue before I got very far (managed to reverse the problem by restoring the default templates, so the problem is either with my call to the comments form, or some other module that I call in my template files).

Edited by creativejay
Link to comment
Share on other sites

Then the problem is in your blog-tag and blog-category templates. You have two choices:

  1. Set up access to the pages using these templates, i.e. an individual 'tag' and 'category' respectively by setting up access in their respective parents' templates, i.e. 'blog-tags' and 'blog-categories' AND making sure the two child templates 'blog-tag' and 'blog-category' have No checked for their respective 'manage view and edit access for pages using this template?' setting. In that case, pages using 'blog-tag' and 'blog-category' will inherit their parents' access. Then, in 'blog-tags' and 'blog-categories' you will need to check for the role 'blog-author' View Pages, Edit Pages, Create Pages and Add Children. Alternatively:
  2. Set up access on the child templates themselves, i.e. in 'blog-tag' and 'blog-category' templates. In this case, in their parents' templates, 'blog-tags' and 'blog-categories' you would only need to add the access Add Children. In 'blog-tag' and 'blog-category' you would need to grant access to View Pages, Edit Pages and Create Pages

If the above don't work, there could be some access inheritance issues going on...Access issues are of course controlled by ProcessWire itself and not Blog :-)

Link to comment
Share on other sites

Thanks Kongondo, that confirms what I'd been doing was correct.

I got clarification from the blog-author role user that spotted the problem with creating new pages from fields: she had never been able to do this.  On a hunch I disabled PagesCreatedEdit and sure enough that allowed the user to create their new tags, categories, etc. Unfortunately now blog-author can edit blog posts other than their own created posts. I may make a custom Module based on PagesCreatedEdit to try and make a special exception to the rule for certain templates.

Link to comment
Share on other sites

Hey Kongondo,

I noticed that when I first installed Blog, probably about 4 months ago, the module was called in my templates as

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

And now $blogOut seems to be $blog in your more recent documentation. Is there something in the modules themselves that should compel me to go back to the default templates as a new starting point? (Yes, I'm still struggling with comments and I have narrowed it down to being caused by my template file code...)

Link to comment
Share on other sites


I am just getting started with PW. I've successfully installed but not yet confirgured the ProcessBlog module and would like to know before I delve further whether or not a single instance of the module can be used to deliver multiple blogs. What I have in mind for the website I am currently working on is both a separate News section and a separate Testimonials section.

Is it actually necessary to completely split the two sections/blogs in terms of the backend? If not, how should I go about setting this up? Can categories be set up to split the data for News and Testimonials? Effectively both pages could be built around the same underlying data structure, for example:

$post-date-time             ( - would like the date|time to appear as yyyymmdd - hh:mm:ss, though)
                                         - do I actually need this field or can this data be retrieved from a built-in PW source??




$post-category              ( - needed or not?)

In addition, what are the advantages / disadvantages of the different blog styles? Purely from the path name perspective it appears that Blog style 3: /mysite/posts/example-post/ might be the most appropriate.

Otherwise, would Joss's Simple News System be a better place to start?

Any guidance would be greatly appreciated. :)

Edited by kongondo
Moved to Blog's support forum
Link to comment
Share on other sites


Welcome to PW and the forums.

Multiple Blogs:

This issue has been raised a couple of times but I haven't yet resolved how to best implement such a feature:


Is it actually necessary to completely split the two sections/blogs in terms of the backend? If not, how should I go about setting this up? Can categories be set up to split the data for News and Testimonials?

At the moment it is not possible to have such a split. I am wondering whether this can be achieved by simply adding some field on a post's template to assign it to a particular field...hmm...
Change your date's input/output format in the field 'blog_date'
You can have a post summary by using renderPosts($posts, true) - see the Blog documentation. Alternatively, you can create your own summary field and use that.
Blog Styles

In addition, what are the advantages / disadvantages of the different blog styles?

Purely user preferences...
Link to comment
Share on other sites


I am sorry for the delay in replying, I thought I'd raised a new topic (Evidently not! :huh: ) and therefore wasn't looking in the right place for any replies.
Thank you for your very speedy reply and the links.

I had an issue with links between the pages which I appear now to have resolved using:

<a href="<?php echo $config->urls->root; ?>about"</a>

All of those below returned blank pages:

<a href="<?php echo $config->urls->templates; ?>about"</a>
<a href="/about"</a>
<a href="./about"</a>

I'll read through the links you have provided and see how I get on.

In the meantime I've tried working through the Simple News System guide so far without success.
I'm not sure if this is an issue related to the installation path of this instance of PW (in this instance while the site is under development: http://localhost:8888/rcl_pw252/ ) or the fact that I changed the name of the templates, fields and pages.
I'm pretty certain I've updated the news.php, news-index.php and inc/news-fnc.inc files have been updated correctly accordingly, but I still get blank pages being returned which might suggest that the inc/news-fnc.inc file needs to include paths in at least some instances as well.
Any thoughts would be appreciated.

Thanks again. :)

Link to comment
Share on other sites

  • 2 weeks later...

Hey kongondo, I finally fixed my comments! As usual, it was something completely innocuous: I had a base href tag in my header that was redirecting the #comments to the root URL of the site installation. Deleted that line, and suddenly my comments worked. :frantics:

I was taking a very methodical approach to figuring this out (finally sitting down tonight after weeks of not having time to focus), thankfully my method led to the answer in five steps.

Now that I can finally put in some example comments to play with:

1) If I wanted to notify the admin listed in the blog_comments/Details tab, PLUS the author of the post that received a comment, what would you suggest? I don't want to add every author to the list of those who receive comments as a global setting.

2) I have a custom admin tab that is the admin home of all authors. I'd like to identify any pending comments they should review and output a message such as "You have # comments pending review. Please visit the Comments Manager."  Would you suggest I start with the code from  "public function findComments($selector)" in MarkupBlog.module (line 541 in the latest release version)?

Edited by creativejay
Link to comment
Share on other sites


Can anyone tell me whats wrong with my code here please. I am trying to blog page with images and small text. Small texts are ok but images showing only one. Any help, would be greatly appreciated.

//CALL THE MODULE - MarkupBlog
$blog = $modules->get("MarkupBlog");
$limit = 10;
$post = $pages->get('template=blog-post, sort=blog_date');
$image = $post->blog_images->first();

<div class="jumbotron">
    <h3><?php echo $page->title ?></h3>
<!-- /.Header_End -->
<div class="main-content container">
    <div class="row">

        <!-- Blog -->
        <div class="blog-list">
            <div class="row">
                <div class="col-md-6 post-list">

                    <div class="ih-item square effect9 right_to_left"><a href="#">

                            <div class="img img-responsive"><img src="<?php echo $image->url; ?>" alt="img"></div>
                            <div class="info">
                                <div class="info-back">



                <div class="col-md-6 post-list">
                    echo $blog->renderPosts("limit={$limit}", true);

            </div><!-- row_end-->
Link to comment
Share on other sites


Can anyone tell me whats wrong with my code here please. I am trying to blog page with images and small text. Small texts are ok but images showing only one. Any help, would be greatly appreciated.

$image = $post->blog_images->first();

On that line you are only calling one image....specifically the first one. If you want to output several images you would have to loop through them. Have a read here. something like

$out = '';
foreach($post->blog_images as $img) {

$out .= '<img src="' . $img->url . '" alt="img">';

//then output $out later on down...within your <div class="img".......

@creativejay...get back to you later.....

  • Like 1
Link to comment
Share on other sites

1) If I wanted to notify the admin listed in the blog_comments/Details tab, PLUS the author of the post that received a comment, what would you suggest? I don't want to add every author to the list of those who receive comments as a global setting.

2) I have a custom admin tab that is the admin home of all authors. I'd like to identify any pending comments they should review and output a message such as "You have # comments pending review. Please visit the Comments Manager."  Would you suggest I start with the code from  "public function findComments($selector)" in MarkupBlog.module (line 541 in the latest release version)?

Sorry for the delay.

#1: Am not sure how to do that. It is really a Comments Module question. Maybe Ryan could help there

#2: Yes  :-)

Seem you really have some cool setup there. Would like to see a screen if possible.



Link to comment
Share on other sites

Thanks! I'm trying to make the site as fun as possible (it's a non-income-generating pet project), to make it emotionally rewarding for the authors that have volunteered to provide content.

I'm attaching a screen shot of the post-login home page for an author (non-superuser). Fair warning, the color scheme may hurt the eyes. I'm going for quirky here.

The challenge area is the 'ticket' system I was referring to.


  • Like 2
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...