3.0.1 Patch

Fixes issue #900.

TightBlog 3.0

Option for Multi-factor authentication using Google Authenticator provided (enabled by default, can turn off if desired)

Blog template language switched from Velocity 1.0 to Thymeleaf 3.0.

Templating system simplified -- rather than older Roller model of defining separate template files for mobile and standard browser for every page making up a template, now a common template file is used, better fitting one-size-fits-all responsive design used today. However, whenever desired, "getDeviceType()" macro remains available to trigger different stylesheets based on the reader's calculated device type (standard, tablet, mobile.)

Comments by a logged-in blogger tagged as such in the database, allowing for differing styling of the blogger's comments to those of the blogger's readers.

All emails sent by TightBlog now in HTML format using Thymeleaf.

Tag and Category Management pages now include counts of the number of entries having that item as well as first and last entries with that item.

Continued code simplification, dropping of 27 Java source files (146 to 119) and one more database table (13 to 12), compare to 493 source files & 33 tables from the original Roller 5.1.0 fork.

2.0.4 Patch Release

Fixes two issues: #810 & #683
Can upgrade 2.0.3 to 2.0.4 simply by doing "mvn clean install" to generate the WAR and replacing the 2.0.3 WAR with it.

2.0.3 Patch Release

Patch release updates TightBlog dependencies, improves robots.txt file provided in the TightBlog WAR, and fixes a bug in which draft entry previews weren't displaying with the correct theme templates.

This patch will require an update to $url.page method calls in any new/overridden Velocity templates, namely the first parameter is no longer used and will need to be removed, e.g, change from $url.page("basic", "basic-custom.css") to $url.page("basic-custom.css"). The shared themes provided by TightBlog have all incurred this update, it is again only for Velocity templates created or overridden by the blogger.

2.0.2 Patch Release

Patch Highlights:

• Application moved to 100% SSL by default (web.xml shows how modifications can be made for partial SSL as done in 2.0.1 if desired). Helps with security, simplicity, and SEO (links no longer split between http and https).
• Bug resulting in tag maintenance page no longer working fixed
• Changes to tags for a blog entry now automatically refresh blog entry pages (clears cache for the weblog) so the updated tag info will be shown
• Several blog template bugs (all known ones) fixed
• SEO improvements: robot meta tag "noindex" directive added to date-based blog URLs to encourage appearance of blog entry-specific permalink URLs in search engine results (e.g., instead of search engine results displaying myblog/blog/date/20170805 for a blog entry "My Blog Title" from August 5th, URL much more likely to be myblog/blog/entry/my_blog_title instead);
• For themes containing them, day & month pagination links to scroll through blog entries now skip day/months that don't have any entries.

2.0.1 Patch Release

Provides an ability for a blog commenter who checked "notify me" to receive emails when there are further comments for a particular blog entry to unsubscribe from these notifications via a link in the email.

The web.xml is now configured by default to require SSL for the login and editor UI. (The web.xml can be adjusted prior to deployment to require SSL on every page, i.e., the pages read by blog readers.)

Removes the largely obsolete Ping Target functionality (seldom used in SEO today, and most Ping Servers already provide a web page to enter a blog URL to send pings.)

Several UI tweaks and improvements.

TightBlog 2.0

Merge pull request #709 from gmazza/issue704_4

Fix table

Patch Release - v1.0.1

Fixes #576 #583 #594

Database and property file configuration remains the same, can upgrade from v1.0.0 to v1.0.1 merely by swapping out the TightBlog WAR file.

v1.0.0: Merge pull request #573 from gmazza/issue559_3

First release of TightBlog. After checkout, simple mvn clean install to build the war, after doing so mvn jetty:run from apps directory for a local demo of the application at http://localhost:8080/tightblog before deciding to do a regular install.

See project home page for more installation information.

v1.0.0-beta: Merge pull request #539 from gmazza/issue538

1st testing release