Skip to content
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

List option changed to normal text #949

Open
HanroSpangenberg opened this issue Jun 4, 2015 · 5 comments
Open

List option changed to normal text #949

HanroSpangenberg opened this issue Jun 4, 2015 · 5 comments

Comments

@HanroSpangenberg
Copy link

We are sending signed up users a new dialogue on Mxit. But when we sent the screen to them form our side, the list options are shown as text (not clickable). If users access the message themselves i.e. adding the Mxit contact then selecting the newest campaign, the list options are available.

screen
The two list options that become normal text. (Content shortened on this example)

phone
What it looks like on the phone once we've sent them the message

@rudigiesler
Copy link
Contributor

From what I remember when looking into something similar, it has to do with the mxit transport. Replies are sent through the mobi portal API (https://dev.mxit.com/docs/mobi-portal-api) , but outbound messages are sent to the messaging API (https://dev.mxit.com/docs/restapi/messaging/post-message-send).

According to the docs, the messaging API does support links through Mxit Markup, but it doesn't go into any detail of how to specify these links.The Mxit Markup docs are really bad, so we might need to find a someone who knows how to specify links in Mxit Markup.

Overall I think it is possible to add links to outbound messages, but the API docs don't specify how.

@hodgestar
Copy link
Contributor

Our transport does support Mxit Markup for the mobi portal API (assuming that uses the same markup as the messaging API). Perhaps we need to try use that for the messaging API too?

@rudigiesler
Copy link
Contributor

The markup that the mobi portal API uses is XML, ie. <a href=..., where as the messaging API uses something like {0} $Click here for...$ (or though I can't be sure, the docs aren't very clear). So unless I'm missing something, I don't think that the mobi portal API uses the same markup as the messaging API.

Edit: Actually, I think I might understand links. You do {0} $label$ in the Body attribute where you want the links, and you include the list of links in the Links attribute. I'm still not sure if somewhere in the Mxit transport there is something that does this.

@smn
Copy link
Member

smn commented Jun 4, 2015

@BradWhittington who does one ping nowadays about this stuff at Mxit?

@rudigiesler
Copy link
Contributor

Response from Mxit:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants