Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Have tried following the recommendation to increase this limit, but the value will not save.
Comments
Comment #1
kenorb CreditAttribution: kenorb commentedIs there any error?
Maybe some limit related to shared hosting?
Comment #2
Starminder CreditAttribution: Starminder commentedNo, unfortunately no error. Everything appears to work like it should...except that the new value is not saved and it reverts to the original.
Comment #3
kenorb CreditAttribution: kenorb commentedI'll look closer to this tomorrow and I'll try to fix that.
Comment #4
kenorb CreditAttribution: kenorb commentedIt's fixed in latest dev version.
Comment #5
Starminder CreditAttribution: Starminder commentedOne step forward, one step back. New dev version gives me "Fatal error: Call to undefined function drupal_strtolower() in /usr/home/hoslo/public_html/includes/common.inc on line 1187" when I try to enable it.
Comment #6
kenorb CreditAttribution: kenorb commentedIncluded additional core file during hook_boot:
Updated .module file:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/drupal_twea...
Comment #7
Starminder CreditAttribution: Starminder commentedOK, getting there. Used file above + latest dev, no errors so far. Max Allowed Packet was set to 1k. I tried to change it to 2GB, got the error "Actual MAX_ALLOWED_PACKET is differ than it was set, probably you do not have proper privileges." and it reset it to 1024 MB.
Is that setting good enough?
Comment #8
kenorb CreditAttribution: kenorb commentedYou should set in example to: '4 MB'. It should be enough. If there will be error about privileges, then unfortunately your hosting provider don't allow to change those settings on the fly.
Comment #9
mvcAs of MySQL 5.0.x the variable max_allowed_packet cannot be set per session, and as of 5.0.84 and 5.1.31 the variable is read-only. Setting this at run time only works in 4.1.x and before. This module should detect which version of MySQL is being used and display a message to the user saying that this variable will need to be altered in the server's configuration file my.cnf.
http://dev.mysql.com/doc/refman/4.1/en/server-system-variables.html#sysv...
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysv...
http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysv...
Comment #10
kenorb CreditAttribution: kenorb commentedhttp://forums.zarafa.com/viewtopic.php?f=9&p=7946#p7945
Comment #11
kenorb CreditAttribution: kenorb commentedMarked #779540: Warning: SESSION variable max_allowed_packet is read-only. -- Also, Cannot set variable `max_allowed_packet` as duplicate.
Probably there should be some condition in the code depends of the mysql version.
Comment #12
drupert55 CreditAttribution: drupert55 commentedSubscribed (my issue at http://drupal.org/node/779540)
Comment #13
AlfTheCat CreditAttribution: AlfTheCat commentedsubscribing
Comment #14
kenorb CreditAttribution: kenorb commentedDuplicate: #1077946: Is DB Tweaks deprecated for MySQL 5 and above?
Comment #15
Starminder CreditAttribution: Starminder commentedAny plans for a D7 version? :)
Comment #16
zvischutz CreditAttribution: zvischutz commentedSee http://drupal.org/node/542874#comment-6697196 as a possible solution for this .
Comment #17
websupportguy CreditAttribution: websupportguy commentedI have just had to disable Drupal Tweaks module entirely because it was generating up to three of these warnings on each page of my website. This is very disappointing as the problem has been around for a long time but seems to have been largely ignored. MySQL moved on and Drupal Tweaks didn't. The workaround provided in the last post did not work for me at all.
Comment #18
kenorb CreditAttribution: kenorb commentedClosed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.