I think all of these have visible symptoms - like pages throwing exceptions. These problems could be caused by a bug now fixed in Elgg, by someone deleting things in the database without understanding the schema, by the database crashing in the middle of an operation. You can always use the validate button to see if anything comes back. I wrote that when I first released it and wasn't sure if it might cause problems. After many happy customers, I feel more confident in this.
thx for update this plugin but after activating the Database Validator I getan Internal Server Error. After deleting the dbvalidator folder it says:
dbvalidator (guid: xxx) cannot start and has been deactivated. Reason: Cannot include start.php for plugin dbvalidator (guid: xxx) at /.../mod/dbvalidator.
What does it mean? Useing elgg 1.8.1 and db validator 1.4
It seems unlikely that this plugin caused a 500 error (internal server error) just by being activated. You are welcome to follow the instructions on this page (http://docs.elgg.org/wiki/White_page) about turning display errors on and report back on that.
As to the other error - that's an Elgg thing and happens when you delete an active plugin.
@Cash I have found the error. After moving the dbvalidator plugin to bottom of the plugin list - it works like a charm. But when I moved the plugin to the top of the list it occurs the 500 error. Is it just me, or? If not a short Info under the "more info" section would certainly beuseful?!
Can you turn on display errors and see what error message is displayed when it is at the top of the list? The developers plugin distributed with Elgg has the option to turn on display of fatal errors.
funny, aftertheerrorwasthree times present the fourth and fifth issometimes with nomoreerrors?!? Icannotreproduce anymore. I am at my wit's end. Now I have thepresumptionthatithasnot at alllocated onyourplugin, embarrassing. Iwilldeletemycomments, or?! I'm sorry.
How can the admin determine the database is having any issues? Any symptoms of wierd behaviour?
I think all of these have visible symptoms - like pages throwing exceptions. These problems could be caused by a bug now fixed in Elgg, by someone deleting things in the database without understanding the schema, by the database crashing in the middle of an operation. You can always use the validate button to see if anything comes back. I wrote that when I first released it and wasn't sure if it might cause problems. After many happy customers, I feel more confident in this.
thx for update this plugin but after activating the Database Validator I get an Internal Server Error. After deleting the dbvalidator folder it says:
What does it mean? Useing elgg 1.8.1 and db validator 1.4
cheers
It seems unlikely that this plugin caused a 500 error (internal server error) just by being activated. You are welcome to follow the instructions on this page (http://docs.elgg.org/wiki/White_page) about turning display errors on and report back on that.
As to the other error - that's an Elgg thing and happens when you delete an active plugin.
@Cash I have found the error. After moving the dbvalidator plugin to bottom of the plugin list - it works like a charm. But when I moved the plugin to the top of the list it occurs the 500 error. Is it just me, or? If not a short Info under the "more info" section would certainly be useful?!
Anyway, a very helpful pluging.
cheers
Can you turn on display errors and see what error message is displayed when it is at the top of the list? The developers plugin distributed with Elgg has the option to turn on display of fatal errors.
funny, after the error was three times present the fourth and fifth is sometimes with no more errors?!? I can not reproduce anymore. I am at my wit's end. Now I have the presumption that it has not at all located on your plugin, embarrassing. I will delete my comments, or?! I'm sorry.