I have a request dialog within a page tab app. I'm hoping not to have to ask the user for any permissions. I'd like the user to be able to send a request to friends (the request dialog is working fine), but I want only friends that are 21+ to come up in the users multi-friend selector. Is this possible?
The Requests dialog has a filters parameter you can use to define which users do/do not appear in the requests dialog.
You can also request the friends_birthday permission from your users and filter out the friends who do not have a visible birthday or where it is <21 years old.
If users absolutely must not see the app if they're under 21, just restrict your entire app via the API or app settings so those users don't see the app, its content, or requests from it.
You may use custom multi-friend selector for this , just like : mikebrevoort's plugin, and do a check on age and send the request.
Related
In Shopify, is it possible to receive an email notification when a new user signs up (just like I get a notification when an order is placed)?
I have checked under Settings > Notifications but could not find anything. If this is not a default option provided by Shopify, is it possible to implement this using any app?
You can create a webhook to send a notification to a particular URL when the Customer creation event gets fired. Go to your Shopify admin, click on Settings, then on Notifications, scroll down and click on Create a webhook. Once the popup shows, from the dropdown, choose Customer creation Event, JSON or XML format and the url where you want to recieve the notification.
Once you have this setup, look for a webservice which reads webhooks and converts them into an email. Zapier would be a good nominee.
I have a mobile XPages application which uses the single page application control (xe:singlePageApp) of the XPages extension library. The application also uses a workflow engine which sends out emails with links to documents to users so they can approve requests.
The link URL is composed like
http://hostname/app.nsf/m_page.xsp?action=openDocument&documentId=2A2A#requestForm
where requestForm is the name of the appPage containing the form to display a single request document.
If the user is already logged in, the browser opens and displays the document as intended.
However, if the user is not already logged in, the Domino login form is displayed (session based authentication). When the user then logs in, the same XPage is opened, but to the default page (selectedPageName attribute of the singlePageApp) instead of the appPage with the pageName requestForm. The reason for this behavior is that after submitting the login form the anchor part (#requestForm) is no longer present in the URL the browser is redirected to because the #requestForm-part is never sent to the server where the redirect URL is computed in the first place.
Possible solutions I can think of are
put the intended pageName in a real URL parameter (like documentId), parse the URL and modify the browser location (from ...&documentId=2A2A&pageName=requestForm to ...&documentId=2A2A#requestForm)
check the URL for the existence of the documentId parameter and modify the browser location (add #requestForm) if it is present
modify the Domino login form as per Jake Howlett's Suggestion (which is a not always permitted)
I was wondering now if there are more elegant solutions to this.
I would take the first option in your case. But instead of handling the url change at the client-side, I would handle this on the server-side. Otherwise, client will load the initial page once and submit an additional request to the server.
On the beforePageLoad event:
var url:XSPUrl=context.getUrl();
if(url.hasParameter("pageName")) {
var pageName=url.getParameter("pageName");
url.removeParameter("pageName");
facesContext.getExternalContext().redirect(url.toString()+"#"+pageName)
}
This will do the redirection before loading the page.
I made a script using Gmail API to get list of contacts. The script working fine but I want to make it more better as for now, when Login POPUP of Gmail is opened it displays this
xxxxxxxxxx.apps.googleusercontent.com is requesting permission to:
Manage your contacts
Where xxxxxxxxxx is my Client ID. I dont want it to be shown. I want to display my API Project Name here like this
"My API Name" is requesting permission to:
Manage your contacts
Is this even possible to do this? If yes then how?
Thanks
Perhaps try this out:
Search for "Google API Console" in the browser.
On the API console page, on the left hand side menu bar, under "APIs & auth", click on "Consent Screen". Setup project name, upload logo, etc.
See if this helps.
I also seem to remember that during oAuth, you need to pass Application Name (which can be the same as Product Name found in Consent Screen option at step 2 above.
I set up an app to allow users to log into my site using Facebook. When users click the FB login button, the expected auth dialog appears. My auth dialog shows a second page which says: "This app may post on your behalf, including status updates, photos and more."
But my app doesn't need any extended permissions, and will not be posting anything to Facebook. I don't want this second page to appear, but I can't figure out how to make it go away.
On my app's settings page, I didn't specify any extended permissions. Is there someplace else I have to specify that I don't want extended permissions?
Thanks for the help.
You might have specified a scope in the "Login with Facebook" button that requests these permissions from the user. Especially if you just copy-and-pasted an example from the documentation, this might have happened.
Check in your HTML whether you have something similar to this:
<div class="fb-login-button" scope="publish_stream">
Login with Facebook
</div>
If so, make sure to get rid of the scope attribute.
Is there any ways to allow user send message to only 10 friends in Facebook app?
I did not found any options for it in the document.
https://developers.facebook.com/docs/reference/dialogs/send/
It's not possible (as of 2013-04). You can pre-populate the To: field with Facebook usernames, but the the user is presented with a send dialog where he can still edit/add/remove any friends (i.e. he can add more than 10 for example).