Can I somehow do a back out of the 3.2.0 installation and go back to 3.1.1? Had I known 3.2.0 was going to cause me this much of a headache, I never would have touched it…
Thanks, Stephen…
We had some issues when we upgraded from 3.1 to 3.2 as well (Windows environment using the emebedded DB). I could not get the problems resolved in time so we were forced to revert back to our previous 3.1 installation. We had backed up the Wildfire directory before we did the 3.2 upgrade, so basically we uninstalled 3.2 in the control panel, reinstalled 3.1 and copied the backed up Wildfire directory over the installation and all is well.
There is a way, but it requires at the very least a backup of your DB and the wildfire.xml.
Unfortunately, I learnt the hard way, I did not take a backup thinking it would not be screwed like it has so, I think I am stuck with it…
Hey guys,
What problems are you having with Wildfire 3.2.0? I would like to help you out so you can have a nice experience with it. We are going to release Wildfire 3.2.1 this week with an important list of bug fixes and I would like to include as many fixes as possible.
Thanks,
– Gato
My main issue was, all upgrades in the past have been smooth as…3.2.0 was a bit different…
-
I could not logon with spark clients after the upgrade, until I deleted all plugins(except admin). Not a real issue now but, would have been nice to know before hand.
-
Not all my users use spark, some use other clients because they need a few more options eg. the ability to block out certain users…spark does not have that function…Take Pandion for instance, after the 3.2.0 upgrade, the users had to turn encryption off otherwise they could not log back on.
Other than that, I am now happy with 3.2.0 just, would have been nice to know before hand that these issues where going to happen. Unfortunately, my environment does not allow me the luxury of a test environment that runs parallel with my production environment so, all upgrades are done on the production environment live time…
Thanks again, Stephen…
Hey Stephen,
Sorry to hear that. Wildfifre 3.2.0 includes a very big refactoring work in the core of the server so we worked hard on testing the server to ensure that transition could be as transparent as possible and even released a Beta and 2 Release Candidate versions hoping to find and fix reported problems found by the community. We are also trying to increase the development team size to include QA resources that could also help ensure a better product quality. Having said that Wildfire 3.2.1 to be out this week will include many important bug fixes.
- I could not logon with spark clients after the upgrade, until I deleted all plugins(except admin). Not a real issue now but, would have been nice to know before hand.
This problem has been fixed for Widlfire 3.2.1. The server will now catch any type of exception and print a friendly message in the log files.
- Not all my users use spark, some use other clients because they need a few more options eg. the ability to block out certain users…spark does not have that function…Take Pandion for instance, after the 3.2.0 upgrade, the users had to turn encryption off otherwise they could not log back on.
I’'m currently working on this issue. So far the only option to use Pandion and encrypted connections is using the old SSL method on port 5223. Current status: After TLS has been successfully negotiated Pandion is no longer able to read traffic from the server.
Regards,
– Gato