Better checks for active Jetpack in Tracks#8685
Merged
Conversation
jeherve
pushed a commit
that referenced
this pull request
Jan 31, 2018
Member
|
Cherry-picked to |
Contributor
|
I'm inclined to revert this one and then see how to fix again. What do you think @dereksmart ? |
Contributor
Author
|
@oskosk yeah, I'd like to try and find a solution where we rely instead on whether or not they have agreed to the TOS / clicked the connect button at least once. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Blocks sending a tracks event (if Jetpack is not connected) late enough to catch all instances of sending an event.