Add attendee survey to wordcamps.

[StevenDufresne]

Fixes #929

This PR is an attempt at implementing the user flow described in this comment.

How does this work programmatically?

• When the plugin is activated:

  • Create a survey page in draft status
  • Create a tix_email in draft status
  • Add Admin page to central.wordpress.org
  • Schedule a daily cron job that looks if camp ended 2 days ago.

• When the cron job runs:

  • Check if we already sent an email for this camp
  • Check to make sure the camp ended 2 days ago
  • Publish Survey page
  • Associate attendees to tix_email
  • Add tix_email to the queue (set to pending)
    • email gets picked up by camptix cron email sending queue tix_scheduled_every_ten_minutes
  • Schedule single event to unpublish the Survey page 2 weeks later.

Screenshots

View	Screenshot
Email queue
Email
Admin
Survey Email

How to test

1. Create a Next-Gen Event WordCamp
   • Make the Start Date in the past
   • Make the End Date the current date (we'll update this later)
   • Create the site in the network
     • Create a ticket: wp-admin/edit.php?post_type=tix_ticket
       • Make sure you update the Ticket Options.
     • Setup Stripe for testing:
       • wp-admin/edit.php?post_type=tix_ticket&page=camptix_options&tix_section=payment
         • You can you these keys:
           • Test Secret: sk_test_4eC39HqLyjWDarjtT1zdp7dc
           • Test Publishable: pk_test_TYooMQauvdEDq54NiTphI7jx
     • Publish the "tickets" page
     • Purchase a ticket using this test stripe credit card
       • Visa | 4242424242424242 | Any 3 digits | Any future date
2. Create a "traditional" WordCamp
   • Create it in the network
3. Visit Next-Gen
   • Go to Pages
     • Expect to see Attendee Survey in `draft mode
     • Check out the content (if you don't have JetPack setup locally, you'll see and error when viewing the content, saying the JetPack form black is missing
   • Go to Ticket -> E-Mail
     • Expect to see an email in draft mode.
   • Run the following wp cli script to make sure the cron jobs are scheduled
     • wp cron event list --url=https://events.wordpress.test/{city}/{year}/{type}
     • expect to see the following cron job: wc_attendee_survey_email
   • Go back to the Next-Gen Wordcamp Post type and update the End Date to 2 days ago.
   • Run this script to set WordCamp to closed wp post update {post_id} --post_status=wcpt-closed --url=https://central.wordcamp.test/
   • Run the following cli command:
     • run wp cron event run wc_attendee_survey_email --url=https://events.wordpress.test/{city}/{year}/{type}
     • Should succeed
   • run wp cron event list --url=https://events.wordpress.test/{city}/{year}/{type}
     • Should see a new scheduled taskwc_attendee_disable_survey.
   • Visit Ticket -> E-Mail -> [[first_name], tell us what you thought: Post-event survey]
     • It should be set to pending (or published if it has been picked up (the job runs every 10 mins )
     • If you are running the docker environment you can check out mailcatcher
       • http://localhost:1080/
   • Visit the survey link on the front end an submit
   • run wp cron event run wc_attendee_disable_survey --url=https://events.wordpress.test/{city}/{year}/{type}
   • Revisit the link, the page should be unpublished.
   • Head over to https://central.wordcamp.test/ click on "Attendee Survey"
     • Verify the list is accurate
4. Make sure none of this exists on the traditional WordCamp :)

[iandunn]

Looks good so far 👍🏻

I didn't read most of the code yet, though, since you mentioned wanting to discuss some things before going further. I mostly just responded to the things in the PR description.

LMK if there's anything else you'd like me to review at this point.

[StevenDufresne]

I'm curious what is a better way to do this. It also isn't localized.

[renintw]

Maybe something like below would work? (exclude shortcodes and HTML tags from the i18n functions)

$email  = "Hi [first_name] [last_name],\r\n\r\n";
$email .= sprintf( 
	/* translators: %s: wordcamp name. */
	__( "%s is over, thank you to everyone who joined us! \r\n\r\n", 'wordcamporg' ),
	esc_html( $wordcamp_name ) 
);
$email .= __( "As a community-led event, feedback is really important to us. It helps us improve our events and to keep providing high quality content.\r\n\r\n", 'wordcamporg' );
$email .= sprintf( __( 
	/* translators: Please leave %1$s and %2$s untranslated. They represent the opening and closing anchor tags, respectively. */
	'Please take a moment to answer our %1$spost-event survey%2$s and help us to do amazing WordPress events!\r\n', 'wordcamporg' ), 
	'<a href="' . esc_url( $survey_page_url ) . '">', '</a>' 
);
$email .= __( "(If you can't open the link, copy and paste the following URL)\r\n", 'wordcamporg' );
$email .= $survey_page_url . "\r\n\r\n";
$email .= sprintf( 
	/* translators: %s: closing date. */
	__( "Please complete the survey by %s.\r\n\r\n", 'wordcamporg' ),
	$closing_date );
$email .= __( "Please also note that all responses will be kept confidential, and we will not share your personal information with any third parties.\r\n\r\nThank you in advance, we really appreciate your time!\r\n\r\nBest regards,\r\nOrganising Team,\r\n", 'wordcamporg' );
$email .= esc_html( $wordcamp_name );

[iandunn]

It may be good to open an issue in the milestone that reminds us to remove this after iterating, otherwise it'd be easy for it to get overlooked and no one ends up using the plugin.

[renintw]

Have gone through all the test cases I could think of, and everything appears to work as described 👍 Will delve deeper into the code.

[renintw]

LGTM 👍! Thanks for handling this issue, it's great.

[iandunn]

LGTM 👍🏻

[iandunn]

Since we've needed this here and in the Speaker Feedback plugin, I think it makes sense to extract it into a generic function in mu-plugins/wp-cli-commands/miscellaneous.php, next to set_skip_feature_flag().

That way any plugin can use it, rather than duplicating it.

[StevenDufresne]

I also wondered about just removing it since we're limiting it to events and this survey will probably apply across the board.

I think I'll remove it. Yep.

[iandunn]

I think this'll need to be updated to work on production.

You could use get_top_level_domain() in place of a hardcoded .test, but I think it'd be a bit more clear to check if $site->blog_id === EVENTS_NETWORK_ID.

[StevenDufresne]

Yep. Makes sense.