Log in | Register
  1. Forum
  3. Discontinued Products
  5. JFBConnect Joomla 2.5 Support (CLOSED)
  7. Opengraph description problem with punctuation marks in Hebrew and K2

Topic-icon Opengraph description problem with punctuation marks in Hebrew and K2

Active Subscriptions:

None
14 years 2 months ago #21144 by emanuelr
Hello,
In K2, Hebrew, most of the time, when there is any punctuation mark in the beginning of the introtext, the created og:description includes a strange character at the end (but the rest of the text is readable and everything else is fine).
Then, when facebook reads it, it turns the title to Gibberish and the description is partial.
Example 1 with gibberish at FB (Hebrew of course, but you can still recognize Gibberish vs Hebrew ):
www.sh-taim.co.il/kithcef/meat/item/22-s...with-root-vegetables .

I wrote 'most of the time', because I have one link which has quotation marks in it's introtext, there the title is fine, but the description copied to facebook is only until the first quote mark appears. See example 2: correct title but description cuts to the first quotation mark .

For sure, if there isn't any comma, quotation mark, dot etc. - everything is fine.
It seams that a kind of escape or even complete removal with regex is needed in the process of generating the og tags.

Emanuel.
The topic has been locked.
Active Subscriptions:

None
14 years 2 months ago #21145 by mtk
Shalom Emanuel,
there seems to be a UTF bug with the Use beginning text in article for default, so if you are using the option try setting it to NO and manually set the meta description for all the content articles.

Let us know if that helped.

Mati
The topic has been locked.
Support Specialist
14 years 2 months ago #21177 by alzander
Emanuel,
Mati is correct, there is a bug with UTF-8 characters in JFBConnect 4.1. It will be fixed in the upcoming 4.2 release, due out later this month. Until then, if you're having issues, we'd recommend what Mati said.. disable the "Use beginning text in article" setting in the Open Graph area and either manually set the description with the {JFBCGraph description=blah blah} tag, or let JFBConnect use the meta description tag automatically.

Hope that helps,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 2 months ago #21193 by emanuelr
Thanks. I'm following your advice. So far it is OK (turning off the description and use the description from the meta-tag automatically).

By the way, there is another problem of UTF-8 compatibility in JFBConnect control panel - it is impossible to add default opengraph definitions. Once we save the changes, the non-Latin characters turn to ?????????

Emanuel.
The topic has been locked.
Support Specialist
14 years 2 months ago #21218 by alzander
Emanuel,
No clue why the defaults box is behaving like that, but I added it as a last minute issue to investigate for our upcoming 4.2 release (later this month).

Thanks for letting us know, and I don't see any reason why this shouldn't be fixed pretty soon.

Alex
The topic has been locked.
Support Specialist
14 years 1 month ago #21584 by alzander
Emanuel,
It's been a while, but I wanted to respond to this thread. We've been doing some testing with JFBConnect for our upcoming 4.2 release and can't recreate the issue you mention here. Each time we enter non-Latin characters, they work properly.

Can you check your database collation? I'd assume it accepts non-latin characters since your article contents and other things are likely using those, but it's the best thought we have as to why it's not working for you.

Tools like PHPMySQL can tell you the collation pretty easily, but if you're using the command line MySQL query command, you can enter the following commands to figure out what your database is using:
use <YOUR_DATABASE>;
show variables like "character_set_database";
show variables like "collation_database";
I believe the recommendation for Joomla is "UTF-8", whereas the MySQL default is "latin1_swedish_ci".

Please let us know how that goes for you. The other alternative that crossed our minds was if you have a 'security' extension of some sort installed. Since UTF-8 characters get translated into character codes, that could make some security software consider the use of them in database update statements to be 'risky' and break them.

Good luck,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 1 month ago #21631 by emanuelr
Hello Alex,
You are right, the database collation was set to the default Latin...
So I changed it to UTF-8-CI-General now.
But all of the relevant fields in the tables connected to JFBConnect, are still set to Latin. Is it because my DB was set to Latin before I installed JFBConnect, or it is because this is how you defined the tables?
Usually when I add a new table, by default I set every text or varchar field to utf-8 collation...

Of course, I'll modify your tables manually, but the will I have to deal with it again after upgrading to the next version?

Thank you for the time you put into it!
Emanuel.
The topic has been locked.
Support Specialist
14 years 1 month ago #21637 by alzander
Emanuel,
Our installation SQL file doesn't specify the collation of the tables at all. They should just inherit what the default is for your database. You can (if you care) view the actually SQL install files in the /administrator/components/com_jfbconnect/install/sql directory.

Our updates to the database tables, similarly, do not specify a collation. So, I'm not sure where that collation was set on those tables, but it's not something that JFBConnect is forcing on those tables. Once you set it manually, I don't think you'll have to deal with that as an issue again.

Hope that helps,
Alex
The topic has been locked.
  1. Forum
  3. Discontinued Products
  5. JFBConnect Joomla 2.5 Support (CLOSED)
  7. Opengraph description problem with punctuation marks in Hebrew and K2
From the Blog
Facebook | Twitter | LinkedIn | Blog RSS