It used to work in my Chrome, but now I don't see the check boxes.
Am I the only one that doesn't see the check boxes next to public link?
enter image description here
I suspect that you are using an account that is not the owner of those objects. The "Public link" link will appear whenever the object is publicly accessible, but the checkbox should only appear if you have permission to change whether the object is publicly accessible. Please make sure you're viewing the objects with an account that owns those objects.
Related
I am trying to create a Facebook store for my Facebook page with the checkout leading to my website and not Facebook. When setting up the store I am not given an option to do it. I have seen it in some tutorials showing this choosing checkout option. Is there a way to get to the checkout option?
Found this video by Mexbs that explains how to overcome the issue. In short, here are the steps:
Change the location of your Facebook page to Germany (or some other country that Facebook didn't limit yet)
Add the Shop tab and proceed with the Shop setup. "Checkout on another website" and "Message to buy" should be available now.
Add one product to your shop (so Facebook won't delete your shop tab once you change the page location back to the original).
Change the page location back to your original location.
Apparently this feature was available before FB had its own payment method. Even though you can manage your catalog and add a product url, the checkout button only goes through the FB interface. I am going to ask FB tech support if there is currently a way around this.
I haven't found this yet either and would be stoked if someone can give a clear answer. I've found that if you add products from the Catalog section, you can add a website link for each product which is described by FB as, "a link to the website page where people can view more details and buy this product."
However, my store page is all sorts of mangled at the moment and I'm (sloowwwwlllyyyy) working with FB to get it all sorted out so I can't tell if it's actually working as I'm hoping it does.
To anyone who stumbles on this thread and needs help finding the answer to this problem...
When you click the shop tab to start the setup process DO NOT choose the United States as your location. Choose your location as literally any other location, I did Canada. When you do, it wont try to force you to use Facebook's automatic checkout. It will immediately pop up with the option to buy through messages or direct them to your website. This does not change the location of your actual page either, just choose another country when it asks you right at the shop set up process.
Because of the kind of product I sell I cant accept returns. I needed the ability to send them to my store
Im pretty new to Firebase, so please bear with me on this one. This problem has been stuck in my head for the past days.
I have seen some videos on Dynamic Links, but i havent seen some clear answers to what im hoping to achieve. I want to create a Dynamic Link, that allow users to share their account with their friends (through a link).
So my question is how can i manually construct a dynamic link (with User A´s uid), so when User B clicks on that link (and has the app) it will go straight into the profile of User A?
Should i create a link when a user signs up and store it under their profile in the database?
Looking forward to hearing how you guys would go about solving this problem im having.
You essentially want to create link where the link parameter (what's called the "Deep link URL" in the Firebase console) looks something like https://www.example.com/userProfile?uid=314159. (The full deep link will look different than this.)
When your app opens up this dynamic link, it will convert the incoming URL to a Dynamic Link object, and that object will have a url property that equals this link parameter. Your app will have to do the work to analyze this url and say, "Oh, this appears to be a request to view a user's profile, so I'm going to redirect to that part of my app". It won't happen automatically.
Whether you create it when the user first signs up, or when they decide to share their profile is kinda up to you. I'm generally not a fan of pre-generating deep links ahead of time, because you might realize later you want to change an aspect of these links, and that's easier to do if you don't have thousands of pre-generated DLs. Keep in mind that either way, there is a network call required to convert these longer URls into a prettier short URL.
we have submitted for approval three actions (2 custom and 1 common, watch) on Facebook Open Graph, this is the text that we have write in the review instruction:
The action Add and Watch are published only if user has activated the automatic
sharing inside his profile settings. Those actions use explicitly sharing only
and if only if the corresponded switch is on.
In order to use Share action, user have to touch the rounded Facebook button
at the bottom of the episode page or the series page, then he can write a comment
and only by touching send the action is published. The control is inside user's
hands, and it is obvious that the sharing is explicit.
we have also insert this image along with other images, that show that a user have to enable explicitly the options to make a explicitly share:
and one action need that the user touch a sharing button to be shared.
But Facebook have reject all the action, and have answered this:
we doesn't know how make it, and we need that this actions are explicitly because the user ask it to us. Anyone can help?
It's the explicit option in your settings that's causing Facebook to reject your story. Explicit shares have to be explicitly shared by the user each time (hence the name), so by having an automatic explicit share option that shares the story without the user choosing to share it each time, you're breaking the rules. That's a really complicated sentence... Basically, the user has to choose to share a post every single time for it to be explicit. If it posts automatically without any interaction from the user, then it's implicit.
So your "share" instructions, with the user hitting a share button, is the correct usage. Add and Watch are not.
Ok- new to this today. Two major issues:
First- I am setting up a FB comments box for each of the pages on my website. I have followed step by step and have created an app so I can mederate all of the comments at once rather than page by page. Problem is when I get to my app I am supposed to click on "settings", however I cannot find it. There is an "edit settings' but it does not take me to the box where I can choose either to make every post visible or to let me approve each comment, etc... it just takes me to a summary of my app where I can choose app display name, app namespace, etc.
Here are the directions I have been given:
Changing Moderation Settings
Click on your app in the left column. Then click on Settings (it has two small gears beside it) in the top right corner of the tool to give you access to a few options...
Second issue is that after creating my app and saving changes, I was supposed to click on "need to grant permissions" to create an access token and then see a pink box with the App ID/API Key and App Secret.
After I saved the changes for my app. there was no "need to grant permissions" nor was there a pink box. The App Id and API key and App Secret show, but they are just at the top of the app- no pink box. Do I need to do something with permissions and create an access token? If so how? (I am not even sure what this is)
Assuming the comments plugin is linked to the app correctly (which can be checked by running your URL through the URL Debugger, you can moderate the settings in two places:
The Comment moderation tool
The Settings links, with the gears, displayed in the top right of an instance of the comments plugin itself
You can see your current access token for an app you admin in many ways, but the easiest two places I can think of are:
The Access token tool on the Facebook Developer site
By authorising your app in the Graph API Explorer
I'm trying to programmatically create an application in Facebook. I can do that with this:
https://www.facebook.com/connect/create_app.php?api_key=[key]&name=app_name
However, there's always a popup that says "Allow [Root App] to integrate Facebook functionality for you?" ... OK.
Is it possible for the "Root App" to create the application on the user's behalf without the popup via some previous permission which they have allowed, like stream_publish ...etc or maybe a session_token or ??
Someone said I can create child apps via "admin.setAppProperties" but couldn't get it working. I've also tried "FB.Connect.createApplication" and "Facebook.createApplication" but also failed.
Can anyone help? Maybe with some sample code.
There used to be an API for this but I think it has been discontinued. You can see if you can hack it together from the information available here:
http://blog.programmableweb.com/2009/10/15/facebook-lets-you-easily-integrate-into-sites-and-widgets-with-new-create-application-api/
Child applications (I believe they called them 'fourth party applications') intentionally need user interactions to create.
The documentation for https://www.facebook.com/connect/create_app.php?api_key=[key]&name=app_name is scarce to none. Are you able to access the API key of the newly created application somehow? Or set further app settings such as site-url?
I'm thinking you would need the user's permission to view /accounts then monitor before/after state to detect which one was created.
Is it possible for the "Root App" to create the application on the
user's behalf without the popup via some previous permission which
they have allowed, like stream_publish ...etc or maybe a session_token
or ??
If you create a Facebook application that only pulls someone's profile information, and then you add new functionality that allows it to automatically post on people's walls; you would have to require the user to re-authenticate themselves to give you those extra permissions.
It's hard to understand what you meant by that question.