Jump to content

Module: Blog


Recommended Posts

1) Dev Install. I also made a backup overnight just in case  :rolleyes:

2) Local Machine. Head scratcher this one!

3) No code alteration. 

4) Yes the admin account. The only account I normally use 

5) See below

6) Do you mean reinstalling the module or physically copying files across to the Blog Module directory?

I've tried to reinstall but PW says I already have the latest version.


Just another thought, perhaps have the Cleanup Code available as a separate module could be good too?

Link to comment
Share on other sites

That image tells me you haven't finished installing the Blog module. It is step-2 of the installation. I don't know how you got the Blog pages then since you seem not to have finished installing blog. There's is a button 'Run Install Wizard' on that screen that you need to press to fully install Blog (see image below). When done, you should see a screen like the one I posted earlier, i.e. the Blog Dashboard. You don't see the cleanup menu because you haven't finished installing Blog. What happens you click on the 'Run Install Wizard' button? If this is local install, then it is just easier to start over. If you wanna go that route, I'll guide you with the cleanup...

Edited by kongondo
Link to comment
Share on other sites

Yes, I don't know how I got myself into this predicament.
I did press the run install wizard and everything indicated that the installation went fine.

Run Install Wizard won't run now because of all the existing fields, templates etc & the installation rolls back.

I'm happy to start again.

The reason I need to start again (besides this)  is that I can't seem to add Authors under the Authors page and wasn't sure I had to do it via the Blog Module. 

I will keep an eye out on logs etc in case it happens again ... touch wood it doesn't.
Having a bad day and hoping this is the start of my change of fortunes

Link to comment
Share on other sites

Authors are not added via the authors' page. They are normal ProcessWire users with the role 'blog-author'.
Try the following to cleanup blog manually:

  • Copy all the code in BlogCleanup.php to one of your template files, at the very top. Save
  • Find and replace 'private function' to 'public function' in the code you just copied
  • Find public function cleanUpPages() and add the following lines to it, at the very top of the function. Save
//Get the module config data
$this->data = wire('modules')->getModuleConfigData(get_parent_class($this));

$this->blogStyle = $this->data['blogStyle'];//selected blog style (1-4)
$this->commentsUse = $this->data['commentsUse'];//commenting feature on/off
$this->templateFilesInstall = $this->data['templateFilesInstall'];
  • Add the following code to your template file, somewhere after the last } of the BlogCleanup class you copied to this template file
$bc = new BlogCleanup();
echo $bc->cleanUpPages();
  • Visit a page that uses the template file you added the BlogCleanup class to. Blog Cleanup will run but you will get lots of PHP notices. Just ignore them. You will also have to manually delete your template files (normally it would be done for you but that needs code alteration in our manual cleanup).
  • Restore you template file to the state it was before you added the BlogCleanup class. Save

You should be able to start afresh then. I am afraid I don't have any more time today to invest in this. Hope it works out.

Edited by kongondo
Link to comment
Share on other sites

Hi Kongondo,

Thanks for the instructions, Kongondo!

Much appreciated!

Unfortunately, it didn't work too well for me as it didn't clean up everything (as you mentioned) and I ended up deleting entries off the CMS as the error messages dictated.

I finally managed to get it install (I think!) with 1 error message that I'm not sure is an error, as the comments table actually is created by the installation.

I've also remembered why I got into this predicament.

The very first installation I did failed because my xdebug.max_nesting_level was set to 100 and not something higher & the installation process reached that limit. 
I was meant to come back to it, but never had the time.

After I did the cleanup & increased this number to 300, I got new error messages which I worked through. which I fixed eventually.

I will also try and post the SQL I used in seperate post.


Rollback instructions. Use at your own risk.

1) Export your site or DB first before you do anything else. Backup! Backup! Backup!

2) Run the following script

start transaction;
select * from templates where name like '%blog%';
delete from templates where name like '%blog%';
select * from templates where name like '%blog%';
select * from fields where name like '%blog%';
delete from fields where name like 'blog%';
select * from fields where name like 'blog%';
select * from pages where name like '%blog%';
delete from pages where name like 'blog%';
select * from pages where name like 'blog%';
select * from fieldgroups where name like '%blog%'
select * from fieldgroups_fields where fieldgroups_id in (
select id from fieldgroups where name like '%blog%'
delete from fieldgroups_fields where fieldgroups_id in (
select id from fieldgroups where name like '%blog%'
delete from fieldgroups where name like '%blog%'
If the Rollback attempt looks fine, run a Commit version of it.
Link to comment
Share on other sites

Aah...wish you'd mentioned that xdebug issue :-). It's bitten somebody else here before. Anyway, you got there in the end. The comments field sql error can be safely ignored. I mentioned it to Ryan a while ago but he didn't seem to be able to replicate it. It has nothing to do with Blog per se, but the comments module which ships with PW...

You rollback instructions (even with the disclaimer) seem quite dangerous and I wouldn't recommend any one to use them. You are using LIKE to search. That will match other things that are not 'blog' but 'sound' like blog...Instead, use the cleanup facility in Blog :-)

Edited by kongondo
Link to comment
Share on other sites

Yes I agree with it being dangerous ... but I was in a desperate corner and I was willing to take the risk.

As for the script itself and '%Blog%' being dangerous, I do agree but that's why I also had Select statements in there for the user to check before they delete.

Hopefully no one else will have to go through what I did :)

That XDebug issue, I only recently discovered what the cause & its outreaching effect was.

Also I first installed the blog quite a while back, long before XDebug became a big issue and i was searching around for answers.

I definitely will have a "Cleanup" celebration later this evening with some well earned bevvies!

Link to comment
Share on other sites


I have a question regarding logging in the Processwire Module as a Blog Author.

I created a user that is a member of the blog-authors group.

When I login to the Processwire admin page using the user's credentials, this is all I see is this.


Had a look, and it has the following error log entry.


2015-10-18 14:05:33 admin /processwire/page/list/?id=id&render=render&am…

SQLSTATE[HY000]: General error: could not call class constructor [pageClass=Page, template=]

The URL Link above is :


Logging in as Admin, there are no issues with the blog.

I can do everything including entering blog posts.

There are no error log entries for Admin/Blog Module.

FYI, I have set couple of child pages of the Blog as hidden. Could this be the cause?

Link to comment
Share on other sites

This is actually ProcessWire territory and not a Blog one. :-).

