2

On a site that heavily uses Drupal core's taxonomy, we are encountering serious problems when editing content: Already entered taxonomy terms are not properly loaded into the node editing form; fields that should contain values are rendered empty; when the nodes are saved, the terms are lost. So this is not a display issue.

Please note: Some terms are not loaded into the node editing form. We know exactly which terms should be there because a View displays the terms in a structured fashion.

I am aware that Drupal inherits multiple issues with large forms from PHP; for example, large user permission screens are not being saved in Drupal, because PHP has a default value for 'max_input_vars' of '1000'; by increasing this value, e.g. to '1500', Drupal becomes able to save user permissions again. We'Re supecting something similar with the node editing screens. However, in our case, values are not even inserted from the database into the node editing form, so it's totally unclear where to even start looking for a solution.

The environment:

  • Drupal 6 (Pressflow)
  • Around 110,000 nodes
  • 24 vocabularies with > 100,000 terms

Also noteworthy: The problem with incomplete node editing forms is not limited to taxonomy terms; it sporadically also applies to other form elements like attach images.

Are there any PHP configuration values that could cause this misbehaviour or does Form API have any hard limits in redard not the size of node editing forms (e.g. number of form elements per form, memory limits per node editing form)?

  • Do you have any custom code in relation to your node forms? – rooby Oct 7 '14 at 4:14
  • 3
    This question appears offtopic because it's a bugreport for PressFlow. Bugs belong to issue queue, not here. All terms should be loaded, we are literally unable to debug your site and tell why they are not for you. Try to use devel module, identify offending query. Maybe then we'll be able to help. – Mołot Oct 7 '14 at 5:34
  • @rooby: No, we do not use any custom code on the node editing forms. Also, the default forms are not overriden by a contributed module like Panels. 1 This question appears offtopic because it's a bugreport for PressFlow. Bugs belong to issue queue, not here. All terms should be loaded, we are literally unable to debug your site and tell why they are not for you. Try to use devel module, identify offending query. Maybe then we'll be able to help. – Mołot 6 hours ago – user153878 Oct 7 '14 at 12:20
  • @Mołot: This problem is not a Pressflow issue; you can exchange Pressflow with a vanilla Drupal core and it shows the same behaviour. Why do you think that there is an "offending query"? – user153878 Oct 7 '14 at 12:27
  • Are the taxonomy terms being edited using SELECT elements? This could simply be a browser issue if you are trying to load huge forms. Are the forms complete if you pull the page source using wget or similar? – Alfred Armstrong Oct 7 '14 at 12:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.