Form creation is very slow on 100+ field forms

This is likely just a problem with the Field API, which is what Entityforms, node, users, terms, etc use.. I personally have never had that many fields on any entity.

To test you could add that many fields to a test content type on a test copy of your site. You could use Field Tools quickly copy the fields.

Though I pretty sure you would have the same problems.

What kind of server/resources are running Drupal on?

Postponing this b/c we need more info

@Qandeel sorry to say but 100 field might too fields. I am pretty sure that 300 fields is too many so this module will probably not work in that case especially if you cannot increase the memory limit.

Checkout When to Use Entityforms. It might need something on field limits.

it might be usefull to revisit this section and move it on some other tab just like "validation rules" and "submission rules" Most of the time user does not want to add token to the body field of entity types so lets put it as suggestion to move it to separate tabs.

@Qandeel, so just to clear you suggesting moving the token browser off the entityform type edit form?

Sorry I think it is much more common for people to want to have access to all tokens than to have 100+ or 300+ field on the form. Tokens can be used in various places on the entityform type edit form.

The token browser will not work the same way if it is on another tab. You are able to click token and it shows in the last form element you were in. That would not work from another tab.

The problem with having so many tokens because of so many fields is not limited to the entityform type edit form. This will be a problem anywhere the token browser is displayed. For instance the token browser is used extensively in the Rules module.

A solution for your problem would be to implement hook_form_entityform_type_form_alter and remove the $form['tokens'] element.

As far as revisions please checkout #2021009: Add revision support to submisions.
Please keep each issue focused on 1 topic

Also just in-case others find this issue I would not recommend using this module with 300+ field forms with this modules. Webform is a better module in that use case.

@Qandeel, this might not help in your case since obviously you have already invested a lot of time making these forms.

@Qandeel if you are not using Rules then you could upgrade to Entityform 2.x. That would allow you to disable Rules and entity_token module. I think disabling the entity_token module would reduce the number of tokens created by the token browser

re: #1954464: Memory Issue

Looks like the Token Tweaks module might help you out.

I also have the issue of very slow form and memory getting exhausted at 313 fields. Memory (256 MB) gets exhausted when trying to create a new field. It didn't help to install Token Tweaks and set "Maximum depth limit for the token UI" to 1 - This is the only tweak Token Tweaks currently delivers. Any other ideas?

@rosell.dk I don't think this module(or any other entity type) can handle that many fields. Of course more memory will increase the number of fields but I don't know what the limit will be.

For other users in the future I have created a sandbox project Field Max.

It simply allows easily creating any number of text area fields on a bundle. It could be used to test out the number fields that a system might be able to handle.

I have added a warning and a link to this issue on the module project page.

If someone would take the time to update this issue summary so that new users could get an idea of the issue right away that would be great!

I working on web based diary,

In the diary there are 21 days where every day is a Parent 'Group' with field type Vertical tab. Every day has 16 fields which are same for every day, total of 336 fields.

I am able to create successfully 17 days without any problem but after that I am not able to assign fields to any parent 'Group'.

after selecting parent and clinking save it reload the page without saving the configuration.

There is no error or any message to help identifying the problem, I am new with Drupal and don't have any idea why it is happening, I try Google and couldn't find any information that could help.

I was wondering if this is something to do with entity forms limitation on the number of fields/group.

@yfarooq I would suggest not making the dairy the way you are suggesting I think you will run into many more problems.

It would seem to make a lot more sense to use Entity Reference to connect a child Day entity to parent Dairy entity.

Or you could use field collection where you have 1 feild collection fieild on Dairy then limit that to 21 items.

I have more than 100 fields on the entity form and adding more fields make it slower and slower.. any idea why is it like this

For huge surveys (more than 100 fields), you can use the Limeurvey Sync module : successfully tested with 700 fields; note that it does not correspond to 700 fields in the field core module but 700 questions.

Webform worked well for me for large data forms. I've exported 800 fields successfully for one project.

So the info should be taken of from the Project Homepage, if this issue is fixed now.

@kenorb the support request was fixed but I still think the warning on the home page:

Do not use Entityform for forms that will contain 150+ form elements

Is correct.

I still would not recommend Entityform if you have that many field.s