Just five days after 2.1.2 was out, we are now greeted with 2.1.3. It turns out that upgrading to EE 2.1.2 brought some pretty significant issues with the publish form for some people. Lisa posted a brief note about the update on the blog and of course you can consult the change log for details.
The error I saw the most reports of on the forums was about some sort of 500 error showing up on the publish form. If you’re experiencing that, or if you’re just running 2.1.2 at all, I highly recommend updating.
That being said, let me leave you with one public service announcement:
Make sure you back up everything before doing these updates. Using version control of course is one of the best ways, but if you’re crazy enough not to use version control, at least make a full site backup before upgrading. This means the database too! I have my fingers crossed that 2.1.3 is going to fix the issues with 2.1.2, but nobody should ever do an upgrade like this without having a way to roll back to the previous version. Sure, it was EllisLab who dropped the ball in letting some bugs slip through their testing, but even when I’m 100% confident a piece of software has been extensively tested in environments just like mine, I still back up everything before doing upgrades.