This Blog module enables you to easily create and manage a Blog in ProcessWire. It is based on the Blog Profile module by Ryan Cramer. The module consists of three separate modules:
ProcessBlog: Manage Blog in the backend/Admin. MarkupBlog: Display Blog in the frontend. BlogPublishDate: Automatically sets a publish date when you publish a Blog Post.
- Dashboard with quick stats about your Blog.
- Quick post.
- Full view, create, edit, delete, update (CRUD) Posts, Categories and Tags within a single interface.
- Bulk actions.
- Edit Blog settings.
- Blog Authors' stats.
- Turn widgets on/off (publish/unpublish).
- Fully uninstall/cleanup Blog templates, fields, pages and optionally template files.
- Easily output your Blog in the frontend, where and how you wish (e,g, only output part of the Blog).
- Use any CSS framework (or not!) you wish.
- PocketGrid CSS included with the demo Template Files (fully responsive).
How to Install
Install via ProcessWire modules' screen. Once installed, there's two steps involved to finalise the install:
A. Configure Blog settings in its module's configuration screen.
Here you will have to choose from 4 Blog styles to match the Blog URL structure you want:
- Blog style 1: /mysite/blog/posts/example-post/
- Blog style 2: /mysite/blog/example-post/
- Blog style 3: /mysite/posts/example-post/
- Blog style 4: /mysite/example-post/
On this screen, you also select:
- Whether you want to enable the commenting feature;
- The auto-publish/unpublish posts feature (for which you would need the module SchedulePages;
- Whether to install 'no template files', 'blank template files', or 'demo template files'; and
- Optionally specify a tag for grouping Blog Templates and Fields in their respective ProcessWire admin pages
B. Install Blog Templates, Pages, Fields, Role and optionally Template Files.
In this second step, via the Blog dashboard (admin/blog/), you will see an overview of the settings you selected in the first step above. Here you install Blog's components. Before you click the button to run the install wizard, nothing will happen yet. You can still go back and change the module configuration settings. Until you run the install wizard in this second step, you will have no Blog Pages, Fields, Templates, etc.
On this page, you will also be able to rename your Blog’s main pages before they are created. If you don’t do it at this stage, you can also rename them post-install in the ProcessWire pages' tree. If you are happy with your settings, click the install wizard to proceed. Blog will be fully installed with your settings within a few seconds and you will then be presented with the Blog dashboard.
Only Templates, Pages and Fields necessary for your selected 'Blog style' will be installed. For instance, if you did not enable the commenting feature, related Templates, Pages, etc. will not be created.
Note that non-enabled features cannot be enabled once the second part of the install is complete. However, using the 'Cleanup' feature (see below) you can return Blog to the first-step of the installer stage and enable a feature you want or even select a different Blog style.
If you chose to install the demo Template Files, also manually copy over the /css/ and /scripts/ folders present in Blog module's folder to your /site/templates/ folder.
If you need to change some configurations, you can go back to the module settings and do it BEFORE you finalise step two of the installation. It is important that once the installation is finalised, in case you had left the ProcessBlog's module configuration's browser window open, NOT to press submit again. Otherwise, MarkupBlog may not function as expected. However, if you reload the module configurations screen once the second-part of the installer has finished, you will not be able to change the configuration settings. Instead, you will be presented with an overview of your installed settings.
How to Use
Full documentation is available here.
- The module Dashboard will not work with Blog Profile installs!
- MarkupBlog replicates the Blog Profile. Hence, the 'items' Fields, Templates, Template Files and a couple of Pages are installed where such, with similar names, do not already exist, i.e., installation is non-destructive.
- With the exception of Template Files, note that if even one item with a similar name (and path for Page items) already exists on your site, NONE of the items will be installed. Instead, step two of the installation will be aborted.
- For Template Files, if you did not select the 'no template files' option, these are only copied over to /site/templates/ where no template with an identical name already exists. This means that no Template File gets overwritten.
- Fields and Templates are prefixed with blog_ and blog- respectively.
- The module also adds 3 Fields (biography [blog_body], image [blog_images] and title) to the user template. These are needed for the Blog Author biography.
- Role blog-author and permission blog are created on install.
- Until you set 'author titles' for your Blog Authors (in Admin > Access > Users), a generic 'Author Name' will be used as their display names.
- In order to use the Recent Tweets Widget, you will need to separately install and setup the module MarkupTwitterFeed.
Uninstalling Blog is a two-step process. If you are logged in as a superuser, you will see a Blog menu item called Cleanup. It will lead to a screen with info about all the Fields, Templates, Pages and Role you are about to delete. It will also list the Blog Template Files that, if you wish, you can also delete. This utility is also useful when you want to try out the different Blog styles without uninstalling the whole Blog module. It returns Blog to the state similar to when you first installed the module. Of course, in case you want to remove Blog as well, just go ahead and uninstall in the normal way but AFTER you have cleaned-up.
- Fix bug in add new 'blog-author' role that threw fatal error.
- Various other minor fixes.
- Better error message after blog cleanup.
- Add option to getArchives() that allows ordering of post months in descending order.
- Fixed illegal offset warnings bug in template blog-archives.php.
- Refactored array empty/not empty checks.
- Fixed bug that caused blog settings not to save.
- Code refactoring.
- Added method to find embedded images for use as featured image(s), for example.
- Support for namespaced ProcessWire only (ProcessWire 3.x).
- All ProcessWire Comments Form Options can now be passed as as options to renderComments(). See the options here
- New, cleaner UI.
- Better sorting of Posts, Categories and Tags in their dashboards.
- New option for posts: post_edit. Allows top or bottom placement of link to edit post for logged in users or non-display of link for all users.
- Code refactoring.
- Fixed sql error thrown when comments disabled and accessed blog dashboard.
- Added capability to copy demo JS and CSS files on blog install as well as remove them on uninstall.
- Full compatibility with ProcessWire 2.8.x and ProcessWire 3.x. See PR.
- Fixed bug where comments' date was being output as a raw timestamp (owing to a miss during the last commit).
- Fixed bug where comments' date were not being correctly output.
- All MarkupPageNav (used in renderPosts()) options can now be passed to renderPosts() to customise pagination of posts.
- Added option to use Rich Text Editor (CKEditor) in Quick Post. Setting is configurable in ProcessBlog module settings (both pre- and post-install).
- Fixed issue where dashboards were loading very slowly on sites with lots of posts.
- Added some missing translation strings.
- Some code optimisations.
Preserve all line breaks as paragraphs for posts created via ProcessBlog's quickpost.
Added a very visible reminder in Blog's module configuration screen not to uninstall the module BEFORE running the in-built Cleanup Utility.
Added a renderRelatedPosts() method.
- Fixed Posts/Categories/Tags dashboard html rendering issue on multilingual sites.
- Added 'post_small_tag' option to renderPosts() to specify html tag to wrap summary blog posts (small).
- Some code optimisations.
- Use Blog authors' display names in author pages url/links rather than their usernames
- Fixed renderNextPrevPosts() not sorting/displaying previous/next posts properly
- All main methods that render HTML output are now configurable via a parameter/argument $options.
- Ability to add a featured image to a post
- Minor updates to demo template files.
- Fixed a comments' visibility issue.
- Enhancement to comments' visibility status (added status HIDDEN).
- Four Blog styles (URL structures).
- Two-step installer/uninstaller.
- Configurable module.
- Cleaner utility (for Blog fields, templates, template files, etc.).
- Auto-(un)publish feature.
- Commenting feature - enable/disable.
- Other various enhancements.
- Added new small autoload module BlogPublishDate as part of the Blog module suite, that saves a Blog Post's publication date.
- Enhancements to Posts, Categories and Tags Dashboards: Customisable number of posts/categories/tags to show per page (via a drop-down select). Selected value is preserved via a cookie per context (i.e. can have different values for posts, categories and tags dashboard) and per user.
- Date column: shows 'Pending' for unpublished posts (never before published ones), 'Expired' (published then unpublished posts) and published Date for currently published posts.
- Date shown is formatted according to the format set in 'blog_date'.
- Fixed sorting by date column.
- Changes to renderComments(). Added a 4th Array $options argument for customising the texts describing the various comments' statuses.
- Minor styling issues updates.
- Added comments visibility settings at post and global level.
- Added Posts' Bulk Actions.
- Added new widget 'Post Author'. The widget allows to add a post's author's biography with each post (above or below the post).
- Made 'posts truncate length' configurable.
- Several strings made translatable
- Support Forum
- Full announcement about Blog version 2
- Video ProcessBlog demo (Blog version 1)
- Video MarkupBlog demo (Blog version 1)
Upgrading from Blog version 1 to version 2
Please refer to this post for full instructions and an upgrade script.