Opened on 08/12/2014 at 01:52:27 PM

Closed on 02/21/2018 at 05:50:42 PM

#1198 closed defect (invalid)

If you share your statistics via facebook, you get a german headline and an english description

Reported by: passbrains Assignee:
Priority: Unknown Milestone:
Module: Websites Keywords:
Cc: saroyanm, sebastian, greiner Blocked By: #5447
Blocking: Platform: Unknown
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by sebastian)

Adapted from



How to reproduce

  1. Install ABP
  2. Click at the icon in Safari
  3. Click at Share via Facebook

Observed behaviour

But the headline is in German, text in English

Expected behaviour

That the text is in English OR in German

Attachments (1)

1598_1407588706_abp_desc.png (222.0 KB) - added by passbrains on 08/12/2014 at 01:52:30 PM.

Download all attachments as: .zip

Change History (20)

Changed on 08/12/2014 at 01:52:30 PM by passbrains

comment:1 Changed on 08/12/2014 at 01:52:33 PM by passbrains

1 - 12 Aug 2014 13:52:12 posted by Philip Hill
It's not Safari-specific, happens also with Google Chrome.

comment:2 Changed on 08/12/2014 at 01:53:39 PM by philll

  • Description modified (diff)
  • Priority changed from Unknown to P2
  • Ready set

comment:3 Changed on 08/12/2014 at 09:00:24 PM by saroyanm

The description part of facebook share dialog is being taken from "".
So I can see 3 solutions here:

  1. Use description from web locale meta (14 Languages), detect language and use url for appropriate language (ex.:
  2. Add share dialog description to ABP locales and load that description from ABP (48 locales).
  3. Use only English text (which I don't think we want here).

Not sure which is more preferable.

With 1-st solution I've noticed problem that even when using localized sharing link the description is always in English, not yet sure the case, this something connected to website itself, so for example if "" url is being added to the post in FB, it's always shows English text not sure if it's a bug or feature. Also in case of 1-st solution we don't have all ABP translations for website.

Last edited on 08/12/2014 at 09:11:31 PM by saroyanm

comment:4 Changed on 08/13/2014 at 07:40:46 AM by saroyanm

  • Cc added

comment:5 follow-ups: Changed on 08/27/2014 at 01:17:49 PM by sebastian

I think it makes sense to have Facebook use the title and description from the metadata on our website, and to fix those if necessary.

Consider that the FB button inside the extension's bubble UI, isn't the only way to share on Facebook. So we should make sure that those metadata are correct and complete.

Or do I miss something here?

comment:6 Changed on 08/27/2014 at 01:19:15 PM by sebastian

  • Cc saroyanm sebastian added; removed

comment:7 in reply to: ↑ 5 Changed on 08/27/2014 at 03:16:26 PM by saroyanm

Replying to sebastian:

I think it makes sense to have Facebook use the title and description from the metadata on our website, and to fix those if necessary.

Yes anyway it make sense to fix the metadata because if you will try to share for example current link post description is in English again, while we have correct metadata in German version of the website, so not sure why it takes again English text from
I think we need to create another ticket for website fix.
And maybe after fix we will need to generate correct link according to the platform language and use English link for the missing website languages.

comment:8 Changed on 08/27/2014 at 04:40:59 PM by saroyanm

  • Blocked By 1274 added

comment:9 in reply to: ↑ 5 Changed on 08/27/2014 at 04:42:36 PM by saroyanm

Replying to sebastian:
I've created another ticket for fixing metadata issue in website:

comment:10 Changed on 08/27/2014 at 04:43:38 PM by sebastian

Thanks. I was just about to do it myself. :)

comment:11 Changed on 08/27/2014 at 04:45:20 PM by sebastian

  • Component changed from Unknown to User-Interface
  • Description modified (diff)
  • Platform changed from Safari to Unknown
  • Priority changed from P2 to P3

comment:12 Changed on 10/21/2014 at 12:39:26 PM by greiner

  • Cc greiner added

comment:13 Changed on 08/09/2017 at 10:51:46 PM by juliandoucette

  • Blocked By 5447 added; 1274 removed
  • Tester set to Unknown

This bug should be fixed by #5447.

comment:14 follow-up: Changed on 08/17/2017 at 06:46:46 PM by juliandoucette

Scratch that. It looks like the locale is not being sent to Can you look into this greiner?

comment:15 in reply to: ↑ 14 Changed on 08/18/2017 at 03:39:32 PM by greiner

Replying to juliandoucette:

Scratch that. It looks like the locale is not being sent to Can you look into this greiner?

I guess you're referring to the fb_locale query string parameter?! Because their documentation mentions

When Facebook needs to render an object in one of the specified locales, we will make a request to the object URL with the fb_locale URL parameter set, e.g. &fb_locale=es_ES. The app should then return the object markup in that specified locale.

If so, it sounds like we'd have to handle this parameter in our server-side routing logic because currently returns the English version.

comment:16 Changed on 02/12/2018 at 10:24:22 AM by agiammarchi

We are removing share stats so I wonder if this ticket makes sense now.

comment:17 Changed on 02/14/2018 at 02:01:28 PM by greiner

  • Component changed from User-Interface to Websites
  • Priority changed from P3 to Unknown
  • Ready unset

It's indeed no longer a concern for UI since we're going to remove share functionality from both the icon popup as well as the first-run page.

The underlying issue still remains though. Facebook's crawler will fetch the English version of the page whenever someone shares a link to Therefore I'll set the module to Websites.

comment:18 Changed on 02/21/2018 at 05:30:33 PM by juliandoucette

I believe that the websites part of this issue was resolved by #5683?

comment:19 Changed on 02/21/2018 at 05:50:42 PM by greiner

  • Resolution set to invalid
  • Status changed from new to closed

Indeed sounds like there's nothing to do anymore. I'm closing it as "invalid" then.

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none).
Note: See TracTickets for help on using tickets.