Fri, 10 Apr 2026 02:21:33 +0000 https://bugs.horde.org/ticket/2114 convert_imp_filters.php doesn't convert correctly I have ran into troubles with convert_imp_filters.php. Tried upgrading our old system to new, settings are these: Old system: Horde 2.2.3 IMP 3.2.1 My new setup is this: Horde 3.0.4 Imp 4.0.3 Ingo 1.0.1 Took dump from old system db and tried converting from that. Script gives correct output, showing everything as expected and results are correct. However when looking what it has actually done is quite disaster. Script seems to add every rule it encounters into same queue, and assings current queue to user currently being prosessed. That means first user gets his filters converted correctly, and then things break down: second user gets 1.st user filters and own, 3rd user gets 1st and 2nd and own filters and so forth until everyone have been prosessed. This quite much kills easy possibilities to upgrade setup, at least when sieve has been used. No knowledge if it works with other. Thu, 09 Jun 2005 12:23:03 +0000 https://bugs.horde.org/ticket/2114#t9038 Can you upload any example SQL dump as short as possible to reproduce this? Thu, 09 Jun 2005 12:40:44 +0000 https://bugs.horde.org/ticket/2114#t9039 Alright, here is true data, just anonymized. I tried with this myself too, and it gives faulty result. There is twice same data, with only different usernames. I would think that 4 first entries are enough to see what is happening, but those 4 more gives stronger effect. If there is need, I can provide more data, but I think this gives idea. Thu, 09 Jun 2005 13:17:52 +0000 https://bugs.horde.org/ticket/2114#t9040 Hi - I just ran into this bug myself with convert_imp_filters.php. The problem is this line (I think): $filters = $ingo_storage->retrieve(INGO_STORAGE_ACTION_FILTERS) There is an optional boolean parameter for the retrieve() function which prevents it from retrieving cached data for the session. I switched it on thusly: $filters = $ingo_storage->retrieve(INGO_STORAGE_ACTION_FILTERS, false) ... and the problem went away. Don't know if this is the correct solution but it seems to work. -Robin Fri, 10 Jun 2005 18:44:06 +0000 https://bugs.horde.org/ticket/2114#t9072 Nice catch, committed, thanks. Mon, 13 Jun 2005 09:21:46 +0000 https://bugs.horde.org/ticket/2114#t9111