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.
The Token Browser seem's not to work as attended, when clicking on the "Browse available tokens" link under a default value input, an overlay div appears and display "Loading token browser..." without any evolution.
In the past version, actually i've only tested with the alpha6 version, it was working great, we could use the usual token tree browser.
However the token works with a manual entry.
Tank you for your great work.
Comment | File | Size | Author |
---|---|---|---|
#12 | error.png | 49.46 KB | RaulMuroc |
Capture d’écran 2013-07-24 à 17.44.46.png | 62.46 KB | dom18fr |
Comments
Comment #1
quicksketchYour server is probably running out of memory when generating the token list. If you have installed Rules (with Entity Token) your server probably doesn't have enought memory to generate the list of tokens. Try increasing the PHP memory limit or (if possible) disabling Entity Token.
Comment #2
quicksketchPlease reopen if this solution doesn't work.
Comment #4
RaulMuroc CreditAttribution: RaulMuroc commentedReopen cuz not solving.
Comment #5
quicksketchCould you elaborate here? The best thing to check is to use a network inspector like Firebug or the tools in Chrome to see what's happening during the AJAX request to load the token browser. Usually what happens in this case is the AJAX request fails with an HTTP 500 error and Token module doesn't pass on the error to the user, instead it just doesn't load.
While using the inspector, it's a good idea to check for JS errors as well.
Comment #6
dimmech CreditAttribution: dimmech commentedSame thing happening here.
This was the error in firebug.
"NetworkError: 403 Forbidden - http://mysite.com/token/tree?options=%7B%22token_types%22%3A%5B%5D%2C%22global_types%22%3Atrue%2C%22click_insert%22%3Atrue%2C%22show_restricted%22%3Afalse%2C%22recursion_limit%22%3A3%7D&token=vRn9Upr4kqil6C2fcgmXT5O-u3IGFeFD-FSeYLB7ohY"
Comment #7
joseph.olstadI've seen this browse token problem with a version of the 'ember' admin theme and most likely not caused by this module (unless a possible css conflict). There is a patch for the 'ember' admin theme is available related to this issue (fix is to css values ) however if it's not ember you're using try a different admin theme just to test it such as the bartik theme or one of the other common ones. this might help you isolate the problem to determine what is actually causing it. Is it the admin theme? is it your custom css, is it the webform css ? use the browser debug tools built into Firefox or Chrome .
Comment #8
DanChadwick CreditAttribution: DanChadwick commented@dimmech -- I'd look at why the token module is return a 403.
Comment #9
DanChadwick CreditAttribution: DanChadwick commentedComment #11
RaulMuroc CreditAttribution: RaulMuroc commentedNothing is fixed. Errors persists.
Comment #12
RaulMuroc CreditAttribution: RaulMuroc commentedComment #13
DanChadwick CreditAttribution: DanChadwick commentedhttp 500 errors are almost certainly not directly related to webform, but rather to server configuration, such as memory. You'll have to debug this one yourself, I'm afraid.
Also, be sure to use the latest version of webform.
Comment #14
RaulMuroc CreditAttribution: RaulMuroc commentedok thanks!
Comment #15
ebren CreditAttribution: ebren commentedI was experiencing the same issue with the token browser on the url patterns admin page running the adminimal theme on a local (xampp) environment. In my case, the problem was I was using spaces in my directory names. Changed the directory path spaces to dahses and voila. I
Comment #16
tory-w CreditAttribution: tory-w as a volunteer commentedI know I'm a little late to the party, but there is a fix. As "quicksketch" said above, your server is running out of memory. Aside from increasing PHP memory, you can use the "Token Tweaks" module. https://www.drupal.org/project/token_tweaks.
What this does is allows you to set the depth of the token tree in order to save memory. The site I am working on is HUGE. So, I set mine to a depth of "2" and I can see the tokens. If you need a deeper depth, it is useful to understand the naming convention of tokens. For a simple example, with Token Tweaks set to 2, I can see node:field-entity-reference-node. But, if I need the Nid, I put in node:field-entity-reference-node:nid
Hope this helps someone else!