Hi,
First of all, yes, I read all the earlier posts and documentation dealing with the header information issue (it's suposed to be some sort of blank spaces at the end of the file) but it's not running for me. Cleaning the file is not getting away this message, and when I try to do it now I cannot see any blank space after the end of php tags on file common.inc (see below).
Anyway, here is my error log, and I hope some of you guys could point me to the right solution:
user error: Access denied for user: 'drupal@localhost' to database 'drupal'
query: LOCK TABLES sequences WRITE in /home/httpd/vhosts/damaine.name/httpdocs/includes/database.mysql.inc on line 90.
warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/domain.name/httpdocs/includes/common.inc:63) in /home/httpd/vhosts/domain.name/httpdocs/includes/common.inc on line 481.
where domain.name is my domain name.
Regarding the database issue, I took the mysql scheme file (database.mysql) and uploaded it thru phpmyadmin. I couldn't manage anything about permissions (as installation documentation said) but drupal was running so I didn't worry about it.
Do you know if my problem with database access is a real problem or something related with the second error? It's a clean installation and I'm able to post comments, new nodes, or anything, but somethimes I get these errors and no information how to deal with them.
My MySQL version is 4.0.24.
One more piece of information. After posting a comment and receiving the error I gave you, if I go back and press submit again, what I receive is the next message:
Duplicate comment
The comment you submitted has already been inserted.
So, if this message is shown (and in fact the comment is there), why am I getting the earlier write-in-database error? If there is a problem writting into the database, comment shouldn't be there, should it?
I also did a flush privileges; and the answer is RELOAD privileges.
Someone can explain me what can I do???
Thanks i ¡n advance for your time.
Comments
I had the same problem
I had the same problem recently and this post node/17241 explains the issue.
I had to contact my ISP and have them grant LOCK TABLES priviledge on my database and then everything worked great (but as you read the post, you will note that not every ISP is so generous).
Hope that helps.