Hey there. Just a quick info: It seems BlogText runs smoothly with WordPress 3.5. Haven’t encountered any glitches yet. If you find any, post them at our bug tracker.

BlogText 0.9.4 has just been released. It’s primarily a bug fix release but there are two things you should know about (see below).

As usual, you can download the new version from wordpress.org (see Download & Installation), or use WordPress’ update mechanism.

Syntax Changes ∞

This release introduces two syntax changes that were necessary to fix some bugs.

1. To indent some text, you now need at least two spaces. Before 0.9.4, one space was sufficient. This change was made to avoid accidental indention of content generated by other plug-ins (such as the more-link generated by WordPress itself).

2. List items (like *, #, or ;) now require a space between them and their text. Before 0.9.4, this code *some text would have worked. Now you need to write * some text to create a list. This change was necessary to allow bold text (**) at the beginning of a line.

Logging Database Table ∞

Before 0.9.4, BlogText used to log to a database table called logging (with WordPress prefix, usually wp_logging). This functionality has been removed. However, as a precaution, the database table will not be deleted automatically. You need to do this yourself.

If you want to make sure you’re deleting the correct table, here’s the table’s definition (in SQL):

CREATE TABLE `wp_logging` (
  `id` BIGINT(20) NOT NULL AUTO_INCREMENT,
  `date` datetime NOT NULL,
  `level` CHAR(5) NOT NULL,
  `source` VARCHAR(100) NOT NULL,
  `message` text NOT NULL,
  PRIMARY KEY (`id`),
  KEY `date` (`date`)
)

Changelog Since 0.9.3 ∞

• [Syntax Change] To add indented text to an open list, its items now need to be indented by at least two spaces; previously only one space was necessary. This change was made to avoid accidental indention of content generated by other plug-ins (such as the more-link generated by WordPress itself).
• [Syntax Change] Ordered and unordered list item (e.g. *, #, *#, …) now need a space after them to be recognized. This change was introduced to work around a problem where the BlogText parser didn’t recognize the bold syntax at the beginning of a line.
• [Style Change] The TOC no longer uses float: right.
• Double hash code sections (##) now work, when they’re at the beginning of a line.
• Fixed code blocks with syntax highlighting: No more additional empty lines between code lines (only happen when syntax highlighting was used but line numbering wasn’t).
• Fixed thumbnails that weren’t displayed when PHP strict warning were enabled.
• Fix: Bold text can now be at the beginning of a line, even if indented.

• Updated to newest GeSHi revision (svn: r2522, hg: b4dcf778dccf)

I’m proud to announce the release of BlogText 0.9.3. This version now supports WordPress 3.3. Other than that there were some code improvements and links to headings on the same page now work in multi post view (i.e. the view you see when you open up your blog).

As usual, you can download the new version over at wordpress.org (see Download & Installation) or use WordPress’ own update mechanism.

Note: If your WordPress post editor toolbar is blank after updating to WordPress 3.3, hit the “Reload” button in your browser while in the “Create New Post” or “Edit Post” screen. If this doesn’t work, clearing your browser cache should do the trick. (This is not a BlogText problem but rather a problem with your browser that doesn’t load the new version of a certain file.)

We’re proud to announce that we’ve released BlogText version 0.9.1.2. Version 0.9.1 brings mainly bugfixes but also some new features and changes. The highlights are:

• Feature: There’s now a button in the editor called “lang lookup”. This opens a new window where you can search the list of programming languages that are available for syntax highlighting in code blocks.
• Change/Feature: Adding a custom anchor id to a heading now requires the hash sign to be separated from the heading text by at least one equal sign. For example, the line == My Heading #my_heading now must be specified as == My Heading == #my_heading. This now allows for a hash sign in the heading without needing to know the HTML entity for a hash sign. Headings like == C# Overview == are now much easier to type.
• Feature: Absolute links (like [[/feed|my feed]]) can now be used.
• Feature: Added backticks (`) for inline code snippets (as alternative to the ## syntax).
• Feature: The quote characters (") around attributes for {{{ ... }}} code blocks are now optional. So you now can specify a code block like this: {{{ lang=java5 class TestClass { } }}}. (Note that there are now quotes around “java5″.
• Feature: The programming language can now also be specified by using the language’s file extension. You can do this, for example, with {{{ lang=.adb package AdaPackage }}} instead of {{{ lang=ada package AdaPackage }}}.
• Bugfix: Certain JPEG images (encoded with Progressive DCT) can now be used. Previously they were identified as malformed JPEG images.
• If an alt text is specified for an image (in WordPress’ media browser), it’s now used as title as well (if no title has been specified separately). Previously the file name was chosen instead.

• Bugfix: Plain text URLs should now always be recognized. Previously, they didn’t work in lists in some cases.

The full changelog can be found here (if WordPress decides to parse the readme file correctly).

As always, head to our download page to download your copy. Or use WordPress’ update manager.