Falang and Fabrik for J3+ Multi Language

Bongo1111

New Member
Hi I just modified the content elements for jomfish made by Manel Zaera to work with Falang. It works for me so if anyone needs a multilanguage site, here you go. Install the zip from falang content elements installer and test it. It translates elements, forms, lists, groups and visualizations.
Best regards!
Bobby
 

Attachments

  • Falang Fabrik Elements.zip
    2.6 KB · Views: 541
I think this would be useful to many however your files do not seem to match the Fabrik 3.1 files I have.

I think it would be helpful if you could explain further what you did to enable this - or maybe even create a new wiki entry "Multilingual forms with Falang".

Thanks.
 
Hi Sophist, I do not understand what you mean by saying my files do not match yours. Just install the zip via the Falang installer under content elements menu and in translation you should be able to view fabrik lists, forms etc. next to the language selector. I`ll make the entry in the wiki this afternoon with screenshots or even small video, but please explain what exactly is not working for you.
Best Regards!
Bobby
 
Apologies for not being clearer. As an example, your fabrik_elements.xml looks like this:
XML:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<falang type="contentelement">
  <name>Fabrik - Elements</name>
  <author>Manel Zaera, manelzaera@yahoo.es Benjamin Rivalland - www.decisionpublique.fr</author>
  <version>1.8</version>
  <description>Definition for Fabrik  Elements</description>
  <reference>
<table name="fabrik_elements">
<field name="id" translate="0" type="referenceid">ID</field>
<field name="name" translate="1" type="titletext">Name</field>
<field name="label" translate="1" type="titletext">Label</field>
</table>
  </reference>
  <translationfilters>
    <keyword>label</keyword>
    <fabrikgroup>group_id</fabrikgroup>
    <author>created_by</author>
    <published>published</published>
  </translationfilters>
</falang>
whereas mine looks like this:
XML:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<joomfish type="contentelement">
  <name>Fabrik - Elements</name>
  <author>Manel Zaera, manelzaera@yahoo.es Benjamin Rivalland - www.decisionpublique.fr</author>
  <version>1.8</version>
  <description>Definition for Fabrik  Elements</description>
  <reference>
<table name="fabrik_elements">
<field name="id" translate="0" type="referenceid">ID</field>
<field name="label" translate="1" type="titletext">Label</field>
<field name="default" translate="1" type="textarea">Default</field>
<field name="sub_labels" translate="1" type="textarea">Sub labels</field>
<field name="created" translate="0" type="created_date">Created</field>
<field name="modified" translate="0" type="modified_date">Modified</field>
<field name="checked_out" translate="0" type="checked_out_by">Check out by</field>
<field name="checked_out_time" translate="0" type="checked_out_date">Check out date</field>
</table>
  </reference>
  <translationfilters>
    <keyword>label</keyword>
    <fabrikgroup>group_id</fabrikgroup>
    <author>created_by</author>
    <published>published</published>
  </translationfilters>
</joomfish>
So the Falang one is much shorter than the Joomfish one. But now I think that I didn't understood them properly first time. Can you just confirm that the extra lines are not needed?

And now I am wandering about whether they can coexist given that they have similar filenames? Do Joomfish / Falang files need to be named like this?

S
 
In fact I had to remove those lines to get the elements to work. If you don`t, it will give you an SQL error. So just use mines and will be ok.
 
Do they have to be named the same as the joomfish ones?

It would be helpful if you could name them differently in order to have both joomfish and Falang files in the Fabrik distro.
 
They are named differently:
<falang type="contentelement">

<joomfish type="contentelement">

so no harm is done if the files got the same names. You put the files in different places. Falang has its own directory and joomfish the same. I don`t know why you would need joomfish as it is not joomla3 ready or I am missin`something.
 
Yes - I had spotted the file difference. I guess we can probably put your files in a falang directory then. I will create a PR on your behalf to do this.

And you are right to say that joomfish is not yet J3 ready - but it might be in the future.

S
 
PR824 created for this for both F3.0 and F3.1.

I have put the files in /administrator/components/com_fabrik/falang_content, so if you could create a new wiki entry called "Multilingual sites using falang" to describe how to set up falang to use these files that would be very helpful.

Thanks.
 
I have explained twice how to use them.
Just install the zip via the Falang installer under content elements menu and in translation you should be able to view fabrik lists, forms etc. next to the language selector. The actual file directory is:

administrator/components/com_falang/contentelements/

So please just do it that way and post if any issue.
 
Ah - I see - once you put the files in this directory, the integration is done!! I can create the wiki on this basis.

I have moved the files and resubmitted the PR.
 
Hope everything works fine now and fabrik is multi language , what my original goal was. Besides - no duplicate lists, forms or content on site.
Best Regards!
Bobby
 
There is another step in order to translate the data entered by the user. You first need to use the same database prefix as for all joomla tables. When you create a new list be sure to set the prefix of the table in the data tab otherwise it will give you a SQL error. Second you will need to manually create a XML file with the tables you want to be translated for example fabrik_country.xml. See sample :
Code:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<falang type="contentelement">
  <name>Fabrik - Table Country</name> 
<author>Your Name</author>
  <version>1.8</version> 
<description>Definition for Fabrik Country Table</description>
    <reference>
      <table name="country">
            <field name="id" translate="0" type="referenceid">ID</field>
                    <field name="country" translate="1" type="titletext">Title</field>
            </table>
   
              </reference>
         
    </falang>

Third install the XML via the Falang Installer.
 
Please change in fabrik_elements.xml
<field name="label" translate="1" type="titletext">Label</field>
to
<field name="label" translate="1" type="text">Label</field>

Issue is that everything works fine in backend but translations are not shown in frontend.
That must be something with Falang itself. Can't find ?ny way of solving it any help is apreciated.
 
This is interesting but I guess you still can't translate tooltips and validations/error messages. can you confirm this?
 
You can add <field name="params" translate="1" type="textarea">Parameters</field> in the fabrik?elements xml and you can translate the tooltip. Errormsgs as well are supported but what drives me crazy is that no Fabrik translations are shown on frontend. All is in english. in the back and in the DB everythink is transletable. Heelp:(
 
Please change in fabrik_elements.xml
<field name="label" translate="1" type="titletext">Label</field>
to
<field name="label" translate="1" type="text">Label</field>

Issue is that everything works fine in backend but translations are not shown in frontend.
That must be something with Falang itself. Can't find ?ny way of solving it any help is apreciated.

PR-829 created for this. It will first be merged into F3.0 and then eventually into F3.1.
 
After joomla latest update to 3.1.4 Falang stopped working thus givin'me 500 layout default not found error.
I am totally frustrated now, wondering if it is possible to create multilanguage component using..Fabrik. There is no one single quality component for the job by now , so it would be great to create one. Is This possible with Fabrik?
 
Well, Joomla 3.1.4 was only released a few hours ago, so you are probably one of the first people to install it - and I guess you are seeing some teething problems. I suspect that this is just a minor incompatibility between falang and the very new bright and shiny version of Joomla.

Have you:

1. Tried to reinstall falang?

2. Contacted falang support to see if they need to fix something to make it work in 3.1.4?

To answer your final question, I would imagine that it would be possible to use Fabrik as the basis for managing translation workflow, and with php plugins I guess it would be possible to tie it into Joomla so it served translated content but it seems to me that it would be much easier to get falang back working again. Certainly I would not spend the effort trying to make the fabrik round peg fit the falang-like square hole, when the specialist solution falang is likely to be fixed quite quickly.

S
 
We are in need of some funding.
More details.

Thank you.

Members online

No members online now.
Back
Top