The Symphony team is pleased to announce the immediate availability of Symphony 2.1, codenamed Hot Wallaby Ba—oh, wait, that's right... we don't do codenames here. Sorry.
More secure than ever, and so stable we should be sweeping horse manure out of it, Symphony 2.1 is the last major build in the 2.* series. As of this release, development focus shifts primarily to Symphony 3, and the 2.* series will see only critical bugfixes and security updates in the form of minor point releases (2.1.*).
Symphony 2.1 is a flagship release as it represents the culmination of all the development that's gone into Symphony 2 over the past few years—it is faster, more powerful, more efficient, more stable, and more secure than any release to date. We recommended that all websites running Symphony 2.* be upgraded immediately (remember to backup first).
And be sure to act now! The first 100 people to update their Symphony installs will receive a free voucher1 for an awkwardly lingering embrace from Allen and/or a rare white wallaby.
Excited? Go get it! (Zip, Git)
Note for Git Users
Git users, please note that we are now using GitHub's organizations feature. The Symphony 2 repo, and all submodules, are now forks owned by the Symphony CMS organisation. To fully update a git-based installation, you will need to edit your .git/config file (and the .git/config files of all core extensions—Debug Devkit, Profile Devkit, Markdown, Maintenance Mode, Selectbox Link Field, JIT Image Manipulation and export_ensemble) and change the URLs of the remote repos from github.com/symphony or github.com/pointybeard to github.com/symphonycms.
Note on Version Numbering
Version 2.1 is the stable build based on the 2.0.8 release candidates. As suggested by Nils, the version number was bumped to better align with our future release procedure and version numbering plans.
1 No they won't.
Comments
Woot! Thanks, dev team. Time to get busy advocating and documenting.
Outstandign! I’m just about to push a new site live next week!
Wooohooo
W00t!
Great!
Great, thanks for the update!
3 sites updated to 2.1 in the last 20 minutes. Good stuff guys - upgrading Symphony sites is so straight forward!
If I may ask a stupid question… If I installed Symphony via
git clone, what’s the command for now updating to this version?I tried installing Symphony 2.1 from scratch and there appears to be an error, which causes, that “symphony.symentriesdata_26” is not generated from the install.php file in the workspace folder. This results in Symphony fatal errors when I try to access Data sources within the Blueprints section of the backend. Am I missing something or is this a valid bug.
I’m new here, so I’m unsure where to post these bugs. I’m loving Symphony regardless.
@jstar198: Have a look at the readme file that is attached to the Git repository. It contains a step by step guide. For the most recent version browse to <http:// github.com/symphonycms/symphony-2/>.
@marcelklimo: Your issue has been reported in the forum. It’s most likely a bug in the default workspace SQL. Alistair said he is going to look into it. If you like to start with a clean install, just delete the default workspace folder an a new one will be created during the install (be aware that there will be no templates, sections or pages included in this case — you’ll have to creare them manually).
If you find bugs the issue tracker is available at http://getsymphony.com/discuss/issues/.
Yippie!
@Nils: Thanks Nils. Yeah, I just got the clean source from github. I looked into the workspace SQL file and it doesnt have CREATE table query for that specific table.
Damnit, I got excited about receiving a rare white wallaby, then I read the footnote. I want my wallaby!
Nice work!
Happy happy. Nearing the end of project build with RC3, so good timing for an update. One observation: an extension we were using (Unique Upload Field) broke after the update and required a little squishing to make it work. Ever considered a mechanism for extensions to update themselves after a core update?
@ferrai: It’s up to extension developers to keep their extensions current. We’ve asked nicely and even applied peer pressure.
We do want to make it easier for users to update their extensions when updates are available, though, and that’s something we’re mulling over for Symphony 3. That said, it’s not an easy question. People install Symphony and manage extensions in different ways, from simple zip-upload schemes to complex multi-repository + submodules git schemes. And everyone’s environment is different.
Me like!
Although, I tried the beta of Symphony 3 and me like even more! However, I wonder how recyclable the extensions will be…
@ferrai: If it needed some tweaking, could you fork on Github and send the update back to the original author?
Compatibility table is currently at 1.6%. Nice.
(Craig I’ve emailed you about this separately, the previous 2.0.8 compatibility appears to have been lost with the rename to 2.1)
We will miss you 2.0.x
I am very happy with Symphony 2.1 (although I somehow missed the “contributor” mention this time…)
@ferrai:
I don’t see any reason for this, and it did not happen to me. Please post your issue on GitHub — the extension is used a lot in the community, so I will care for any problems immediately.
Outstanding! Thanks for everyone who have contributed.
Sorry, Michael. I tried to be thorough when crawling through the commit logs but I must have missed you. Will add you now.
Just posted a new install archive. Should fix the missing #26 problem. Apologies everyone.
That’s the last time, Alistair. I’m afraid we’re going to have to let you go ;-)
Best press release EVER
I’m having trouble pulling the default extensions using
git submodule update:export_ensembleis referencing the unknown treea068d9c8765129cd7ac66dc33b0e6b51b0a05521.I guess it’s a commit-hash but I can’t find it, neither in github.com/symphonycms/export_ensemble nor in github.com/pointybeard/export_ensemble.
I had the same problem as @phoque. I ended up removing the extension and adding it manually.
That submodules issue was reported and fixed.
Create an account or sign in to comment.