v2.1.1

This patch release corrects the v2 to v2.1(.1) migration for PostgreSQL data storage (#43). The only other change in this release version numbers; v2.1 users need not upgrade to this release if they are using SQLite or RethinkDB. Conversely, v2 users can skip straight to this release if they have not yet moved to v2.1.

See the v2.1 release announcements for the enhancements that were a part of that release.

v2.1

NOTE The v2 to v2.1 PostgreSQL migration is not working correctly in this release. If you are running v2 with PostgreSQL, please wait for v2.1.1. Version 2.1.1 has been released; please use it instead of this release.

See the full release announcement over on The Bit Badger Blog.

v2

This is the first public release of v 2.0! It contains the following changes as compared with v2-rc2:

New Behavior

• The PostgreSQL data implementation now uses a document-style store; see notes below for migrating existing data.
• Both .NET 6 and .NET 7 runtimes are supported on both Windows and Linux (x64). The application itself uses v7 libraries.
• The htmx library provided by "auto htmx" moves to v1.8.5.

Bug fixes

• Messages are now returned from theme uploads, whether they were successful or encountered errors (#28)
• The "back" link from the RSS settings page was broken due to admin area rearranging for RC2; it has been fixed (#34)
• The list of pages in the admin area was not handling paging correctly; this has been remedied (#35)

Upgrading

Upgrading from v2-rc2 to v2 follows the standard upgrade procedure. For RethinkDB and SQLite data stores, no special processing is required. PostgreSQL users will need to use a backup / upgrade / restore process detailed on the project site.

v2 (Release Candidate 2)

This release contains the following changes from v2-rc1:

• PostgreSQL is a supported back-end data store (#30)
• Password hash storage has been upgraded to ASP.NET Core's implementation (#32)
• Podcast and episode settings, as well as meta items on posts and pages, were streamlined in SQLite storage (#29)
• The application now uses explicit time zone handling throughout (#31)

As a result of the above, there are some breaking changes with this release, and RethinkDB storage will require manual migration steps; see the upgrade notes for details.

v2 (Release Candidate 1)

This release contains the following changes relative to beta 5:

• Theme handling has been streamlined. Any themes in the application directory are loaded at startup, and themes can be added, updated, and deleted by Administrator-level users. As a result of this change, release packaging is a bit different, but requires fewer steps. (#20)
• The runtime caches used to speed page generation can now be refreshed via the application. This should be unnecessary in normal operation, but changes that occur outside the application (ex. CLI actions) used to require restarting the application; now, a cache refresh will pull in that new information. (#23)
• The admin area has received a bit of a makeover; a loading indicator will now appear when a page is loading, and notifications are displayed as "toasts" (small, overlaid blocks of information) instead of "alerts" (text on the page, which shifted the text when the alert went away). (#25)
• Deleting a category, when that category had subcategories, rendered those subcategories inaccessible. Now, when a category is deleted, any subcategories are reassigned to the deleted category's parent category. (#27)
• The CLI now has a help option that lists all available commands; if a bad command is passed, this is also displayed. (#22)
• A handful of small bugs discovered during end-to-end testing were fixed.
• Both the admin and default themes now use Bootstrap 5.1.3.

This release also marks the end of beta releases for v2.0, which is now feature-complete. As of this release, any future releases will handle any required data migration; you can use this release with confidence, knowing that the same care that was taken to make this product easy to use will continue for future releases.

v2 (beta 5)

• Implements user management and access levels throughout the application (#19)
• Cleans up database names (#20) - several were named as one thing but used for another; this task was to take the time to sync the names and their current use

Due to #20, this release has significant data incompatibility with beta 4. There is a file in the root of the repo that can be used to update the case of fields within RethinkDB. While the casing of fields does not affect SQLite, there are some column names that have changed. As with prior beta releases, no data migration is present, but please file an issue if you have been using beta 4 and need assistance with updating to beta 5.

There are also some theme impacts with this release:

• If you looped through categories using where: "id", [value], this should be changed to where: "Id", [value].
• The variable to determine if a user is logged on is now is_logged_on (it was formerly logged_on).
• There are 4 new theme variables to use for checking the access level of the currently logged on user - is_author, is_editor, is_web_log_admin, and is_administrator. These consider levels, so an administrator's is_author will also be true.

Additionally, this release requires updating the admin theme. (Beta 6/RC 1 should bring a change where this will happen automatically on startup.)

v2 (beta 4)

• Revision management for pages and posts (#13)
• Upgrade htmx to v1.8.0 (#18)

Upgrading from beta 3 will require reloading the admin theme from this release. The default theme is unchanged, and no data migration is required.

v2 (beta 3)

• Support uploaded files (#2)
• Add podcast-level tags (#3 / #4 / #7)
• Use web log slug for backup (#16)
• Make MyWebLog executable in tar.bz2 archive (#14)

Upgrading from v2.0-beta02 will require reloading the admin theme; the default theme was unchanged.

v2 (beta 2)

This is the second beta release. Data migration between beta 1 and this release is not provided, though if you get stuck, file an issue and I can help. If you are upgrading from beta 1, you will need to reload the admin theme; it has several changes to support the work done below.

Enhancements:

• Podcast episodes are now their own structure instead of being based on post metadata fields (#9)
• Podcast episodes support chapters (#5) and transcripts (#8), as well as season and episode numbers

Bugs Fixed:

• Backup restoration fails (RethinkDB) (#10)
• Custom feeds are not saved (SQLite) (#11)
• Uploading a new theme now invalidates the running theme cache (#12)

v2 (beta 1)

Initial beta release of myWebLog v2. See the project site for more information.