Jump to content

Module: Blog


Recommended Posts

Hmm it must be something to do with the newer comments module for sure.

I should have stated earlier that i am also running pw 2.5.10 dev branch.

I tried backing up to an earlier installation and reinstalling with the same 2 issues with the tables field_blog_comments and field_blog_comments_votes

Link to comment
Share on other sites

Thanks Alex for catching this.

I can confirm this behaviour only happens in the dev branch since the addition of the updated FieldtypeComments. Ryan managed to break something :-). Hey, the new fieldtype is still under development. I will bring this to Ryan's attention.

Meanwhile, a workaround that I have tested is to first install the stable branch PW, install Blog, upgrade PW to dev branch. Works fine.

FYI the message logs for dev branch (unsuccessful upgrade of blog_comments)

2015-01-06 18:07:29	lightning_admin	http://curium-kcu.lightningpw.com/processwire/blog/	Updating schema version of 'blog_comments' from  to 4
2015-01-06 18:11:06	lightning_admin	http://curium-kcu.lightningpw.com/processwire/blog/	Updating schema version of 'blog_comments' from  to 4
2015-01-06 18:17:05	lightning_admin	http://curium-kcu.lightningpw.com/processwire/blog/	Updating schema version of 'blog_comments' from  to 4

Compare that to a successful one..

2014-11-30 01:51:37	kongondo	http://localhost/pb/pb/blog/	Updated schema version of 'blog_comments' to support website field.
2014-11-30 01:51:37	kongondo	http://localhost/pb/pb/blog/	Updated schema version of 'blog_comments' to support website field.
2014-11-30 01:51:37	kongondo	page?	Updated schema version of 'blog_comments' to support website field.
2014-11-30 01:51:37	kongondo	page?	Updated schema version of 'blog_comments' to support website field.
2014-11-30 01:54:34	kongondo	http://localhost/pb/pb/blog/	Updated schema version of 'blog_comments' to support website field.
2014-11-30 01:54:34	kongondo	http://localhost/pb/pb/blog/	Updated schema version of 'blog_comments' to support website field.
2014-11-30 01:54:34	kongondo	page?	Updated schema version of 'blog_comments' to support website field.
2014-11-30 01:54:34	kongondo	page?	Updated schema version of 'blog_comments' to support website field.
2015-01-06 17:46:32	kongondo	http://localhost/pb/pb/blog/	Updating schema version of 'blog_comments' from 1 to 5 (FieldtypeComments)
  • Like 3
Link to comment
Share on other sites

Awesome! Nice one man! You are a bloody marvellous chap. Some might say a gentleman and a scholar... I most certainly would say so!

I shall follow your process process down to the wire.

  • Like 3
Link to comment
Share on other sites

  • 2 weeks later...

Update: Blog version 2.3.1


Thanks to @matulkum, fixed this bug (thanks @bwakad) where...unparsed HTML would be output in Blog Posts/Categories/Tags Dashboards in multilingual ProcessWire environments. 


As per https://processwire.com/talk/topic/7403-module-blog/?p=83971. Thanks to @Gazley, added 'post_small_tag' option to renderPosts(). Enables developer to select HTML tag to wrap around a 'small' Blog Post, i.e. a post excerpt/summary. Value should be left blank if no tag is desired. Especially useful if using the option 'post_small_allowable_tags'. The default tag is '<p>'. Use option as:

//$options = array('post_small_tag' => 'div');//note we enter the tag only without the angle brackets!
//render a limited number of summarised posts
$content .= $blog->renderPosts("limit=5", true, $options); 


Thanks to @loopyloo, added MarkupBlog frontend demo screenshot to README. See post #304-312 for why...

  • Like 2
Link to comment
Share on other sites

Option 2.

