Out of the discussion at Dublin, we would like to formalise approval of all of the Phase 2 issues. We have informally discussed this approach and it was approved so this is just to document the approval separately so it's not lost in a sea of comments.

Proposal roadmap: Phase 2

Bring in features from contact_storage and finalise those missed in D8.0.

  1. #306662: Add redirect option to site-wide contact forms
  2. #2750613: Add option to store messages from contact forms
  3. #2750617: Add views integration and listing page for contact module Message entity.
  4. #2750621: Add bulk delete action plugin for contact module Message entity
  5. #2750629: Add view builder for contact module's Message entity
  6. #2750627: Add Edit and Delete forms for contact module Message entity
  7. #2750633: Add view builder for contact module's ContactForm entity
  8. #2689265: Allow changing the 'Send message' contact form string and optionally hiding the preview button
  9. #2750649: Add option to disable form submissions for contact forms

Required sign-off before proceeding this

Owner Status Description
Product manager
@Dries or @webchick
Pending
Release manager
@catch and/or @xjm
Pending

Comments

pameeela created an issue. See original summary.

naveenvalecha’s picture

Issue summary: View changes

Thanks @pameela
Updating issue summary with the sign off table. I have added the signoff needed by a framework manager as the issue was tagged with Needs release manager review Feel free to update the issue summary if its not needed.

// Naveen

naveenvalecha’s picture

Issue summary: View changes
webchick’s picture

Status: Active » Postponed (maintainer needs more info)

In order to provide sign-off here from a product management POV, I need a bit more context as to what these features mean in terms of end-user facing functionality. What are the problems currently? What will the list of features get us at the end? Why do we think that's the right stuff to work on, and in the right order?

pameeela’s picture

My understanding is it's porting the basics of contact storage into core, in order to lay the groundwork for future features.

@jibran, @larowlan, @berdir can provide more context.

jibran’s picture

What are the problems currently? What will the list of features get us at the end? Why do we think that's the right stuff to work on, and in the right order?

I think we covered all that during our call on Fri 3 Jun 2016 or Thu 2 Jun 2016 for @xjm and @webchick. These are all those issues we specifically discussed on the call with @webchick and @xjm. We just want to get the formal approval on that.

If you still need further information then we can setup another call.

jibran’s picture

Status: Postponed (maintainer needs more info) » Active

Changing a status to get a reply.

askibinski’s picture

Just wondering if the problem of scaling was discussed in the process.

It was mentioned by larowlan here about a year ago:

Forms with lots of fields. Each field is a config object and this can increase the size of your fieldmap, as well as the number of tables. Webform stores its data in a single table, Field API stores fields in one-table per field. There is obviously a storage and performance implication there (This is the same issue with entityform in D7).

and:

Lots and lots of forms. Each contact form is a new entity-type bundle so adding lots is equivalent to adding lots of content types. (This is the same issue with entityform in D7).

Can't find discussion about this in the issue queues but it does seem to be one of the reasons people are choosing yamlform instead of contact + contact_storage.

fenstrat’s picture

@askibinski Many forms/fields is indeed an issue for contact & contact_storage, however I believe that would fall into the 20% usecase for webform (FYI yamlform looks set to rename to webform).

Gábor Hojtsy’s picture

I think we covered all that during our call on Fri 3 Jun 2016 or Thu 2 Jun 2016 for @xjm and @webchick. These are all those issues we specifically discussed on the call with @webchick and @xjm.

is it possible to inform others or should @webchick and @xjm be the ones who are informed on calls only? You can imagine people will look at this, its a public posting and wonder what are the problems being solved, etc. That @webchick and @xjm have been told on a phone call sounds good, but not very informative unfortunately :/

yoroy’s picture

Component: Plan » Idea

In light of Webform being alive and kicking for D8, I wonder if that changes the desire/need for this. What do people think?