Datenstrom Yellow 0.8.19 has been released

[markseuffert]

What’s new:

• Added support for installation with built-in web server
• Updated wiki extension, renamed layout wikipages to wiki-start
• Updated blog extension, renamed layout blogpages to blog-start
• Updated blog extension, replaced shortcut blogarchive with blogyears and blogmonths
• Updated language files, added decimal separator
• Updated layout files, moved pagination into layouts
• Updated API, replaced pagination() with paginate()
• Updated installation guide for command line

Let us know what you think. Any comments are welcome.

[cellio]

Sounds great! I haven't been through an upgrade yet; is there any sort of porting guide? I'm specifically interested in the blog extension; I've made changes on the previous version and now want to move to the new version. Is diffing what I have against the baseline of the previous version, and then figuring out where to apply those changes in the new version, my best bet? (Sorry if this too much of a beginner question.) Thanks for the great platform!

[markseuffert]

See also: How to update a website. This is probably a good starting point for new users.

[cellio]

Thank you! I didn't know about the update command. That page looks very useful. (Before this, I thought "update" meant "download the new zip file, unpack it, and try to sort out the diffs yourself", which sounded intimidating.)

[markseuffert]

Hope this is more comfortable than git commands and zip files. Let us know how it works for you.

[cellio]

I'm not afraid of git commands (so long as you don't say rebase :-) ), but I didn't do things properly when I first started building my site and now I've gotten myself into a bit of a revision-tracking hole that I need to climb out of. I'll do those updates on a branch to make sure everything works before merging it back and updating the live site. I'm glad to learn there's some automation available to help me with that; I thought I was going to have to diff individual files one at a time to sort out the update.

[markseuffert]

I would recommend to update your website after each release, then the updater can take care of the heavy lifting for you. Don't wait too long. Skipping over multiple releases is not really recommended, because the updater doesn't carry around multiple years of backwards-compatibility. As with most open source products, frequent updates and feedback are greatly appreciated.