Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • " Debugging information follows." - post it. Look in watchdog, in server's logs etc. Commented Sep 5, 2014 at 14:32
  • That's the thing - it says 'error', yet there are no AJAX errors after checking logs/posting to dblog. I initially thought it might have something to do with execution_limit, however the response code is a 200. Commented Sep 5, 2014 at 14:34
  • @AdamThomason Additionally you can see ajax request/response with Firebug extension(Console tab) Commented Sep 5, 2014 at 15:23
  • I've tried firebug too, but with no luck! I'm beginning to think it's something down to my vagrant configuration, although surely this wouldn't only affect one AJAX request! Commented Sep 5, 2014 at 15:28
  • @AdamThomason what it shows? Commented Sep 5, 2014 at 15:42