Error on deleting article

Next topic

Author	Message
M Tonissen	Wednesday 09 August 2006 8:03:02 am Whenever I try to delete an article in admin screen I get these errors: Fatal error: A database transaction in eZ publish failed. The current execution was stopped to prevent further problems. You should contact the System Administrator of this site with the information on this page. The current transaction ID is TRANSID-3bd0af6bebb8b3a6d5cef1cc4ba13c4c and has been logged. Please include the transaction ID and the current URL when contacting the system administrator. What does this mean and where can I find that log??
M Tonissen	Friday 11 August 2006 4:40:10 am No one can help me with this one???
Matt Brady	Tuesday 15 August 2006 7:06:27 pm I'm having the same problem... however, reading through the forums I found this: The MySQL user needs the CREATE_TMP_TABLE permission. It's not easy being easy.
Marko Žmak	Tuesday 15 August 2006 10:53:12 pm This means that the deletion of the article didn't succeed entriely. But you should provide more details about your problem. What version of eZ, PHP, Apache, MySql are you using? Does the problem happen only when you try deleting an article or it happens with other classes as well? Does the problem happen EVERY time you try to delete an article? Does the same problem happen when you try creating or changing an article? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
M Tonissen	Tuesday 15 August 2006 11:35:14 pm EZ version 3.8 php version 4.4.3 mysql version 4.0.22 webserver version ???? Deleting classes is no problem, the problem concerns only deleting articles, and happens allways. Creating or editing an article isn't a problem and can be done.
Matt Brady	Thursday 17 August 2006 4:24:33 pm I'm still experiencing the same problem after getting the grant set up to allow create_tmp_tables I cannot delete any article, folder, forum etc etc regardless on wheter I created them or not. Specs are as follows: ez version 3.8.3 php version 4.4.2 mysql version 4.1.2 No No No... I tell lies.... the grant wasn't set up properly... that definately fixed the problem :) It's not easy being easy.