Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 374464" data-attributes="member: 21313">I'm gonna be totally honest with you: I can't explain these problems you have.&nbsp; But you seem to be the only one with such big problems, so I'm not sure where this is coming from.&nbsp; My &quot;quick&quot; guess that is has something to do with your system or setup somehow.&nbsp; Also, all the things you describe as having problems with in 1.3.3 are not really related to any of the changes between 1.3.2 and 1.3.3, another reason I really can't explain why you should have these problems with 1.3.3 and not with 1.3.2.What I can explain is the troubles you had when you reinstalled 1.3.2, this is simply not possible.&nbsp; Your database has been converted for 1.3.3 and will no longer work with 1.3.2.&nbsp; It's too bad we didn't foresee this and build a check into 1.3.2 to refuse to run or alert you or something, so you are quite correct that this is a usability issue! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />&nbsp; But the problems you got after reinstalling 1.3.2 are no surprise, you really need to restart with a clean, emtpy database then.Thanks, that what we aim for! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />&nbsp; And luckily for the majority of users it seems to be running to their liking <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />I'd love to understand what's going wrong on your system...&nbsp; But until that point I fear there's not much we can do about it <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" /></blockquote>

[QUOTE="dvdfreak, post: 374464, member: 21313"] I'm gonna be totally honest with you: I can't explain these problems you have. But you seem to be the only one with such big problems, so I'm not sure where this is coming from. My "quick" guess that is has something to do with your system or setup somehow. Also, all the things you describe as having problems with in 1.3.3 are not really related to any of the changes between 1.3.2 and 1.3.3, another reason I really can't explain why you should have these problems with 1.3.3 and not with 1.3.2. What I [i]can[/i] explain is the troubles you had when you reinstalled 1.3.2, this is simply not possible. Your database has been converted for 1.3.3 and will no longer work with 1.3.2. It's too bad we didn't foresee this and build a check into 1.3.2 to refuse to run or alert you or something, so you are quite correct that this is a usability issue! :( But the problems you got after reinstalling 1.3.2 are no surprise, you really need to restart with a clean, emtpy database then. Thanks, that what we aim for! ;) And luckily for the majority of users it seems to be running to their liking ;) I'd love to understand what's going wrong on your system... But until that point I fear there's not much we can do about it :( [/QUOTE]

Verification