Well, I am a non-Facebook developer, and a normal .NET programmer who have created a Facebook application for a regular website around one year ago using FBML. I have no time to read the roadmap every day and know what will be next. So I had no idea about OAuth and HTTPS till yesterday.
All of a sudden I received an email yesterday saying (27 Sep) upgrade to OAuth 2.0 and HTTPS,
otherwise the application will be disabled from 1st Oct.
Now, I read about OAuth 2.0 the whole day yesterday, and think I can get around it now chaining things, but I found that the site which currently host my Facebook application doesn't have SSL (HTTPS support) or dedicated IP address and I found that I need to invest around 20$ to get SSL and another $20 for a dedicated IP address. I am ready to pay
for it, but as you know a response from hosting are not that quick.
Now I have emailed my hosting to make arrangement for it, but sadly they have not responded yet, and I now only have one day left (I don't know they will respond or not).
So how can I save my application? I don't have any server that support HTTPS for now. Even if I get some free SSL I am not able to implement it as I don't have a dedicated IP address.
Is there some way I can put a "will be back soon" kind of message. Or how can I save the application now?
I think I need to update that HTTPS canvas page in the setting anyhow.
FBML applications are not required to migrate and support HTTPS and signed requests.
Source: http://developers.facebook.com/blog/post/567/
Also, be aware that Facebook will stop supporting FBML apps at the end of the year.
Related
Firebase hosting requires that a TXT setting be set up to as they call it
Prove the domain is yours
I purchased a domain. It is mine. In order to set this TXT setting I have to have the domain hosted. The place I purchased the domain from sells hosting for minimum one year at a time. What is the point of firebase hosting when I have to buy hosting somewhere in order to prove that the domain is mine? Is there any way to get around this catch 22?
Proving ownership is done by putting a TXT record in the DNS. This doesn't require that you have a website hosted yet, it merely requires access to the DNS settings for your domain.
It's hard to help beyond that without knowing where you registered your domain.
Update. I took Frank's advice and set up a few Namecheap accounts. Wowie! The discount names are as cheap as 50 cents/year if you buy 1 or 5 years. Thanx for the advice. There is a caveat to using Namecheap/firebase, however.
Do not take this as if I were looking a gift horse in the mouth. I am super grateful to Google for free hosting. I merely want to warn users that firebase is not a free country. Google forces the s religion. I put in many hours of work to create my website using my girlfriend's hosting MySQL. Her hosting platform does not have an s in the URL: https. So the Angular 5 HTTP calls barf. I also included a contact page and a share via email popup. I used my girlfriend's hosting and set up a poor man's PHP web service for that. That does not work because girlfriend's hosting uses HTTP not https. So now I have to go back and recode these backend connections to use Google firebase and Google functions/SendGrid. I could have done that from the get-go and saved myself the time and aggravation.
this github repository hosts my website www.deyaeldeen.com
this is how the website should look...
--
this is the spam suspendeddomain.org !!!! (this stock photo alone should give anyone cancer)
on android devices and my mac, with main browsers, it shows normally.
on my iPhone and some other friend iPhone, the domain redirects to spam website, on another iPhone it works normally,
this is the godaddy zone and dns settings
--
--
the forward with masking forwards to deyaeldeen.com
I hope someone can help with this, on a side note, I added my domain to infinityFree service, and deactivated their account and moved to github pages, do you think this caused this problem?
this is a visual representation of ns redirects
it works fine now, I had to wait, it took more than two days
the documentation mentioned 48 hours though!
I have old Sandbox business & personal accounts that stopped working. I have to go back and test a site I developed two years ago. I saw a reference to importing these accounts on the new site but every link seems to go in circles. I certainly can't afford time to rewrite all my client's api's even if they would pay me just to go into testing mode.
Can someone suggest how I might revive these accounts.
There are currently some issues that are being addressed to resolve this issue. As a workaround try using FireFox or Chrome if you were using IE. Clear your cookies and chache prior to opening up that browhwer. Then go to developer.paypal.com and log in with your live PayPal account email address. Then try importing your accounts. There have been more issues with IE than the other browsers.
I am trying for the first time to setup Paypal PDT and want to test it against the sandbox.
When I try to go to http://sandbox.paypal.com, I am getting forwarded to https://www.sandbox.paypal.com/hk/webapps/mpp/home , then I get an error generated by Tomcat (404).
Is that normal? Is this site to be used only though APIs and am I doing something wrong when opening it directly in a browser?
Under the FAQ, I can read that
I'm a non-U.S. developer. How does the site redesign affect me?
The current new REST APIs and PayPal Mobile SDKs are currently
targeted for the US market only. We will be rolling out in all
geographies over the rest of the year.
Is this a reason for that? Is the sandbox a part of the REST API?
I apologize for the inconvenience. We are working to fix this as soon as possible. In the meantime please try using https://www.sandbox.paypal.com/webapps/mpp/home as a workaround to log in.
Just wanted to follow up and to let you know that the 404 issue has been resolved.
Nope, it's broken for me to in the UK. I tried using a US proxy, and it seems that it's broken for everyone, no matter where you are.
Best to just sit it out and wait, although in the meantime I'm going to be using something else. Way to go, PayPal.
When Oct 1 rolls around, I want to make sure my games are covered. So in that light, I have a couple of questions.
I understand I need to offer SSL version, which is done, but does that mean that the http version is going away? or will it just mean that all apps will require both versions, rather than being able to leave one blank?
With the dashboard increment calls going away, what prompts the system to add a [1] next to the app in the sidebar when the player has something they need to do? unless the app has some way of telling the facebook server that a user has some task they need to perform, how is that going to increment?
with the new "manage_notifications" permission, does this imply that after a long haitus, apps will once again be able to post messages to a users notification drop down? which would be great and would make the previous dashboard question void.
thanks for your help!
The SSL version is required for your users who have secure browsing enabled in their security settings. Without an https version your app is not accessible to users who opt for secure browsing.
The [1] that you see next to the apps is the number of pending requests sent using the request Dialog.
For more details...https://developers.facebook.com/docs/reference/dialogs/requests/