Hello! I've just tried to upgrade this module from 1.3 to 2.0rc, but now the same 2.0rc doesn't recognize hi own version! I ran cron.php, update.php and manually checked for new versions of all of my modules, but without success. Please, advise! Thanks!

Comments

merlinofchaos’s picture

merlinofchaos commented

Can you clarify what you mean by "Doesn't recognize its own info"?

Does it...

not appear on the update status page?
appear on the update status page with the wrong version?
something else entirely?

jazzitup’s picture

jazzitup commented

Correct: it appears on the update status page with the wrong (previous) version: 1.3

jazzitup’s picture

jazzitup commented

@merlinofchaos:
I was tired and I have opened several FTP sessions of various locations on my client and it seems that I upgraded the "wrong" Drupal site. I'm sorry man, it's my fault! I'll be your slave! :) lol

jazzitup’s picture

jazzitup commented

Hm... But I'm still experiencing problems. I don't have issues with my Drupal 5.1 installation, but my new Drupal 5.2 installation returns this:

http://phpfi.com/252990?lang=plaintext

merlinofchaos’s picture

merlinofchaos commented

That error indicates MySQL is crashing and is very severe. It is probably not related to update status, though. It might mean corrupt database, or out of disk space, or some other strange problem. It's beyond my ability to help you debug.

jazzitup’s picture

jazzitup commented
Status: Postponed (maintainer needs more info) » Fixed

SOLVED:
What happens is if the MySQL server receives a packet bigger than the size in the config file (my.cnf), it throws an error and closes the connection. PHP then displays the "MySQL server has gone away..".

More info:
http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)