Module LanguageFieldTabs

[Soma]

Can we please remove this module from directory already? Every other installs this instead of the core one and runs into problems!

[renobird]

First time using this module (the core version). I have the module installed, and 4 LanguageText fields. How do I make them into tabs? I assumed there would be a new field type that I wrap them in, but nothing is showing.

Running the latest dev

[apeisa]

Tom, do you have more than one languages?

[renobird]

Hey Antti,

I do have language packs installed. Turns out there was some other weird stuff with the install as well.

Just setup a fresh test environment, and everything is working as expected. Sorry for the false alarm.

[inspeCTor]

Hi there, i ve just installed PW 2.5.2 in Multilanguage basic mode and am missing the Language Tabs Core Module, which should be available in core modules since PW 2.4. Am i doing something wrong?

Cheers Chris

[Soma]

It's right there, have you installed it?

https://github.com/ryancramerdesign/ProcessWire/tree/dev/wire/modules/LanguageSupport

[inspeCTor]

Hi Soma, yes physicaly its stored in wire/modules/ folder but doesn´t shows up in modules core nor install area. Is there a way to install it manually?

[Soma]

Have refreshed the modules cache? It may has to do with folder/file dates, as there was something added by Ryan which caused problems fro others, but can't remember and never had an issue.

[inspeCTor]

Yes refreshed cache already... it has no effect to modules list so far.

[inspeCTor]

Ok, there is something definitely going wrong. Once again i installed a new blank PW 2.5.2. Starting with no language support activated, but 4 language modules listed under core modules

Languages Support
Languages Support - Fields
Languages Support - Page Names

Languages Support - Tabs.

Installing one by one everything is fine until Tabs. I got an error message about an missing ID (Sorry i ve been to fast and closed message without copying).

Afterwards listing core modules the Languages Support - Tabs module wasnt listed anymore...

So... any ideas anybody?

[netzhoerer]

I have the same issues.
In Debug Mode i get a error:

 Modules: Module 'LanguageTabs' dependecy not fulfilled for: LanguageSupportFields

I also tried it with 2.5.4 dev

[LostKobrakai]

Any ideas regarding the LanguageTabs issue? I've the same one, but only with the version which is online. On my local dev server everything is working. 

PW-Version is 2.5.3

[arjen]

I just ran into some issues as well with several javascript errors like "setupLanguageTabs is not defined".

Looks like I had an old "templates-admin" folder in my /site/ folder. Deleting this fixed my issues.

[Michael van Laar]

Having the same problem here, I investigated a little and found a bug and a workaround.

First, there is a bug in LanguageTabs.module, lines 83 and 84. This prevents the JS and CSS file from being found.

Wrong:

$this->config->scripts->add($this->config->urls->LanguageTabs . "LanguageTabs.js");
$this->config->styles->add($this->config->urls->LanguageTabs . "LanguageTabs.css");

Right:

$this->config->scripts->add($this->config->urls->LanguageSupport . "LanguageTabs.js");
$this->config->styles->add($this->config->urls->LanguageSupport . "LanguageTabs.css");

But this doesn’t solve the bug that the module doesn’t show up in the Core section of the module list. The quick and dirty workaround to fix this: Move the file LanguageTabs.module from directory /wire/modules/LanguageSupport to /wire/modules 

 

Unfortunately I have no idea why this fixes the problem. I have not found any hint in any file which would indicate that ProcessWire doesn’t like the file LanguageTabs.module in the subdirectory /wire/modules/LanguageSupport

[Michael van Laar]

I opened an issue on Github mentioning the above findings: https://github.com/ryancramerdesign/ProcessWire/issues/919

[m-artin]

This is probably a future topic:

I'm wondering, if it's possible to divide the page content into tabs for each language? (in order to avoid having tabs for every textfield)

Let's say there would be just one tab per language next or below to the page content-tab. (e.g. could be called LanguagePageTabs) Wouldn't this be nice and resulting in a cleaner interface while editing? 

Especially with a couple of different languages and a few more content-fields I would find it easier to keep track of the content. 

Then of course the question is how to handle Non-MultiLanguageFields, which will have to be not editable and grayed out for example.

I guess such a different approach is a bit out of range for this great module. 

But anyway, I just want to share my thought.

P.s.

Because I only have a dozen pages with slightly a different structure and different images, I'm considering to build separate trees without using the multi-language modules. I stumbled upon the PageReferencesTab Module and my idea is to use it for referencing the different page-languages with the default one. 

This way the editor can jump from a page with the default language to a referenced different one. This is the idea so far 

[LostKobrakai]

I'm wondering, if it's possible to divide the page content into tabs for each language? (in order to avoid having tabs for every textfield)

Let's say there would be just one tab per language next or below to the page content-tab. (e.g. could be called LanguagePageTabs) Wouldn't this be nice and resulting in a cleaner interface while editing? 

Especially with a couple of different languages and a few more content-fields I would find it easier to keep track of the content.

You could build this by yourself with language alternate fields and fieldset tab: http://processwire.com/api/multi-language-support/multi-language-fields/#language-alternate-field-values. It's a lot more clicking to get this does, but it does work.

I think a automatic way wouldn't work as easily, as you can't depend on users having only a single tab with fields and duplicating 3 or 4 (or even more) tabs for each language will quite fastly lead to something, that's less clear than the current way. Maybe a "global" switch to change all fieldtabs of a page to the selected language would have the same effect, while keeping the current structure.

[m-artin]

Thanks Lostkobrakai, for your input and reminding me of the precious and easy to use fieldset tabs. 

I'm still overlooking these gems.