Add your custom fields to the template 'blog-post' and use the module 'Page Edit Field Permission' to hide your custom fields as relevant to your Posts types A - D. In your template files, you will need to echo your custom fields separately from renderPosts(). I think I would go for this option since it requires the least work and you only have 1 template to deal with..In your template file you would only echo out your custom fields if they were not empty.

Finally getting back to this project, and I see you tested this with a lot of success. I think I will give this a go. I promise to report back.

I'm also very excited to see the other features you've added since I last sat down to play around with the blog module, because you've taken care of so many things that were going to be a bother in my case. Thanks again!

Link to comment
Share on other sites

Hi hi hi,

Quick question which will either be a yes or no and if it's a yes hopefully it will be quite simple for someone to answer...

I'm aware that styling is easiest by just using CSS, however I am using bootstrap so would love to be able to change the markup if that is at all possible. Haven't seemed to have found anything to say there is an easy way of doing this. It's just that based on my design I need to have a div class="container" within div class="post" for each post.

Otherwise I am going to have to do a whole load of mixins and stuff.

This isn't to detract from the module as it is the tits. Just a question to hopefully make my life easier.

Thanks in advance.

Link to comment
Share on other sites

Not sure I get what you mean by

.... I need to have a div class="container" within div class="post" for each post..

Do you mean this

<div class='post container'>My post</div>

Or this?

<div class='post'>
  <div class='container'>My post</div>

Both can be achieved by using jQuery if you don't mind manipulating the DOM using js.

If the former (add a class using jQuery .addClass())


If the latter (add an inner wrapper using jQuery .wrapInner())

$("div.post").wrapInner("<div class='container'></div>");
Link to comment
Share on other sites

Thanks for the super speedy reply Kongondo! Very grateful as ever.

Ok, so currently there isn't a away to add or adjust the markup elements via the options array?

Hmm... I have this issue in my head with doing it with javascript because of the extra bloat etc. But then I guess it really isn't adding that much and the rest of the site relies on javascript to run so this wouldn't be too much of a bad thing using it for this purpose as other things would break too.

Link to comment
Share on other sites

No, you can't adjust that markup via options.

There's other ways of doing it on the PHP side though, making it more foolproof than doing it client-side.

  1. See option #3 in this post (writing your own code to render posts): https://processwire.com/talk/topic/7403-module-blog/?p=83119
  2. Maybe using str_replace: See this post by DaveP: https://processwire.com/talk/topic/7403-module-blog/?p=78348
  3. Copy and modify the method renderPosts() into your own function which you can include in your template files

Using #3 above, you can continue using the rest of  MarkupBlog methods such as renderCategories() together with your own modified renderPosts(). If this doesn't make sense just ask :-)

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

I think #3 sounds best.

So effectively I guess I can just copy it to my global _func.php file and then drop the $this instance and I should be good to add to the markup?

Also one other thing I have been trying to get the featured image of renderPosts() to show but cant seem to figure it.

Have enabled tags in blog_image field and left the featured options as default. Have tried adding the tag featured to the image I want as featured but it is not showing.

Sorry for all of these questions. I'm having a bit of a moment these last few days.

Link to comment
Share on other sites

Pretty much, but with a few additions as well. I have created a Gist of the renderPosts() function here:
In the demo blog-post.php and blog-posts.php you could use it as shown below (assumes you've already included the function)

//assumes function renderPosts() already included in page
$content .= renderPosts("limit=5", true, $options);//using our function above//blog-posts

$content = renderPosts($page, '', $options) . $blog->postAuthor() . $blog->renderComments($page->blog_comments) . $blog->renderNextPrevPosts($page);//blog-post

For featured image, the default is off (0) :-). So, you need to add an $options array with values for featured image 1 or 2 for the type(s) of post where you want a featured image (i.e. small or large). Below are the defaults:

//display post's featured image: 0=off,1=top(above post-headline),2=bottom(first item in post-body)')
$options = array('post_small_image' => 0, 'post_large_image' => 0);//these are the defaults -> off (zero)

