-
Notifications
You must be signed in to change notification settings - Fork 846
Form Block: allowing marketing consent collection #16723
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Form Block: allowing marketing consent collection #16723
Conversation
This is an automated check which relies on E2E results is available here (for debugging purposes): https://jetpack-e2e-dashboard.herokuapp.com/pr-16723 |
jeherve
left a comment
There was a problem hiding this 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.
extensions/blocks/contact-form/components/jetpack-newsletter-integration-settings.js
Outdated
Show resolved
Hide resolved
extensions/blocks/contact-form/components/jetpack-newsletter-integration-settings.js
Outdated
Show resolved
Hide resolved
extensions/blocks/contact-form/components/jetpack-field-consent.js
Outdated
Show resolved
Hide resolved
extensions/blocks/contact-form/components/jetpack-field-consent.js
Outdated
Show resolved
Hide resolved
* 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]>
7647030 to
a64f5e0
Compare
* 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]>
f14f5c9 to
f9e3d56
Compare
…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`.
f9e3d56 to
8eec5b4
Compare
Co-authored-by: Renovate Bot <[email protected]>
Co-authored-by: Renovate Bot <[email protected]>
Add travis job url into slack messages
* Add retry to .org login method * cleanup
5014082 to
d2ae31b
Compare
|
Added support for the Newsletter variation and consent field |
reintjanhoiting1
left a comment
There was a problem hiding this 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?
extensions/blocks/contact-form/components/jetpack-field-consent.js
Outdated
Show resolved
Hide resolved
Co-authored-by: Renovate Bot <[email protected]>
Co-authored-by: Renovate Bot <[email protected]>
add translatable strings add isSimpleSite check
d2ae31b to
3cb9b52
Compare
|
closing this in favor of #16808; it should make it easier to review things. |
Changes proposed in this Pull Request:
Jetpack product discussion
N/A
Does this pull request change what data or activity we track or use?
Testing instructions:
test case 1
test case 2
/Todo WIP/
/Todo WIP/
test case 3
/Todo WIP/
/Todo WIP/