I'd suggest that you search and have a read in the forums and docs how ProcessWire implements access controls. As you've figured out, access in ProcessWire is controlled at two levels; the high level (when editing a 'role') and the low level (at the template level).. Also have a good read of the info in the 'role' edit screen. This 'homework' will help you beyond Blog...:-)

  • Like 2
Link to comment
Share on other sites

Ok thanks for the Homework :)

Feel like I'm back in school again.

I've read the docs and some forum articles as you suggested.

Didn't realise you had to allocate Add-Children permissions as well on the Blog-Posts to be able to add a new Blog-Post.

(Create Page & Edit Page permissions was not enough)

Was there a reason no permissions are set by default during the initial installation?

Seems to me a Blog-Author role implies it should be able to create & edit Blog Posts by default.

Link to comment
Share on other sites

Was there a reason no permissions are set by default during the initial installation?

Seems to me a Blog-Author role implies it should be able to create & edit Blog Posts by default.

Yes. Doing things the ProcessWire way....we make no assumptions (aka total freedom for end-user to implement as they wish). Some stuff, e.g. the role and demo files, Blog offers as a courtesy to get you started

Link to comment
Share on other sites

Yes. Doing things the ProcessWire way....we make no assumptions (aka total freedom for end-user to implement as they wish). Some stuff, e.g. the role and demo files, Blog offers as a courtesy to get you started

Aaah the Processwire way. Had a feeling you might say something similar.

I'm slowly getting accustomed to it nonetheless :)

Link to comment
Share on other sites

Hi Kongondo,

I've noticed there's a Quick Post section in the Posts Menu in the Blog Dashboard.

But it's not showing a field I added to the Blog Post Template.

I'm guessing I have to modify some module code to get it showing (& saving)?

Do you know which modules I have to look at?

Or is there another way that I've overlooked?

Link to comment
Share on other sites

I assume you meant traversing the Page Tree and entering a Blog Post as a page?

I think for a CMS administrator or a Developer, that is a fine workaround.

But unfortunately we're trying to convince bloggers to come write for our site and that particular UX in Processwire is not a great selling point for us IMHO.

I think the Blog Panel is actually a much better UX for a non technical person to enter blog entries into.

Just a shame that  adding a single custom field to it as not as straight forward.

Link to comment
Share on other sites

I assume you meant traversing the Page Tree and entering a Blog Post as a page?

I think for a CMS administrator or a Developer, that is a fine workaround.

But unfortunately we're trying to convince bloggers to come write for our site and that particular UX in Processwire is not a great selling point for us IMHO.

I think the Blog Panel is actually a much better UX for a non technical person to enter blog entries into.

Just a shame that  adding a single custom field to it as not as straight forward.

use this in combination with that and you have a strong "selling point" and/or alternative admin UX for batch editing even this module could be a solution for the "holder page" like /pw-root/posts/... to use ;)

The Blog panel serv also all posts in the postspage and all posts have a edit link on there titles....so hide the quickpost row simple via CSS...

Also make use of the simple and easy "Add New" Button and/or bookmarks so the user don't have to navigate trough the pagetree...there are many shortcuts and UI improvments possible with PW - but like everything else the choice to use them in your setup is on you!

regards mr-fan

  • Like 3
Link to comment
Share on other sites

@FrancisChung, best way to remove manually is to literally uninstall module and remove the pages, so everything under blog in the page list should be deleted, including the blog page itself.  Then move into deleting the fields, then delete templates.  As in delete, I mean, delete through ProcessWire.  Once you have done this, empty trash on the page list.  Then go ahead and delete the templates from your templates directory via SSH or FTP. 

If you have tons of posts under blog, then use batch editor to remove them all at once. 

Just curious, 

Why are you removing this module?

Link to comment
Share on other sites

@quickjeff...his Blog install got messed up by an x-debug limitation so he needed to reinstall. He was caught between a rock and a hard place and couldn't use the 'cleanup feature' since Blog didn't finish installing due to the x-debug thing.

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

Update: Blog Version 2.3.5 (dev branch only for now)


  1. Fixed issue of slow loading dashboards on sites with lots of posts.
  2. Added some missing translation strings, thanks @mr-fan.
  3. Decluttered modal window, thanks @mr-fan.
  4. Some code optimisations.

I don't think there are any other pending issues. Apologies it took so long to get to this update; we got there in the end :-)

Edited by kongondo
  • 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...