Posted
3 months
ago
by
Simone Chiaretta
Subtext finally leaves the SourceForge Hell and moves source code and issue tracking on Google Code.
What does that mean for users? First of all that means that you won't have to fight with the bad user experience of SourceForge any
... [More]
more.
Then, if you were reading and asking questions in the SF Forums, now you have to subscribe to the Subtext group on Google Groups.
For the moment the latest stable version is still on SourceForge, version 2.1. Actually the really latest version (2.1.1) is available for download and install from the Windows Web App Gallery.
I'm pretty excited by this move, since I was really annoyed by the lack of new features and usability of SourceForge.
Google, Subtext [Less]
Posted
7 months
ago
by
Simone Chiaretta
Taking advantage of the Thanksgiving Day’s holiday, Phil wrapped up a few changes and bug fixes and released the first update of Subtext 2: Subtext 2.1.
This new version fixes also on flaw that could allow a potential XSS attack via
... [More]
comment.
To read more about the release, go to Phil’s post: Subtext 2.1 Released! Contains Security Update.
If you are on Subtext 2.0 there are no database schema changes, so just replace the dlls and merge the web.config file, and you are done.
Download the latest version here.
Technorati Tags: subtext [Less]
Posted
11 months
ago
by
Steven Harman
Plenty of other folks have already announced that the Subtext 2.0 bits finally dropped this past Sunday afternoon, hot off the CI server. And by finally, I mean – over a year after the last official release, and four months after we said it was
... [More]
just around the corner.
Good things come to those who wait At least that’s what the Heinz company says. Or maybe they just had a brilliant marketing department.
Anyhow, Simone Chiaretta and several other folks have already hit the release highlights, so I’ll just steal their summaries:
Top notch support for Windows Live Writer thanks to some patches and check-ins from Tim Heuer New CSS-based admin design that makes better use of apace Support for mobile skins (and a default mobile skin if your favorite skin doesn’t have mobile support built in) Streamlined installation Process Support for Enclosures CSS and JS optimizations Setting a date in the future for publishing posts Login to your blog using OpenID, as well as use your blog as an OpenID Delegate Ch-ch-cha-changes! As you can see, the new bits are packed with a metric crap-load of bug fixes, new features, and patches. And yes, metric-crap load is a technical term and a real unit of measure… or not, whatever.
But hey, you don’t have to take my word for it. You can get a full list of the changes here:
Bug Fixes Delivered Feature Requests Accepted Patches Go get you some Oh yeah, and I should probably link to the new bits: DOWNLOAD
Technorati Tags: subtext, open source, openid [Less]
Posted
11 months
ago
by
Simone Chiaretta
As I already anticipated a few days ago, Subtext was on its way to be released. And today Phil just announced it: Subtext 2.0 has been released, one year and a few months after the previous version 1.9.5.
I already explained a some of the
... [More]
new features of Subtext 2.0:
Publish in the future JS and CSS performance optimization Enclosures but Subtext 2.0 also brings to the table:
Enhanced MetaWeblog API implementation Enhanced WLW implementation new CSS-based admin layout Mobile-skin support OpenID support, both to login to the admin and to use you blog as OpenID delegate and many bug fixes Read Phil blog for more details on the release notes and for the future plans for Subtext (MVC anyone?).
And, you want to upgrade you blog, or give Subtext a try, here is the url for the download: Subtext 2.0 of SourceForge.
Technorati Tags: Subtext [Less]
Posted
11 months
ago
by
Simone Chiaretta
In the last two days I wrote about two new feature of Subtext 2.0: Enclosures and performance optimizations for skins.
Today I’ll talk about another new feature of Subtext 2.0: Future Posting.
I already anticipated this feature
... [More]
while I was testing it last week: posting in the future allows the blog’s author to write a post either with the post editor online or with any offline blogging application (like Windows Live Writer), set the date and time, save it on the server as published (not as draft), and have it automatically published both on the blog and the RSS feed at the specified moment.
This is useful when writing series of posts: you write all your posts at once, and then schedule them to appear online one per week or per day or every couple of days. (Which is what I’ve been doing with this series of posts.)
It’s also useful when you go on holiday but you still want to publish something on your blog: you can write some posts before your leave and set the publish date in the future while you are relaxing on some Maldivian beach.
How to set the publishing date of post?
If you are using the online post editor, you have to set the Post Date (in en-US format mm/dd/yyyy hh:mm:ss AM/PM) in the Advanced Options panel. The time must be in the blog’s time zone. Expect some enhancements in a future release of Subtext, like an Ajax datetime picker, or similar UI elements.
If you are using Windows Live Writer, you can set the date of the post with the date picker on the bottom toolbar.
How do I know that a post will be published in the future?
A post published in the future will not be accessible online till the publish date has been reached, but you can see the scheduled posts looking at the list of posts in the admin. If the post is scheduled for future publishing, the list will tell you when this will happen.
How dates relate to URLs
Subtext stores 3 different dates for each post:
the date in which the post created
the last modify date
and the publish date
Till Subtext 2.0 the permalink of the post was generated using the date of creation, but now that it’s possible to post in the future this will not make sense anymore: if you write 10 posts and schedule for future publishing they will appear as created all at the same day.
So now the permalink will be generated using the publish date, so that also the url shows the real publish date.
But to keep the backward compatibility, and don’t change the url of past posts, the upgrade procedure to Subtext 2.0 includes also a little update scripts that copies the date of creation into the publish date.
Feedback? Questions?
As usual, if you have questions, bug reports and feedback just write on the forums and report bugs.
It’s done with the features I implemented in Subtext 2.0: tomorrow I’ll write about how the frontend performance optimization works behind the scenes. Please subscribe to the feed if you want to get it automatically in your feedreader.
Technorati Tags: subtext,future post [Less]
aspdotnet blogtools publishing subtext blog web cms asp.net
|
edit tags
Rhino Tools 