Btw, note that for large posts you cannot use an embedded image as the featured image. You will need to designate a featured image. For small posts, both embedded and images tagged 'featured' will be picked up as featured images.

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

I'm thinking of using this. Can anyone suggest a fairly representative and recent blog site based on it which I can show my client?

I realize the best answer is probably to spin up a new site but something real might make more sense to them.


Link to comment
Share on other sites

@Kongondo thanks for all of this! I will take a look into it and stop nagging you now!

@SteveB I'll have something up very shortly so will update when it is there. In the meantime, no doubt someone else will point you towards some examples when they see your post. I'll be working on the blog the next day or 2 though.

Link to comment
Share on other sites


Did you try my option 2 suggestion above? I tried it and it works brilliantly (tested on lightning.pw so can give you access before the test site expires) .

Sorry I didn't see this at the time to play in the example you built. I'd love to know more about how you set this up, if it's not too much trouble.

Link to comment
Share on other sites

It really is straightforward if you follow the the module 'Page Edit Field Permission' instructions :-)

  1. Create all your extra fields for your Categories A - D
  2. Add those fields to the template 'blog-post'
  3. Create 3 roles . I say three since as per your description Category B and D seem to have the same fields? If not, create 4 roles and give them distinct names
  4. Install the module 'Page Edit Field Permission'. Make sure to read its instructions.
  5. In its configuration screen use the 'Handy Tool....' to create permissions for all your 'blog-post' fields that you want to limit access to. For instance, if you want all your users with the roles Categories A -D to be able to view the 'title' field, then there is no need to create a permission for it. 
  6. The module will create permissions prefixed with 'page-edit-', e.g. if you ticked 'blog_body' as one of the fields in that screen, a permission 'page-edit-blog_body' will be created.
  7. Edit each of the roles you created in #3 and check the relevant permissions allowed for those roles. (i.e. give the roles access to edit selected blog fields).
  8. Edit and assign your users the different roles your created in #3. You can test with some dummy users, e.g. Jane, Samra, Onuko, Shah to represent your four Categories/Roles. Also give them the role 'blog-author' (needed by Blog).
  9. Edit the template 'blog-post'. In the Access tab, you should see the four roles created in #3. If they will all have 'view pages', 'edit pages', 'create-pages' and 'add children' privileges, then rather than granting these to each role, just assign the four privileges to the role 'blog-author' in that same screen. This is a template level access you are granting.
  10. Try logging in as each of your four dummy users. Edit a blog post. You will notice some fields are hidden depending on the role that user was assigned. Logging in as a superuser enables you to see all fields.

That's it really... O0

  • Like 1
Link to comment
Share on other sites

So are you saying you will have four fixed categories? A - D? And each of your posts will belong to only one of those categories? If yes to all, then the easiest way (but maybe confusing) is to create your 4 categories, create your extra fields and add them all to the 'blog-post' template. Then, when rendering posts, pass a PageArray filtered according to your categories to renderPosts() to display. The problem with this approach is that you may end up with lots of fields some of which will be empty depending on the post category and this may confuse your editors. I am not sure if they could be hidden using PW show/if/dependency. I can't think of any other ideas atm. Otherwise, you might have to modify MarkupBlog to suit your needs.

Link to comment
Share on other sites

Thanks a bunch Kongondo! I added the extra fields for field type A to a second tab, because I didn't want to distract from the category select field - I was afraid folks would miss that if I didn't put it right at the top! I think I can keep it to two group types.

Now back to modifying the output with custom templates. Kongondo, thanks as always for the quick support. You're a star!

Link to comment
Share on other sites


In that case ProcessBlog wouldn't work. It has to find 'blog posts' by the template 'blog-post' rather than their parent because depending on the blog style you selected, the parent might not be a blog page. E.g. In blog style 4, the parent is the root page. The only way to differentiate blog posts in that scenario is by their template.

What did you have in mind?

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