We noticed that Clublog has recently changed their XML namespaces.
This means Log4OM is no more able to read the data provided by Clublog itself.
To the date, the namespace was included in the source code as well as field names, but this field may change.
Theoretically only in presence of new data structure that require program rewrite, so no problem, but this time they changed it without apparent reasons. As a result, Clublog file doesn't work anymore, and will stop working as soon as Log4OM executes his planned automatic update.
We're working on a new release to move this field into an external config file (logomui.exe.config) with many other parameters and fields, and in the meanwhile we're preparing a new build of Log4OM.
Please note that the release make more simple for the end user to adapt to new changes on the XML file provided by Clublog (while waiting for a new release, and if Clublog doesn't change their xml format), but a "manual intervention" or a program release is necessary in any case on this kind of situations.
Need help? - Post here and we will find a solution for you.
1 post • Page 1 of 1