Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue with Google plus and Slack #24

Open
nncuong1311 opened this issue Jan 12, 2015 · 2 comments
Open

Issue with Google plus and Slack #24

nncuong1311 opened this issue Jan 12, 2015 · 2 comments

Comments

@nncuong1311
Copy link

My web use angular-seo.js and config htm5 link
$locationProvider.html5Mode(true);

My issue is when i copy my link and paste into the shared box on Google plus, Google plus don't parse my website's title and description, and when i do the same thing with Slack chat , Slack display
{{ $root.pageTitle }}
{{ $root.pageDescription }}

With facebook, linkedin, it's normal.
This is my <head> part:
<meta name="fragment" content="!">
<title ng-bind="$root.pageTitle"></title>

<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<base href="/">

<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="My description">
<meta name="author" content="{{ $root.author }}">
<meta name="copyright" content="© Ideapod {{ $root.today | date:'yyyy' }}">

<meta property="fb:app_id" content="12345678">
<meta property="og:site_name" content="MyWeb">
<meta property="og:image" content="{{ $root.pageImage }}">
<meta property="og:type" content="{{ $root.facebookOpenGraph.type }}">
<meta property="og:url" content="{{ $root.facebookOpenGraph.url }}">
<meta property="og:title" content="{{ $root.pageTitle }}">
<meta property="og:description" content="{{ $root.pageDescription }}">

What's wrong with my code, please let's me know. Thank you very much !
@peteclodi
Copy link

I believe that this issue is related to user-agents and how this module is always expecting ?escaped_fragment= in the request URL. I am looking into this for my own implementation of this package and will create a pull request once I find a solution.

@peteclodi
Copy link

I created a pull request, #28, that allows for the handling of requests based off of User-Agent and not escaped_fragment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@peteclodi @nncuong1311