taz.de Posted October 12, 2019 Author Share Posted October 12, 2019 On 4/25/2018 at 3:21 PM, bfarber said: I performed some testing and was able to identify the source of the issue, and will work on a resolution for 4.3.2. Unfortunately, the fix itself will not be retroactive. hi, back then, i had to change your legacyparser-code to avoid the biggest changes in your data. afterwards i had to change some data manually. that was a lot of work. today, i upgraded from 4.2.9 to 4.4.7 and i couldn't believe it - the same bug seems to be still in your upgrade routine. what has become of the fix? regards, ulf Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.