This is good idea but it will hit the traditional drupal problem with too many forms loading on an edit page, which will cause frontend hangs.

Comments

frans’s picture

And this is a bug?
Can you give reproducible steps... it cannot be tested without those.

jeroen.b’s picture

Status: Active » Postponed (maintainer needs more info)
loparr’s picture

Category: Bug report » Feature request
loparr’s picture

I changed status to feature request if you like. Please take look here https://drupal.org/comment/7412696#comment-7412696

jeroen.b’s picture

I think the only solution to this is to display an "Edit" button before actually showing the fields, like Inline Entity Form. Is this something you would like? I might make this an instance setting when people actually want it. The idea of paragraphs is also that you can see very quickly what is in your body. As Paragraphs is meant as a re-invented body-field.

loparr’s picture

Hi, displayying edit button before printing all possible forms seems to me as an good idea.

agoradesign’s picture

+1 for the edit button!

jeroen.b’s picture

Added this in commit http://drupalcode.org/project/paragraphs.git/commit/4247ecd

This adds an option on your field instance "Default edit mode", 2 options: "Open" and "Closed".
Open is the old behavior (all fields showed on the initial form), and the default.
Closed is the suggested mode, the fields aren't shown until you press the "Edit" button.

You can test it by checking out the tag 7.x-1.x-dev-editmode (or 7.x-1.x-dev from the paragraphs project page, not sure if it's updated yet), please do so! If it's OK I will release beta3 with this functionality.

jeroen.b’s picture

Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

nicolas bouteille’s picture

Title: good idea but » Paragraph Items can be Open or Closed on node Edit form
Status: Closed (fixed) » Needs work

Hi,

I just tested the feature.
I installed dev version over beta2 already installed.
I tested this on a content type already configured with a field of type Paragraph and one simple paragraph bundle (text block).

First of all, there is one thing very useful missing from Inline Entity Reference : an ID string (administrative title) to identify each item so that reordering of multiple items of one same bundle type is possible.

Now, no errors at first site but when I clicked on the edit button, I got an AJAX alert error. The message is in French but mainly it says that
an AJAX error occured
Status code HTTP 500
Path: /fr/paragraphs/edit/ajax (maybe your module does not handle language prefixes!?)
Status text : service unavailable
ResponseText : EntityMalformedException : missing bundle property on entity of type node in entity_extract_ids() line 7721 includes/common.inc

jeroen.b’s picture

Hi Nicolas,

That issue is not related to this feature, or to not handling language prefixes (that's something in core).
I'll try the upgrade from beta2 to current dev soon.

I agree with you on administrative title, although it might be very annoying if you have to come up with a administrative title every time you create a paragraph. Would the Entity ID be enough (not very pretty though)?

nicolas bouteille’s picture

Then administrative title could be optional ;)

jeroen.b’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.