Problem on nodes with a lot of paragraphs

Created on 7 September 2023, over 1 year ago
Updated 27 February 2024, 10 months ago

Problem/Motivation

Hello everybody. Were having a big issue trying to edit a node called "course".

This node have a field called "chapters" type paragraph and multiple. The paragraph "chapter" have a field called "lessons" type paragraph and multiple. The node and paragraphs have also another fields (texts, number...).

We had no problem till now that were trying to create a big node. When we are getting close to 80 lessons (distributed in the chapters) we get the next behaviour:

- We try to add a new lesson/chapter or delete one

- When the ajax call (/es/node/{id}/edit?ajax_form=1&_wrapper_format=drupal_ajax) ends the lesson/chapter field dissappeared, or thee lesson added to a differente chapter, ... weird things happen

Version

Drupal core version 8.7.5

Paragraph version 8.x-1.8

🐛 Bug report
Status

Active

Version

1.8

Component

Code

Created by

🇪🇸Spain Manuel Ortiz

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Manuel Ortiz
  • 🇳🇱Netherlands idebr

    If this only happens as your node grows, you might be hitting the Apache headers limit. See 🐛 FinishResponseSubscriber: Need warning/error when headers exceed 16k Needs work

  • 🇪🇸Spain Manuel Ortiz

    Thanks for the answer @idebr.

    I don't think the headers are the problem, it is not too big. The payload is. It can be 160kb.
    Also the biggest problem is there isn't a single clue. Apache logs are ok, drupal logs too. The ajax responses a 200. Everything looks normal.

  • 🇳🇱Netherlands ecvandenberg

    Hi Manual, we use nodes with up to 600 paragraphs! Well...we are expecting 600 paragraphs. We are now around 250. It all seems to work fine, but we are experiencing issues too.
    We have many users that own this type of node and can add paragraphs. Some of them experiencing that not all newly added paragraphs are stored, when saving the node. They must save after every paragraph added to be sure it's stored.

    I try to get it more clear but can not reproduce yet. I bumbed into this issue, perhaps it's related.

Production build 0.71.5 2024