Reply to thread

Message

<blockquote data-quote="edterbak" data-source="post: 541997" data-attributes="member: 69192">It appears to be a database error. WHen I deleted the database file, the error was gone. It returns sometimes, but that is due to configuraion errors on my part....&nbsp; &nbsp; learning this stuff now <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />[edit]I think I found out what happened. I did not read the installation text propperly. I downloade the update and ran that. It worked ofcourse to the level where it tried to create a database file. After I found out that the previous full version needed to be installed, I did so. But ofcourse that means going back to the earlier database files. I read that could give issues, and it did ofcourse. Message I got was like the picture in the first post. Besides the thing I saw because of my own fault, I also tried to fill in *.* in the field for filter file types. This caused a crash numerous times. Deleting the database solved it. It could be something is still not how it is supposed to, but Configurating the plugin is a delecate thing here. One faulty or impatiant click and a database error is present. This results (at least here) in doing the database configuration all over again from scratch. But again, this could be me messing things up. For now I create a backup of the DB file after each step to be sure I dont have to start all over again.</blockquote>

[QUOTE="edterbak, post: 541997, member: 69192"] It appears to be a database error. WHen I deleted the database file, the error was gone. It returns sometimes, but that is due to configuraion errors on my part.... learning this stuff now :) [edit] I think I found out what happened. I did not read the installation text propperly. I downloade the update and ran that. It worked ofcourse to the level where it tried to create a database file. After I found out that the previous full version needed to be installed, I did so. But ofcourse that means going back to the earlier database files. I read that could give issues, and it did ofcourse. Message I got was like the picture in the first post. Besides the thing I saw because of my own fault, I also tried to fill in *.* in the field for filter file types. This caused a crash numerous times. Deleting the database solved it. It could be something is still not how it is supposed to, but Configurating the plugin is a delecate thing here. One faulty or impatiant click and a database error is present. This results (at least here) in doing the database configuration all over again from scratch. But again, this could be me messing things up. For now I create a backup of the DB file after each step to be sure I dont have to start all over again. [/QUOTE]

Verification