Hi Carlos,
First off is the internal error page in the common screen flow needs to be able to catch notokenexception error thats why i placed the "HandleNoAccessTokenException" from the twitter connector inside the common web flow.
Next is the webscreen "Internal Error" itself needs to have a boolean that would indicate if the error is because of the "Token" so i put a variable to store the value.
Then i add a preperation for the webscreen with an IF that catches the notoken error
"Session.ExceptionMessage = "NoFacebookAuthorizationCodeException"
and if the error is true then i place a 'true' value in the boolean variable so that the screen would show a link that would require the user to log in first.
i hope this helps others with the same problem :)
and same is true with facebook connector
First off is the internal error page in the common screen flow needs to be able to catch notokenexception error thats why i placed the "HandleNoAccessTokenException" from the twitter connector inside the common web flow.
Next is the webscreen "Internal Error" itself needs to have a boolean that would indicate if the error is because of the "Token" so i put a variable to store the value.
Then i add a preperation for the webscreen with an IF that catches the notoken error
"Session.ExceptionMessage = "NoFacebookAuthorizationCodeException"
and if the error is true then i place a 'true' value in the boolean variable so that the screen would show a link that would require the user to log in first.
i hope this helps others with the same problem :)
and same is true with facebook connector