I have been using the Flag module for many projects and I have never had this happen. I am not sure if this is module that I added to the site that might be conflicting with the build I am making, but I wanted to ask and see if anyone is having the same problem. Any insight would be helpful, thank you for your time.
Initially I was receiving an error of out of memory, allocated x and cache went over... I tried removing the module Flags, uninstalling it, and re-enabling the module. The screen shot that I uploaded is from this procedure.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | flags_uncaught_exception-2595079-7.patch | 908 bytes | omessaoudi |
| #4 | flags_uncaught_exception-2595079-4.patch | 937 bytes | omessaoudi |
| flagsError.fw_.png | 475.13 KB | Bishupz1 |
Comments
Comment #2
joachim commented'MySQL gone away' is to do with your database configuration -- google for that error message, there are various fixes to try.
Comment #3
Bishupz1 commentedThank you for the quick response... I am sure you see many a message not regarding flags itself. It was just odd to me that something either altered the construct of the site that I was building, database wise, or flags association. The best thing I could come up with was that tokens was overloading the edit page rendering to the point where the database timed-out. oddly nothing had been done with flags for months on the build, and then there was no ability edit the flags thought the previous setup flags worked fine; just nothing could be added or edited. the site is using a good amount of modules, so I could see some aspect of the site altering the way in which the module was called (database wise). The best solution I could find out there was that something/another module was closing the connection. I am probably going to have to go off of a previous build where the flags ability to be edited is working, and build the site backup to its current structure. To see if i can avoid the module, bad view, or what ever triggered this 'MySQL gone away'.
Comment #4
omessaoudi commentedHello,
I have had the same issue and in my case, it was caused by an important number of tokens present in my Drupal installation.
As improvement, could we add the "dialog" option when calling "theme_token_tree" function? Here is a patch for this.
Thx.
Comment #5
omessaoudi commentedComment #7
omessaoudi commentedPatch correctly generated.
Comment #8
omessaoudi commentedComment #9
joachim commentedThanks for the patch!
(Though please remember to update the issue type and title when more details about a problem are discovered.)
> As improvement, could we add the "dialog" option when calling "theme_token_tree" function? Here is a patch for this.
Can I ask how that improves things? I can see that it would mean the flag edit form won't crash, but won't the popup dialogue still crash?
Comment #10
omessaoudi commentedHello,
Sorry for not having updating issue attributes.
It is a improvement in the way that by now (without Dialog option), not all flags need tokens, but if Token crashes, there is no way to add any flag even if this one does not need tokens.
With the Dialog option, if there is a MySQL crash due to Tokens load, this will not have incidence on adding/updating a flagging type page as tokens loads will not occur when loading the the main page, but only eventually when the user will want to browse Tokens.
Comment #11
zerolab commented@joachim see http://drupalblog.torchbox.com/post/96035252861/fixing-out-of-memory-iss... for background information
Moving to RTBC as it is a straightforward fix.
Comment #13
joachim commentedThanks everyone!
Committed.