converting normal website in mobile - mobile-website

I am developping Mobile Application but i am not getting any idea on how a normal URL is converting in mobile like http://www.google.com it is a normal url but it is openning in mobile like http://m.google.com like this for that i have to do any thing or not i dont know please let me know the steps for that if any one knows.
Thanks in advance.

Normally you would check the user agent string when a user makes a request to your site. How you would do this is dependent on your server-side programming language/environment. But when you check the string you would simply compare it to known "mobile browsers" and would forward the user to the other URL accordingly.
It's not really "changing the URL" to something other than a "normal URL" it's just checking a condition at the request time and forwarding the user to a different site if the condition is met.

Related

Using m.me links with ref param

I'm trying to deeplink users into my facebook messenger bot, and I need to pass some data in at the same time. Supposedly this can be done by using m.me links, along with a query param.
My bot's page is https://www.facebook.com/Willy-1610141399078870/
The m.me url would be something like this. https://m.me/Willy-1610141399078870?ref=somedatagoeshere
The m.me link works to a degree on desktop, but the data isn't passed to the bot. I don't particularly need it to work on desktop.
However, when I try to open that link on ios or android, I get an error message.
Android
This user name doesn't exist. Try another code or link
iOS
Username was not found
The bot hasn't been published yet, so it won't be visible to anyone else. I need to be able to test this functionality before I publish, so I hope that's not what is causing the failure.
Has anyone else been able to use this feature?
It seems that the facebook-generated username can't be used for m.me links. It requires you to register an explicit username.
My page's generated name was Willy-1610141399078870, so https://m.me/Willy-1610141399078870 wasn't a valid url.
To register a username for your page, go to your page > About > Create Page #username.
Then, you can attempt to pick a username that isn't already taken. Somehow, #willy-the-test-page is already taken (?), so I got this incredibly confusing error message:
Taking the error message at face value, I decided to create another page and try again. This time, realizing that the message didn't mean what it said. Picking an available username clears the error message, and allows registration.
Just kidding! It will tell you again that the page isn't eligible.
The solution was to create a totally new page, and go through the #username creation flow again. It worked for me on the second attempt.
It's rumored that a page needs at least 25 likes to become eligible for an #username, but this isn't true in all cases.

What is the human-readable URL of this Facebook page?

The URL that I see in my browser is:
https://www.facebook.com/groups/665545990268762/
But it should have a human readable URL. Something like:
https://www.facebook.com/EntrepreneurialMums/
I need to know what it is because I need to put it on a sign.
How do I find out?
And why am I seeing this number URL?
AFAIK, you only get a readable URL in a Facebook group if you select one. An administrator can set it under Group Settings -> Web and Email Address
I believe facebook automatically assigns groups numbers like this. If you would like it to be human readable, then I would recommend using goo.gl or any of the other popular url shorteners. (I recommend goo.gl because it allows you to track clicks, if you are logged in when the short url is created). I would recommend using this in conjunction with a qr code.

This url has been identified as malicious and/or abusive

https://alsalamanty.com/
http://alsalamanty.com/
I`m a developer of Facebook login app for website. When I'm trying to save changes in my Facebook web-application settings, getting this error "Site URL has been been identified as malicious and/or abusive." I can't save anything while field "Site URL" contains my domain name. What am I supposed to do?
Go to facebook.com . Try to share the url. You will get a dialog saying the url is bad and in the button there will be a link if you don't agree and you want to report it.
simple solution is to disable facebook button, so that facebvook change their aggressive globalism political tactic of changing their ways for developers constantly forcing to change their code, like google does with google login.
Other solution is to, according to:
https://www.forbes.com/sites/caroltice/2013/03/15/when-facebook-calls-you-abusive-reclaim-your-reputation/
First go to:
https://global.sitesafety.trendmicro.com/
and check if your URL appears as non safe or as Untested
Click on reclassify --> url reclassification request
Then select the option SAFE
Suggest a category
Add your email
click the button to proceed, then go to yuour email and click the link that trendmicro sent to you, then wait
other links:
https://global.sitesafety.trendmicro.com/index.php
https://www.trendmicro.com/en_us/about/legal/detection-reevaluation.html

My GCLID code gets stripped when user is redirected to my Mobile Site

I have a tracking issue due to GCLID gets stripped when users get redirected from our desktop site to our mobile site. Let me know how we can get this fixed.
Here's a sample:
When a user is detected as using a mobile device, they are redirected automatically. For example, if they were going to sitename.com/, they would instead end up on sitename.com/?___store=mobile2
The problem we are encountering is that we need certain query parameters from the original URL to be preserved when the redirect happens in order for tracking to work correctly.
If someone clicks a Google ad, they'll be taken to a URL with a gclid parameter appended by Google, for example: sitename.com/?gclid=ABC_123-abc
However, if the user is on a mobile device, they'll be redirected to sitename.com/?___store=mobile2. As you can see, the gclid parameter is no longer present.
Let me know if you guys have any solution to this. Thanks a lot.
The code that performs the redirection needs to preserve query parameters on the original request. In your case, it should also append an "&" and the ___store=mobile2 parameter.

Why is my application's authentication page different to everyone else's?

As per the Authentication Documentation, I'm directing my user's to the following URL to initiate the authentication flow:
https://www.facebook.com/dialog/oauth?client_id=251747341532139&redirect_uri=https://www.facebook.com/connect/login_success.html
However, instead of the login page looking like:
... (i.e. like it does in the documentation and in other Apps I've created and used), it looks like this...
Does anyone know why?
I've tracked the redirects that the page makes, and it's as follows:
https://www.facebook.com/dialog/oauth?client_id=251747341532139&redirect_uri=https://www.facebook.com/connect/login_success.html
https://www.facebook.com/connect/uiserver.php?app_id=251747341532139&method=permissions.request&display=page&next=https://www.facebook.com/connect/login_success.html&response_type=code&fbconnect=1
https://www.facebook.com/login.php?api_key=251747341532139&skip_api_login=1&display=page&cancel_url=https://www.facebook.com/connect/login_success.html?error_reason=user_denied&error=access_denied&error_description=The+user+denied+your+request.&fbconnect=1&next=https://www.facebook.com/connect/uiserver.php?method=permissions.request&app_id=251747341532139&display=page&redirect_uri=https%253A%252F%252Fwww.facebook.com%252Fconnect%252Flogin_success.html&response_type=code&fbconnect=1&from_login=1&rcount=1
Application type is set to Native/Desktop, and I've set the App Integration to "Website".
If the language I'm using makes any difference, I'm using C#, and setting the Url of System.Windows.Form.WebBrowser.
As per the above comments, you can use the display parameter in the URL to control which kind of dialog to show, as you would normally do with the JS SDK.
Your URL becomes:
https://www.facebook.com/dialog/oauth?client_id=xx&redirect_uri=yy&display=popup