Content pfp
Content
@
0 reply
0 recast
0 reaction

llamafacts pfp
llamafacts
@llamafacts.eth
Feature request: allow different post urls for each button. By default hit the post_url, but if there is a post_url_2 hit that instead if button 2 is clicked.
2 replies
0 recast
1 reaction

Moon pfp
Moon
@moon.eth
I thought that is what button target was for but it doesn't work when I tried it.
1 reply
0 recast
0 reaction

llamafacts pfp
llamafacts
@llamafacts.eth
@v any thoughts on why this is not working? target is present, but when I click that button it calls the post_url, not the one in the target. Maybe formatting?
2 replies
0 recast
0 reaction

Goksu Toprak pfp
Goksu Toprak
@gt
Can you share the embed URL so we can debug further? It should be using the `target`.
1 reply
0 recast
0 reaction

llamafacts pfp
llamafacts
@llamafacts.eth
Sure, this one https://pinatadrops.com/apps/basketball I put a test button that should call the leaderboard endpoint. <meta name="fc:frame:button:4" content="Leaderboard"> <meta name="fc:frame:button:4:target" content="https://pinatadrops.com/api/basketball/leaderboard">
1 reply
0 recast
0 reaction

Goksu Toprak pfp
Goksu Toprak
@gt
Fixed! There was indeed a bug. Thank you for sharing your frame for us to confirm.
2 replies
0 recast
2 reactions

llamafacts pfp
llamafacts
@llamafacts.eth
hey man @gt can I bug you with one more issue? According to the frames debugger, my frame is hitting an endpoint with a query param. /result?team=1 however when I print the untrustedData, it only shows until /api/basketball even the /result part is not present.
1 reply
0 recast
0 reaction

Goksu Toprak pfp
Goksu Toprak
@gt
Data package holds the frame URL not the target. You should be looking at action index to determine what button was clicked. If you really want to read the query param on a POST — then I would think your API handler has the info when request is received.
1 reply
0 recast
1 reaction