Given that user has shared a widget with friend or contact, and given that the other users received Email that notify for the sharing or a direct link sent by the inviting user, it is no possible for the invited peer to click the invitation link and go directly to the widget.

Note: Of course, a response to invitation will not always be the case of viewing shared widget and a sharing experience may result from an arbitrary visit in a page will invoke shared widgets. However in this chapter we focus on the situation of responding to invitation link. As explained by previous chapter invitation link may be received either by Email (when possible to infer the Email from contact info) or by receiving a link directly from the inviting peer.

Lets follow the Email scenario. It starts by receiving Email that notify for shared widget:

CG shared widget email

 

There is one important thing to note before proceeding - Viewing shared widgets is possible only when Content Glass is running on the website. This happen if either Content Glass is installed on the website either by JavaScript code or by managed-app application (as in the case of CG for Shopify) or using the web browser plugin. So summarize you can view shared widgets if Content Glass run on website:

  • By direct installation
  • By Chrome plugin

So unless you know that Content Glass run on a website you wil have to install Content Glass chrome plugin. Installing the plugin take few seconds and you do that by visiting the Content Glass Chrome  Plugin link. 

So given that you installed the plugin or that CG is running on the source website, the next step is to ysed the invitation link you recieved either directly or by Email. Clicking the invitation link start a procedure of creating interaction with the shared widget. The first step of this procedure is to redirect the user to the web page where widget was shared and present the user with popup dialog to confirm that user wants to accept the sharing invitation:

Once user click the "Connect" button a the invitation process continue as following:

  • If the invited peer is marked as new relation (available only with Content-Glass social network) we will first handle the task of creating the relation and the new account when required. This procedure will be described by next chapter.
  • Else check if user is logged-in to required social-network. If not then present the user with the login page.
  • Else if user login load the shared widget.

In our example the receiving peer was not logged-in to content-glass social network so it was presented with login dialog. Remember that login must use the same account as in the invitation (in this case the account of user tester4@rhizomenet.com).

Invitation confirmed you need to log in

And once completing with the login the widget is presented to the invited peer:

In the next chapter we will see a process of creating relation on the fly using content-glass social network.