Hello, I got an Issue where I got some Error messages each time after activating modules on the module page.
Later I had another problem with this on a messed up page and so I looked into it.
As soon as I deactivated Admin menu I did not get this error any more.
Since I needed to restore the database anyway (to a time where I did not have this problem very often) I decided I can live with this issue since it seemed to work besides when i activated a module (I had to reload the page 2-3 times and the error disappeared).
(tried the dev version about 4 weeks ago, can not remember the Version number, and the version 1.5 I was using initiallly. got the error with both!)
Now (no idea why) I get that Error each time I'm in the Admin section of my page. The only thing I did before the error appeared each time was to set up a new view (that is not called in the admin section of my site) and I added a new content type.
Here it is:
Warning: Got a packet bigger than 'max_allowed_packet' bytes query: INSERT INTO watchdog (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', '%message in %file on line %line.', 'a:4:{s:6:\"%error\";s:12:\"user warning\";s:8:\"%message\";s:1651166:\"Got a packet bigger than 'max_allowed_packet' bytes\nquery: UPDATE cache_menu SET data = 'a:2:{s:4:\\"tree\\";a:11:{i:2214;a:2:{s:4:\\"link\\";a:37:{s:14:\\"load_functions\\";N;s:16:\\"to_arg_functions\\";N;s:15:\\"access_callback\\";N;s:16:\\"access_arguments\\";N;s:13:\\"page_callback\\";N;s:14:\\"page_arguments\\";N;s:5:\\"title\\";N;s:14:\\"title_callback\\";N;s:15:\\"title_arguments\\";N;s:4:\\"type\\& in /kunden/282362_22848/webseiten/drupal/includes/database.mysqli.inc on line 128
The webhoster I assume has 1MB as limit on the max_packet_allowed (if I remember right) but there should be no way Admin menu is eating up so much space is there? Any way to avoid this?
To be specific, I do get this error ONLY with Admin menu on! So I suppose a bug here !
Since this is a very useful module and I do not know about posssible securety problems related to this bug I set this to critical.
Comments
Comment #1
sunThis is a known issue with 6.x-1.x and the reason for why 3.x has been developed.
Comment #2
Bricks and Clicks MarketingI just had this problem, upgraded from 1.x to 3x.alpha4 and still got the error on about half the pages on the site (after clearing caches). The error was irritating enough that I restored an older database. Would this error appear if I installed 3.x directly, rather than upgrading from 1.x?
Comment #3
Bricks and Clicks MarketingComment #4
sunSee #1.
Comment #5
timtunbridge commentedI initially had this same issue but found that uninstalling and reinstalling the latest dev release fixed the issue.