StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Are you sure you actually need the user's access token? According to documentation <a href="https://developers.facebook.com/docs/reference/api/event/" rel="nofollow">here</a> you may need:</p> <pre><code>- a generic access_token for public events (those whose privacy is set to OPEN) - a user access_token for a user who can see the event for non-public events - an app access_token (for non-public events, must be the app that created the event) - a page access_token (for non-public events, must be the page that created the event) </code></pre> <p>You can get info on how to get those tokens here <a href="https://developers.facebook.com/docs/concepts/login/access-tokens-and-types/" rel="nofollow">https://developers.facebook.com/docs/concepts/login/access-tokens-and-types/</a></p> <p>A good idea could be to store the attending users (in the DB) when you have access to the event - when some user is logged in. </p> <p>UPDATE for getting the data from FileContent.</p> <p>I don't know what API response exactly you are referring to, but from my experience they are returning data: - serialized using JSON - you need to use DeserializeJSON(), for example like this:</p> <pre><code>local.returnStruct = DeserializeJSON( local.requestResult.FileContent ); </code></pre> <p>or </p> <pre><code>local.returnStruct = DeserializeJSON( local.requestResult.FileContent.toString() ); </code></pre> <ul> <li><p>send as something similar to URI. I'm using a function to get that data:</p> <pre><code>function getStructFromQueryString( queryString ) { var ret = StructNew(); var i = 0; var key = ''; for(i=1; i LTE ListLen(arguments.queryString,'&'); i++) { key = ListGetAt(arguments.queryString, i, '&'); ret[ListFirst(key,'=')] = URLDecode(ListLast(key,"=")); } return ret; } </code></pre></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload