When managing the display settings on a content type that contains a Block Reference field by clicking on the relevant cog, I am presented with the AJAX spinner and "Please wait..." which continues until I get a javascript popup error that says:
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /system/ajax
StatusText: OK
ResponseText:
Fatal error: Maximum execution time of 300 seconds exceeded in /path/to/site/includes/form.inc on line 1870
To replicate on a fresh install of Drupal, download and install Block Reference and Display Suite then enable. Add a Block Reference field to a content type. Go into "Manage Display" for that content type. Click on the cog for the Block Reference field.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | field_format_settings_display_suite_bug_2706797.patch | 2.18 KB | jaydee1818 |
| Screen Shot 2016-04-15 at 11.59.41 AM.png | 99.38 KB | jaydee1818 |
Comments
Comment #2
rudiedirkx commentedI don't use Display Suite, (and I rather not install it). Are you up for some debugging? If not, I'll do it later, but I can't say when...
Comment #3
jaydee1818 commentedI'm happy to help fix it but not sure where to start
Comment #4
jaydee1818 commentedThis patch fixes the problem for me. I simply altered the implementation of hook_field_formatter_settings_form() in blockreference.field.inc so that the variable names match what is outlined in the API documentation here: https://api.drupal.org/api/drupal/modules!field_ui!field_ui.api.php/func...
I suspect there was a clash going on. Please review.
Comment #5
jaydee1818 commentedComment #6
rudiedirkx commentedI've never understood that hook. One of the arguments is
$form, which is the basis of the form you're building. But you're not supposed to use it!? Form hooks have that too: an argument$formthat's supposed to be empty.With your patch, the Views hack isn't necessary anymore either. That sounds like a good deal.
Comment #8
rudiedirkx commentedThanks!