Jump to content

Module: Blog


Recommended Posts

About 10 pages. When you linked me to your demos, I immediately thought it must be Textile or Hanna but it wasn't. I was surprised to see Autolinks being the issue. Obviously, the other two will add some processing overhead but nothing like Autolinks in this particular circumstance.

Link to comment
Share on other sites

  • 3 weeks later...


I've just installed ProcessBlog on a test install of ProcessWire and all the admin side of things appears to work without issue, however when I try accessing any of the blog pages on the front-end all I get is a 404 not found error.

I've setup with blog style 2, and the blog pages and sub-pages all show OK in the admin page tree, and in the front-end sitemap, but viewing any of them just 404s.

Any ideas on how to what's happening and fix this?

The install was on a clean PW install (site-beginner)

Thanks in advance

Link to comment
Share on other sites

Hi again,

Only possible contributing factor is on completing installation I get a database error that says:

" SQLSTATE[42S02]: Base table or view not found: 1146 Table 'testbed_processw.field_blog_comments' doesn't exist"

Would this be the cause? How to rectify it, and why would it have occurred?


Link to comment
Share on other sites

Hi @roblgs and welcome to PW and the forums.

Did you also install the MarkupBlog module?

MarkupBlog is not necessary if you want to create your own posts.php and post.php template files, but it makes it much quicker and easier to get going and you can use those files as a starting point and style from there.

Link to comment
Share on other sites

Hi Adrian,

Not explicitly, it wasn't clear that was necessary to do so separately from ProcessBlog which said it included MarkupBlog.

If I check modules for 'Site' then I can see

Blog Post Publish Date

Markup Blog

as installed, along with process blog

If I click on either one of those names in the list I get a page showing details, an uninstall link and a submit button. Clicking submit produces a message that the module has been saved...

Blog front-end remains unreachable

Link to comment
Share on other sites

Hi roblgs,

Welcome to the forums and PW.

Apologies for not getting back to you sooner. Sorry for the 'bad' start with the Blog module.

  1. The SQL error you see is something that started happening a couple of PW versions ago. It is safe to ignore it; just reload the dashboard and it will go away
  2. Blog automatically installs both MarkupBlog and ProcessBlog, although you may uninstall the former just fine
  3. 404s usually mean something wrong with your setup (server). URLs not being found where they are expected to be. I really doubt it has anything to do with Blog per se, but we are still going to help you :-)
  • Do other ProcessWire pages work fine? (Home, About, etc?)
  • Is this a sub-domain?
  • Is your install somewhere we can view it? (i.e. not a local install)
  • Long shot, but try installing using the 'blank profile' 

Let us know how it goes.

Link to comment
Share on other sites

Hi Kongondo,

Thanks for getting back to me.

I think I have it sorted, though I took the sledgehammer approach and clean installed both PW and PB.

Previously there were no blog templates installed in /site/templates, they were all in /site/modules/ProcessBlog/template-files... this time around they are all in /site/templates and at least I now get pages when I try loading /blog and so on... i.e. no longer getting a 404.

Couple of questions... the blog templates all include blog-main.inc.

My current setup uses prepend and append files, so I'm guessing that to get it working well I'll have to create a blog-main.php as an append file, based on a merger of current _main.php and the blog-main.inc... that is if all pages are to work off a consistent model...

Initially the blog pages stacked everything vertically, but I've copied 'css' and 'js' folders from the module folder to /site/templates and its producing a more expected layout... except that it mixes the layouts/contents of blog-main.inc with that of the _init.php and _main.php currently being pre/appended, but I think that will be straightforward to clean up.

Still don't know exactly what happened previously, unless an install issue with folder permissions causing some things to not be placed where they should be. That's my current best guess, although there were no on-screen error messages to indicate that... I suspect that the /site folder and its children were not writable to the extent needed.

Anyway, atlas I have something now, which is a giant step forward from yesterday, and a base on which to learn more.



Link to comment
Share on other sites

Glad you got it sorted. The blog templates are all for demo purposes. So you can edit them as you please, or even not use them (only using their code as a reference if you are new to coding/PW...). The CSS and JS folders are intentionally not copied over...(as explained in the read me :-))..

Link to comment
Share on other sites


Unable to add name to user, or to upload an image to a user.

These fields are added by the blog, as they are not present before installing the blog.

Any ideas?

The fields are displayed in the profile edit form, but after I fill the 'name' field with a text value and submit, the field is empty on reload, and no error message.

When trying to upload an image there is a red area below the image name on submit, but no error message.

Link to comment
Share on other sites


I can add a name and an image when creating a new user, but cannot do so when trying to modify the primary admin account, even when logged in as the primary admin...


