Version 0.9.11 is available šŸŽ‰

Version 0.9.11 is a security and bug fix version that incorporates the security and bug fixes introduced in WordPress 0.9.10 into the 0.9 line. The WordPress page describes the changes as following

These changes include a pair of security fixes that handle how comments are filtered and then stored in the database.

The changes were incorporated “as is” and there are no further impacts to calmPress.

Get the full install of 0.9.11 or the upgrade oriented version.

Alpha 5 of the 1.0.0 release is available

The fifth Alpha release of the 1.0.0 line is here. In addition to continued development of calmPressĀ itself, it incorporates changes from the WordPress 5.0.2 release which are not related to GutenbergĀ .

Simplification of the user profile
All fields that do not make much sense were removed, and there is more flexibility in setting a display name.

Username is not beingĀ used anymore anywhere in the UI.
In all of the places where a username was expected as an input, or it was displayed, it is replaced by the userā€™s email address.

In the UI related to user registration, the user does not need to select a username, just specify a unique email address.

For backward compatibility, all places which used to accept either username or userā€™s email address as input (for example, login form) will still accept a username even if the UI indicates that an email address is expected.

From a developers perspective,Ā there was no change in the user APIs, and the main change is that the username is not mandatory anymore. When creating a new user, it will be automatically generated from the email address.

Users will still have a username in the DB, it is just not going to be used anywhere in the core UI.

A category is not mandatory for posts
You do not have to have a hierarchicalĀ categorizationĀ of content if you do not want it.

Password protection of posts was removed
The main reason for removal is that it has bad UX for the author, reader, and developers. We are going to figure out better ways to manage restricted content, but this is so bad there is no point in keeping it around until we will have a better approach to the problem.

The relevant API to detect if a post is password protected is still there, it is just going to return a value indicating a password is not needed.

UI for post formats was removed
The general impression is that themes do not provide any significant distinction between the variousĀ formats and that custom post types are probably a better and more robust way to achieve the goals that post formats feature were trying to achieve.

From a developers perspective, there is no change. Attempts to change the post format via the API, are just going to be ignored.

Calendar and archiveĀ widgets were removed
It seems like navigating content based on its publishing date is an extreme edge case.

Get it now!Ā Ā Just be aware that PHP 7.0 is a minimum requirement to run it.

Version 0.9.10 is available šŸŽ‰

This is the first real step in providing site owners a better experience in operating a web oriented CMS.

For this release, the focus is on giving the site owner a choice on when to upgrade. The importance of this was exemplified in the WordPress 5.0.1 security focused release. People who wanted to stay on the 4.9.x release line longer until Gutenberg stabilized had to chose one of the following bad choices:

  • Upgrade to 5.0.1 although they do not want to use Gutenberg and have the hassle of installing plugins to disable it
  • Stay on 4.9.8 with publicly known security vulnerabilities

Although WordPress released 4.9.9 which solved the security issues on the 4.9.x release line, users did not get any indication in the admin UI that such an upgrade path is possible at all.

There are some other small changes, mostly revolving around deprecation of small obsolete features.

Get it Now!Ā Just be aware that PHP 5.2 is a minimum requirement to run it.

Introducing the user guides šŸŽ

While we all avoid reading documentation, at some point, usually after we have spent too much time trying to figure out things by ourselves, we do start to look for some.

So here come theĀ user guides for calmPress. The guides are under “Documentation” and are focused on the bare essentials right now such as, installing, upgrading, migrating and specific documentation on the difference between calmPress and WordPress.

A developers guide will also come at some point in the future.

Alpha 2 of the 1.0.0 release is available

The second Alpha release of the 1.0.0 line is here. In addition to incorporating the PHP 7.3 compatibility changes from the 0.9.9 release, the major change in this release is removal of all shims related to emojis.

From now on it is assumed that, for better or worse, proper support for displaying emojis is up to the browsers and it does not require software based crutches (which many times produce a sub-optimal result). Just like with using text which is in a different language then the main language used on the site, it is up to the author to decide whether the target audience is likely to use softwareĀ  that will properly display the emojis being used.

Our impression is that for the most used emojis there is a very broad support, and you are not likely to run into display problems unless you use some fringe or very new emoji in the content.

Get it now!Ā Ā Just be aware that PHP 7.0 is a minimum requirement to run it.