Гость
07 Май 2013 09:26

I am testing falang and mirror translation after reading Sergey tutorial

http://www.mintjoomla.com/community/knowledge/user-item/43-sergey/238-cobalt-multi-language-sites.html

I have tested that falang is working, infact I can translate correctly menu items, joomla default articles and module titles

But I cannot understand why it is not working for Cobalt records

What I did was go in frontend, switch from italian to english language and edit one record

it does not work, the record gets edited, but no mirror copy is being created at all...

am I missing something?

Последние изменения: 14 Сен 2015


pepperstreet VIP
Total posts: 3,837
21 Март 2014 10:31

Sergey We store names of categories on article save

?!? You mean "names" are stored with each article for each language? I thought this is all handled by ID's and relations. So, sec/cat name is stored once in the respective table. Not multiple times. (at least, this is taught in any developer/coder class in germany ;-) If you don´t follow this rule, you get no meal, no graduation degree, no job :D )


Sergey
Total posts: 13,748
24 Март 2014 06:55

pepperstreet Not multiple times. (at least, this is taught in any developer/coder class in germany ;-) If you don´t follow this rule, you get no meal, no graduation degree, no job :D )

You will not believe but this is what I was taught as well. But practice showed that 100% normalization is not good for performance. I will not listen teachers who got their degree in early 90's. They teach students what they had learned in early 80's, but that is no longer ture.

Denormalization is one of the greatest way to speed DB up. And Resources vs. Cobalt proofs that. This is by triggers was created for DB to keep data consistent across different tables.

But even that is not good enough. now we meet new era of document or key/value storages. Those performs better, scales better, managed easier, have no structure names no relation no normalization. Or at least those things means something different there.

So what we do is to store DB structure like ID relations but also save small JSON in records field that contain all categories of this article. This way we can list categories of the articles without making any additional query.


pepperstreet VIP
Total posts: 3,837
24 Март 2014 18:07

Sergey what we do is to store DB structure like ID relations but also save small JSON in records field that contain all categories of this article.

I see. Sounds practical from article point of view. But sounds strange to me for category name changes and multi-lingual usage.


pepperstreet VIP
Total posts: 3,837
11 Сен 2015 00:52

Just curious about FaLang v2.x
It seems to have new plugins and frontend feature.
Any new chance or reason to use Falang for Cobalt Records translation!?


Sergey
Total posts: 13,748
14 Сен 2015 16:01

pepperstreet Any new chance or reason to use Falang for Cobalt Records translation!?

Would be nice I think. let's see if we have more requests.

Работает на Cobalt