Firestorm 4.6.9 40478 Blocked?

[KarraSue]

Why didn't they inform users running 4.6.9 40478 that it was going to be blocked today?

[Theresa Tennyson]

---

KarraSue wrote:

Why didn't they inform users running 4.6.9 40478 that it was going to be blocked today?

---

I'm guessing that was the original version of 4.6.9 before it was patched a few days later. They probably didn't think anyone was actually using it any more -- they certainly don't want anyone to use it. It's no longer available for download. You should update to the current version of 4.6.9.

[Ed Merryman]

4.6.9 40478 was never an official release

I can only assume you meant 4.6.1.40478. As for why they didn't inform the users, well they did.

There was a blog post that went out a week ago (see http://www.firestormviewer.org/blocking-version-4-6-1/ )

[KarraSue]

I updated today,thanks

What were the enhancements in this newest release that I have?

 

[Ed Merryman]

There have been a lot of changes since the 4.6.1 release. You can go to the wiki (there is a link to it in the help menu in the viewer) and see the release notes. There is also a link to the class schedule as well. The classes can help you learn about the various preferences and features. Also there is an open Q&A after the classes where you can ask pretty much anything.

[Minuet Voir]

---

KarraSue wrote:

Why didn't they inform users running 4.6.9 40478 that it was going to be blocked today?

---

 Hi KarraSue. The Firestorm build which was blocked on February 20th was 4.6.1. (40478).

There were indeed two warnings; one on February 13, 2015 and the other was December 10, 2014 when Version 4.6.9 was released. This is in keeping with the blocking versions policy announced by the team on November 16, 2013. The top 3 blog posts (which still includes the blocking of Version 4.6.1. post) can be seen on the splash screen whenever you launch the viewer. 

Blocking Version 4.6.1. on the 20th

Firestorm Release 4.6.9.42969

Why Block Older Versions

 

[KarraSue]

Thanks for the info, was just an error on My part by not reading the messages on the login screen