If I logout of primary admin, and login as a different admin, I can then add name and image to the primary... Seems there is an issue with doing so when trying to update yourself.

Link to comment
Share on other sites

  • 2 weeks later...

Hi there,

I've just added this module (MarkupBlog) and I can't seem to see the Cleanup utility as described by the install instructions.

I'm logged in as the admin user and my php debug level is set to 300.

I have not uninstalled the module prior and I've just posted a blank post, in case the Cleanup option shows after inserting the first post.

Is there anything else I should be checking?

Link to comment
Share on other sites

:) ....Not sure how to answer this :-)....The answer is right there in front of you....you haven't finished installing the module. It is a two-step process. What you are seing there is step two (with very clear info :P ). Complete that (there is an install wizard button) and you'll see everything there is to see. Please read the accompanying README in its entirety to get the most of this module. A copy is here in github

Edited by kongondo
Link to comment
Share on other sites

Hi Kongondo, 

I did actually finish the installation before trying to look for the "Cleanup Utility".

I believe this is the correct state it should be in after installation (I chose option 1)?


I think the documentation was leading me astray as it was referring to  "Cleanup Utility", "Cleanup Feature" and "Blog menu item called CleanUp", but there was no clear titles or labels that that actually included the word Cleanup in the pages I saw.

I guess it wasn't clear to me that the first initialisation page also doubled up as the cleanup utility that was referred to multiple times.

I think where it got me confused was after reading "Blog Menu Item called Cleanup".

So I see a menu item on called Blog on the admin screen.

And I was expecting to see a menu item called Cleanup as a submenu item like other different Admin menu items normally have.

Except it wasn't there as expected.

I did read the README multiple times to Cleanup the confusion I was having (pun intended)  and even searched for the word Cleanup on both wizard pages.

Imagine my distraught state when I couldn't do either  :P

Thanks for the prompt reply and building the extension. Can't wait to use it!

Link to comment
Share on other sites

Glad you got it sorted. Thanks for the feedback. I will look into the wording of the instructions. The first initialisation page is not the cleanup utility if by that you mean the first step of the install. Nor is the second step of the install the cleanup utility.. The cleanup feature is accessed via a sub-menu within the Blog itself (the Process Module)...

Link to comment
Share on other sites

The first initialisation page is not the cleanup utility if by that you mean the first step of the install. Nor is the second step of the install the cleanup utility.. The cleanup feature is accessed via a sub-menu within the Blog itself (the Process Module)...

If that's the case, then there must be a bug with the installation as I don't see a Cleanup sub-menu on either the Blog itself or the Admin module

Link to comment
Share on other sites

You will only see it if you are logged in as a superuser, something similar to below. No bug related to this has been reported before. If you are logged in as a superuser and you can't see it, then something went wrong with your installation and its best that you start afresh.


  • Like 1
Link to comment
Share on other sites

If Superuser == Admin user, then yes perhaps something went wrong during the installation.

I had a check at the logs (Modules) and couldn't see any indicator that the installation had gone wrong.

When I get a chance to do a fresh install, I will try again from scratch and let you know.

Are you aware of any clashes with other modules, besides the the Blog Module?

Link to comment
Share on other sites

I'm not aware of any clashes. What do you mean by the Blog Module? This is the Blog Module  :lol:. You probably mean the Blog Profile by Ryan? I know it appears in the modules directory so that can be confusing. 

Let us know how it goes.

Link to comment
Share on other sites

I'm not aware of any clashes. What do you mean by the Blog Module? This is the Blog Module  :lol:. You probably mean the Blog Profile by Ryan? I know it appears in the modules directory so that can be confusing. 

Let us know how it goes.

I've just tried to uninstall the modules, but because I don't have access to the Cleanup option I presume I can't uninstall the module.

Had a look at the docs, and it refers to the cleanup option ....  :huh: 

What's the best way to remove it manually?

Link to comment
Share on other sites

You can still uninstall it but it will leave behind all the pages, fields and templates it had installed before, which then won't allow you to re-install Blog. I don't know how comfortable you are with PHP and PW but you could copy the cleanup utility code to your template file and run it from there. I can show you how to do it but before that:

  1. Is this a dev install? i.e. not a production site.
  2. Is this on a local machine or on a remote server? I just can't figure out why you cannot see the cleanup Menu item.
  3. Did you alter the module code in any way?
  4. Can you confirm you are logged in as a superuser (the main admin person)?
  5. Can you show me a screenshot of what you see when you go to /yoursite /admin/blog/? admin here is whatever you called your PW admin, normally processwire.
  6. Have you tried updating the Blog modules (just overwritting the files) to see if cleanup menu item will appear?
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...