Skip to content

Conversation

@reintjanhoiting1
Copy link
Contributor

Changes proposed in this Pull Request:

  • Lets expand the form block, add a new option allowing folks to collect marketing consent for their contact forms.

Jetpack product discussion
N/A

Does this pull request change what data or activity we track or use?

  • It adds 1 metadata field to the “feedback” post type.
    Testing instructions:

test case 1

  1. Go to Posts > Add New
  2. Search for ‘form’.
  3. Select any of the form types
    image

test case 2

  1. Perform test case 1.
  2. Select the form block.
  3. Click on add “add email permission request”.
    image
  4. Select the “Mention that you can email”
    image
  5. See the new implicit “consent” form element is added to your form.
    image
  6. Go to the preview, see the new implicit “consent” form element is added to your form.
    /Todo WIP/
  7. Fill in a form entry, select the consent.
  8. Find the new entry on the feedback page.
    /Todo WIP/

test case 3

  1. Perform test case 1.
  2. Select the form block.
  3. Click on add “add email permission request”.
  4. Select the “Add a privacy checkbox”
    image
  5. See the new explicit “consent” form element is added to your form.
    image
  6. Go to the preview, see the new implicit “consent” form element is added to your form.
    /Todo WIP/
  7. Fill in a form entry, select the consent.
  8. Find the new entry on the feedback page.
    /Todo WIP/

@jetpackbot
Copy link
Collaborator

jetpackbot commented Aug 5, 2020

Warnings
⚠️ "Proposed changelog entry" is missing for this PR. Please include any meaningful changes

This is an automated check which relies on PULL_REQUEST_TEMPLATE. We encourage you to follow that template as it helps Jetpack maintainers do their job. If you think 'Testing instructions' or 'Proposed changelog entry' are not needed for your PR - please explain why you think so. Thanks for cooperation 🤖

E2E results is available here (for debugging purposes): https://jetpack-e2e-dashboard.herokuapp.com/pr-16723

Generated by 🚫 dangerJS against 3cb9b52

@jeherve jeherve added [Status] In Progress [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it [Feature] Contact Form [Pri] Normal labels Aug 5, 2020
Copy link
Member

@jeherve jeherve left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for that PR!

I've left a few comments below. Do you think you could rebase that branch against master? It's a bit hard to review right now since it includes quite a few unrelated commits. I've rebased the feature branch just now.

@jeherve jeherve added [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. and removed [Status] In Progress labels Aug 5, 2020
leogermani and others added 2 commits August 5, 2020 14:05
* add async call class to connection package

* add docs to the new class

* Async XMLRPC Requests: Simplifying the code.

Combining the `multisite` and `single-site` functions into one to improve readability.

Co-authored-by: Sergey Mitroshin <[email protected]>
@reintjanhoiting1 reintjanhoiting1 force-pushed the add/form-email-marketing-consent branch from 7647030 to a64f5e0 Compare August 6, 2020 07:06
mmtr and others added 2 commits August 6, 2020 10:35
* Adds support for saving the content of a donations block into the post content, so the published view contains the block output.
* It also follows up Automattic#16593 (comment) and implements the content sync logic as suggested there.
Automattic#16724)

* Add basic scaffold for premium nudge

* Add documentation to code.

* Remove testing check and use check for avaiabiliity

* Update extensions/blocks/social-previews/editor.js

Co-authored-by: Damián Suárez <[email protected]>

* Update extensions/blocks/social-previews/editor.js

Co-authored-by: Damián Suárez <[email protected]>

* Remove testing comment

* Normalize to a single button and onClick action

Co-authored-by: Damián Suárez <[email protected]>
@reintjanhoiting1 reintjanhoiting1 force-pushed the add/form-email-marketing-consent branch from f14f5c9 to f9e3d56 Compare August 7, 2020 11:29
sergeymitr and others added 3 commits August 7, 2020 12:25
…c#16736)

Methods `is_active()`, `activate_monitor()`, and `deactivate_monitor()` have not been used since Jetpack 4.2. Marking them as deprecated now.

The WP.com endpoint `jetpack.monitor.getLastDowntime` is not tied to any particular user, so using `blog_token` is sufficient.
Replacing the `user_token` with `blog_token` for that API request.
…16758)

The API request `jetpack.protect.requestKey` does not use the user ID, and can be authenticated using `blog_token`.
@reintjanhoiting1 reintjanhoiting1 force-pushed the add/form-email-marketing-consent branch from f9e3d56 to 8eec5b4 Compare August 10, 2020 07:08
@reintjanhoiting1 reintjanhoiting1 force-pushed the add/form-email-marketing-consent branch from 5014082 to d2ae31b Compare August 10, 2020 11:23
@reintjanhoiting1
Copy link
Contributor Author

Added support for the Newsletter variation and consent field

@reintjanhoiting1 reintjanhoiting1 marked this pull request as ready for review August 10, 2020 11:25
Copy link
Contributor Author

@reintjanhoiting1 reintjanhoiting1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the pull request, made the code a lot cleaner.
@jeherve are you able to rebase the feature branch from master for us?

@reintjanhoiting1 reintjanhoiting1 force-pushed the add/form-email-marketing-consent branch from d2ae31b to 3cb9b52 Compare August 10, 2020 13:01
@jeherve jeherve added [Status] Needs Review This PR is ready for review. and removed [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. labels Aug 11, 2020
@jeherve jeherve added this to the 8.9 milestone Aug 11, 2020
@jeherve
Copy link
Member

jeherve commented Aug 11, 2020

closing this in favor of #16808; it should make it easier to review things.

@jeherve jeherve closed this Aug 11, 2020
@kraftbj kraftbj removed the [Status] Needs Review This PR is ready for review. label Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Feature] Contact Form [Pri] Normal Touches WP.com Files [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it

Projects

None yet

Development

Successfully merging this pull request may close these issues.