Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Widgets

Discuss SilverStripe Widgets.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

LinkedIn share tags


Reply

3 Posts   1205 Views

Avatar
Brand

6 September 2012 at 10:53pm (Last edited: 6 September 2012 10:54pm), Community Member, 8 Posts

Dear fellow SS users. I have tuned the metatags over and over again and nothing seams to work. I can't get the LinkedIn share widget filled with information about the right page. The only thing LinkedIn gets, is the name of the domain. Does anybody knows what goos wrong? Here is the code:

$MetaTags
<meta property="og:title" content="$Title" />
<meta property="og:url" content="http://www.realimpact.nl" />
<meta property="og:image" content="http://www.realimpact.nl/assets/logolinked.png" />
<meta property="og:description" content="<% if MetaDescription %>$MetaDescription<% else %>$Title<% control GetHomePage %>$MetaDescription<% end_control %><% end_if %>"/>

If you want to try it real time: www.realimpact.nl

BTW, the facebook domain gets the og's right...

Avatar
epidote

20 November 2012 at 2:30pm Community Member, 2 Posts

I have the same problem, adding
<?xml version="1.0" encoding="UTF-8"?>
to Page.ss fixes the linkedin issue BUT breaks the site (FF, Safari at least) due to xml validation

site already has
<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
as described in a few posts to fix the issue, but most posts say delete
<?xml version="1.0" encoding="UTF-8"?>
to fix but that seems to be the only thing that fixes linkedin??

That help you? Any ideas?

Avatar
epidote

11 April 2013 at 11:40am Community Member, 2 Posts

In case anyone else has the same problem I tracked this down to the Header -

This was the old header that killed linkedin
Content-Type: text/html; charset="utf-8"

This works fine for linkedin
Content-Type: text/html;

I just edited mysite/code/Page.php

class Page_Controller extends ContentController {
      
   public function init() {
      parent::init();   
    $this->response->addHeader("Content-Type", "text/html");
         
   }
   
}

utf8 still set in template and all appears to be working/dispalying fine.