In beta 3, we have reintroduced the crash reporting system. It is the very annoying thing that stops the execution of GUI at any uncaught exception. In previous betas, some of these exceptions occurs, and they were not critical (i.e. GUI can continue to work without any problem), but we now want to track down all of them. So if error occurs, please send the crash report, or open an issue with copying the System information text displayed in the crash report (prefer this solution actually).
In other hand, the crash reporter system helped us to track down some very serious bugs. One of the most critical has been analyzed just now: We know the reason why the GUI crash at startup sometimes, saying something about ‘maker XXX is not recognized’. This one was particularly tricky to find out but thanks to the all the crash reports, it is now tracked down and fixed.
We also are bored by supporting people having problem with installing ejabberd_xmlrpc. This not standard module helped us to access the admin of XMPP Server in a pretty fast way (first version where using ejabberdctl as subprocess). Making this module correctly working is quite a pain. Build always seems to goes fine, but it’s actually messed up, resulting strange error in ejabberd log, and (most important) making Archipel not working correctly. Seriously, 90% of problem reported by users are related to their install of this module, and most of the time, they lost hours to make it work.
Well, now this is over. As we want user experience to be the most smooth as possible, from installation to usage, the need of this module is no more required. Users management is done by using XMPP and shared groups management is using the ejabberd subprocess for now (we will discuss about change on this later). And as we don’t like to drop functional code, you now have the choice to use it if you want to. Isn’t life great?
All these changes will be published in a Beta 3.1 that *should* be release this afternoon.
We will provide companies with professional support soon.