Drupal 7.14, DS 7.20, php5.3.20. I have a site with 8 content types, which using DS, in display mode, use 180 added DS block fields. I get an Ajax 200 error when I try to modify the fields on the page. I AM able to move them within regions (but then changes will not save), I cannot move a field to another region, add a new field, or even change display mode from DS 2-col stacked back to "none".

The error evidently derives from line 312 in ajax.inc when calling $form_build_id = $_POST['form_build_id'];

What makes this interesting is that I have installed the identical drupal core and modules on my dev server (a laptop) and another host (iPage - php5.3.13) where I AM able to make those changes - it works. Thus, it is probably NOT the module(s), or the code, but how long it takes to do the callback, or something at the host - (database access maybe?). Memory at hosts is 256MB (I am told).

I seek is advice on:

1. what to tell/ask my host (Hostpapa) to get it to work on their servers;
2. How to disable ajax on my DS so that I can modify my nodes and the display on my content types; or
3. What alternatives I have to DS to use fieldgroups and views blocks in my nodes if I am unable to effectively use DS.

Thank you very much for any advice an experienced developer can provide.

Hamish

Comments

Category:bug» support

There are 3 things you need to check:

1. Are you using Memcache?
Make sure you have this line in your settings.php:
$conf['cache_class_cache_form'] = 'DrupalDatabaseCache';

and not this line:
$conf['cache_class_form'] = 'DrupalDatabaseCache';

carefully note the difference. The 2nd line is wrong and used to be posted like this on the project page and in the README.txt file of the memcache module.

2. Is the post_max_size setting high enough in your php.ini file?
Try to increase it and see if this makes a difference. Go really REALLY high, just to be sure this is not it.

3. Is the max_input_vars setting high enough in your php.ini file?
By default this is set to 1000 if I'm correct. Try to increase it and see if this makes a difference. Go really REALLY high, just to be sure this is not it.

Make sure you try everything separately. It could be that it's only 2 or only 3, but it could just as well be a combination of everything together.

As the DS pages get quite big easily the problem is most likely 2 or 3 or both.

Status:Active» Closed (works as designed)

180 fields are quite problematic, that's something that even't core can't handle nicely in Field UI, so I'm afraid there's not much I can do here to help.