fb_likebox.js uses en_EN as fixed language parameter for js.src.

Site admins need to be able to configure this if the sites language is other than English.

Related issue #2499463: Invalid App Id patch #9 makes fb_likebox.js file configurable.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

silkogelman’s picture

P.S.
I'm happy to create a patch for this when a final version of #2499463: Invalid App Id is committed.

I made a proof of concept already, so a patch is not that much work for me (or anyone else for that matter).
Drupal Facebook page plugin with configurable language

silkogelman’s picture

Facebooks official documentation about this:
https://developers.facebook.com/docs/plugins/page-plugin#settings

baekelandt’s picture

Hello Silkogelman, I committed the final version of #2499463: Invalid App Id are you still willing to provide a patch for the language issue (and for #2512556: Allow all page plugin settings to be configurable by user if you have enough time)? I don't think I'll have enough time to create one myself.

silkogelman’s picture

I am, I'll post patches for both issues next week.

Huelfe’s picture

FileSize
3.85 KB

In the zip file are the changes to choose a different language. Sorry for not creating a patch file, but for some reasons i had no time for it. I hope it will help! :)

drozas’s picture

Status: Active » Needs review
Issue tags: +dcnorth15
FileSize
6.39 KB

Thanks @Huelfe,

I have created a patch based on the .zip file that you submitted. Could you please verify that all the changes you suggested are included?

Thanks!

silkogelman’s picture

Tested and updated the patch a bit: the code from #5 works, but there was an array structure mistake in the patch from #6.

This updated patch should do the trick.

P.S.
Sorry for not letting you guys know I did not find the time to create a patch earlier as I described in #4.
I created a patch for #2512556: Allow all page plugin settings to be configurable by user but at that moment I didn't have the time for creating a patch for the current issue.

Huelfe’s picture

The patch from #7 looks good. Maybe the language array should be translatable?

silkogelman’s picture

I like the idea, and I'm happy to update the patch with t() wrappers.

And would it be nice if the list was ordered alphabetically?
It makes it easier for people to find their language.

Another bonus feature could be to create a select box that says 'autoselect users language' to enable an autoselect option that detects the users language.
That may be input for another issue though :)

Huelfe’s picture

Autoselect users language is a interesting feature! But you're right, this is another issue.

I agree with you. An alphabetically sorted array makes much more sense. Just make sure to sort the translated strings and not the default ones. :)

silkogelman’s picture

To have the current issue available for end-users as quickly as possible I suggest we test & commit the patch from #7 asap.

I created new issues for the other ideas:
#2541836: Translatable languages list
#2541840: Order the language list alphabetically
#2541844: Autoselect user language

szecsodimlaszlo’s picture

I can confirm that the patch from #7 is working.
Thank you.

baekelandt’s picture

Committed patch #7 and placed t() functions around the languages as suggested in #8 and #9 (see issue #2541836: Translatable languages list )

baekelandt’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.