When a feature gets really large, it can exceed the php.ini max_input_vars limit. This results in features trying to write the export to the server drive instead of downloading an archive to the users computer.

I spent several hours confused about this. Why was features trying to write the code to the server disk instead of downloading like my local instance did? I wasn't clicking the generate feature button, I was clicking the download feature button.

It took me a while to remember to check my php error log, I guess I assumed all the error messages drupal was showing was all I would get. But I eventually did see:

drupal: PHP Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in Unknown on line 0

(Seriously, why didn't that error show along side all the "Warning: file_put_contents..." error messages?)

Once I increased max_input_vars, it worked normally.

Can Features detect that warning and set a useful message when it occurs?

Shouldn't Features just fail to generate anything in this case? It doesn't really make sense to me for it to try and save the code to the server disk, unless you are clicking the generate feature button.

Comments

jerrac created an issue.