Translation categories by Falang in Frontend OK, in Editing-view only main-language

Hello,

I have translated partially the categories by Falang and in frontend-view is all ok. - Categories will be showed in right language so fare the categories are translated.

But when I want to create a new item oder edit an item in category-selector for main- and secondary-categories will only be showed the main-language. In my case german.

is it possible to show categories in current language in editing-view?

update:
error-message in apache-log-file while editing an item
PHP Notice: Undefined variable: relativePath in /var/www/regiocenter/modules/mod_falang/tmpl/default_dropdown.php on line 48, referer: regio.center/de/?view=item&task=add&maincat=136

error-message in apache-log-file while category-view
[Mon Jun 06 18:49:36.478209 2016] [:error] [pid 7118] [client 91.89.200.160:33195] PHP Notice: Undefined variable: relativePath in /var/www/regiocenter/modules/mod_falang/tmpl/default_dropdown.php on line 63, referer: regio.center/de/

can it be this is a Falang-error and not a FC-error?

update2:
in a fresh joomla-installation only with Falang without Flexicontent it is exact contrary. Editing-view: category will be translated, Frontend-view: Categories only be showed in main-language, but without any errors in log-files

update to update 2 :ohmy:

When only one item is in category-view - category will be translate. Only in Default Page - categories will be never translated.

Flexicontent: 3.0.14-rc2a Release date: 2016-03-23
PHP Built On Linux d10236 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64
Database Version 5.6.15
Database Collation latin1_swedish_ci
Database Connection Collation utf8mb4_unicode_ci
PHP Version 7.0.7-1~dotdeb+8.1
Web Server Apache/2.4.10 (Debian)
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.5.1 Stable [ Unicorn ] 05-April-2016 22:45 GMT

an additional question to Falang and Flexicontent:

Are there ambitions to find a way for translating field-values by Falang in FC or will it never be possible?

please think we do a free powerfull component, with free support ... 100% benevol ... we need time to check it
all your error is on falang code not flexicontent
you can ask to falang support too not ?
joomla translation work perfect with core system we try to do our best to support 3dth party for free but need time and return

Sry, I know you get no money for your great work. I also doesn`t want that you solve my problems. I didn`t know there is an actually error in constellation fc / Falang and php7. Ok, when in your cases all is OK, I will find the reason.

Nevertheless, many thanks for your time and help.

ask to phalang about php7 flexicontent is already ok

Thx, I know the way...

Hello

yes in editing view, the categories names in the selector are not translated because
- we use cached data to speedup ACL checks for the category selector

but we can use these cached data and also make a single SQL query with minimal / small performance cost if falang is installed

I have added this issue with v3.0.16 milestone
github.com/FLEXIcontent/flexicontent-cck/issues/572

note this will be done only for frontend item form, probably will not do for backend item form

Hello,

thank you for adding this on github as issue. But Falang also with this feature seems to be at the moment not the best solution for my project.

Reasons:
1.) no directly translation of values
2.) an another additional complex extension (additional risks and performance requirement)
3.) the language switcher shows any languages to switch and not only available translations
4.) full item translation in my view too cumbersome for the most user

I create separate sites for each language and looking for a solution for the translation and the connection of translated items by Ajax. That seems to be in my case easier to handle.

If I should find a solution, I can public this in fc-forum or send you a message with the solution, if you want. Perhaps you want to integrate this in your project for other user of flexicontent.

Regards and thank you for your work and flexicontent

why you didn't use joomla native system ?

In my view the steps to translate an item are too many (for a normal user). I think it`s also too complicated for these kind of users (creating / batch using / connecting to other items and so on)

I think all needed steps to translate an item should be possible in frontend and an item should be translated after max 3 steps.

• 1.) open an available item
• 2.) override this in new language
• 3.) save these item as new item in new language. -that`s all- (connecting to each language automatically.

and additional conditions:

• two language switcher - one for the whole site, that switches the language for any items, menus and so on - and one switcher in each item, that switches or translate only this item, especially for category view. ( I think this is useful, when not all items were translated or a user want to read in a specific language and doesn`t understand only this or apart from this item )
• the language switcher should only shows translated languages and not all installed languages