I am developing Facebook app and I need one data (like Id) from user to customize service to them. I want to ask data while adding app in page and save it for future use. How can I do this?
Related
I currently have an iOS app that is built and functioning except for one slight problem. I would like to retain CAPTCHA whenever an anonymous user creates an account via the web (using Drupal's user registration form). However, I would like to have another URL that houses the same Drupal registration form (without CAPTCHA) so that users can create an account from within the iOS app (app connects to Drupal site using Drupal iOS SDK and userRegister function).
Is this possible in Drupal 6? Is there a way to clone the user_register form such that the original form has CAPTCHA and lives at mysite.com/user/register whereas user_register_clone form does not have CAPTCHA and lives at mysite.com/user/register/mobile?
Thanks in advance and have a great day/night!!!!
In the autoassignrole (http://drupal.org/project/autoassignrole) module there is a clear example of cloning the user register form and creating a register process in a different page than register.
The module assign user roles based on the path the user is creating the account from.
So you could check the module's code for examples.
It is said you cannot create apps automatically with the current facebook API.
Create and Configure Facebook Apps via API
How to programatically create a Facebook application via JS SDK or Open Graph API? (createApplication)
Yet woobox.com does it.
I have created a few photo contests in their portal. It didn't ask for extra permission. No dialogs showed up. I just got these links:
http://www.facebook.com/pages/-/105892812908965?sk=app_422118604517529&app_data=dlt-1
http://www.facebook.com/pages/-/105892812908965?sk=app_451684954848385&app_data=dlt-1
How did they create these apps?
app_422118604517529
app_451684954848385
I would expect
www.facebook.com/pages/-/105892812908965?sk=app_SAME_APP_ID&app_data=WOOBOX_ID_1
www.facebook.com/pages/-/105892812908965?sk=app_SAME_APP_ID&app_data=WOOBOX_ID_2
You are correct with the presumptions that Facebook apps/users/groups and pages can't be created dynamically. What woo box is what many other page tab applications are doing. They create a number of applications for different templates and then customize them according to your inputs. They don't create apps dynamically. And these dynamic apps get their required data from app_data field.
Another point to note is
An app can't be installed on a page twice
that is why many Service provider that provide page tab applications maintain a pool of applications to fulfill their user's desires.
Is it possible to add a Like button inside an app (iframe) to ensure the user likes the app and not the page that "ownes" the app?
Yes. You can. But the user has to install your app in order to access the user's likes. Permission user_likes is required.
I am new to .NET framework and I want to create a profile page for each user to edit their own page. How do I make this edit page only available to the specific user? Is there a way to do this without me manually going into the code every time I have a new user sign up?
I'd take a look at ASP .NET Membership. Then you can lookup the user "profile" based on their Id to load the appropriate information.
You start by ensuring that the page is only visible to authenticated users. You do this by setting the appropriate settings in web.config for the corresponding folder or file.
Once you've done that, this page should simply load details for the current user. All users would see the same page, but it's content would be populated by your code only for this current user.
There would therefore be no way for one user to display the contents for another user. The ID of the user being viewed/edited should definitely not be a query argument or anything like that.
I have decided to use ASP.NET MVC to develop multi page (registration) forms in asp.net. There will be two buttons on each page that allows the user to navigate to the previous and next page. When the user navigates back to a page they recently filled out, the data should be displayed to them. I understand ASP.NET MVC should remain stateless but how should I maintain page information when the user navigates back and forth.
Should I?
Save the information to a database and retrieve information for each page change?
save information to the session?
Load all the fields and display only whats's needed with javascript?
This registration form is going to be used in multiple sites but with different sets of questions (Some may be the same). IF performance is a main concern, should I avoid generating these forms dynamically?
Jay
This sounds like the kind of information that you would want to store in a user session. What session store is used can be configured, so you could use a database to store session for users if that would be a better fit than using in-process session.