[JUM] Multi Language 2.0.2

[Jumuro]

Jumuro submitted a new resource:

[JUM] Multi Language - additional criteria to display content (nodes)

This plugin will allow you to specify in the settings of the node (of any type) the display criterion for users with a specific language.

Read more about this resource...

 

[Assadi]

Hey, cool. Thanks for taking the time to work on this

Closer to replacing my WoltLab license; good multi-lingual support is the only thing really missing from XenForo.

 

[Kintaro]

@Alfa1 are you interested in this?

 

[Alpha1]

@Alfa1 are you interested in this?

Im not 100% sure what it does as there is no description. You can set a node to display depending on the language the user has chosen. But its not clear if the page language of the node and its content is also set to the appropriate iso code in the html.
To display nodes only when a specific language is set requires a good language selection interface. The default language selector hidden at the bottom of the page will not work. A clear flag at the top is needed.

It looks interesting. I could use it if the other functions are also available somehow.

 

[Jumuro]

Im not 100% sure what it does as there is no description. You can set a node to display depending on the language the user has chosen. But its not clear if the page language of the node and its content is also set to the appropriate iso code in the html.
To display nodes only when a specific language is set requires a good language selection interface. The default language selector hidden at the bottom of the page will not work. A clear flag at the top is needed.

It looks interesting. I could use it if the other functions are also available somehow.

You can see an example implementation of this plugin here.

 

[Kintaro]

are you going to add the possibility to separate in some ways languages in "new posts/recent posts/recent activity" too?

 

[Jumuro]

are you going to add the possibility to separate in some ways languages in "new posts/recent posts/recent activity" too?

This is much more difficult to do. Maybe I'll do it soon.
But while I promise nothing.
At least our community doesn't need this opportunity yet.

 

[sbj]

So from what I understand this addon "hides" forums according your chosen language?

If that is the case, this can also be done by creating usergroups and promotions.

 

[Jumuro]

So from what I understand this addons "hides" forums according your chosen language?

If that is the case, this can also be done by creating usergroups and promotions.

Before, we have something like this happened. But this is wrong and not an elegant method.

 

[sbj]

Before, we have something like this happened. But this is wrong and not an elegant method.

I agree that it is not elegant, but at least then you don't have the problem of "new posts/ recent posts" showing. They won't eb shown by default when done by moving people to usergroups.

But yeah, when it comes to language management, xf barely cares, as most forums are monolingual.

 

[Alpha1]

Please consider to add a flag drop down at the top of the screen.

 

[Jumuro]

Please consider to add a flag drop down at the top of the screen.

I don't know exactly what you mean. Please specify.

 

[Alpha1]

Currently if you want to change your language you need to go to the left bottom of the page.
Instead, place a flag icon at the right top of the screen. Same as burning board has: https://community.woltlab.com/

 

[truonglv]

Hello. I have found an issue of this add-on.

$structure->columns['language_id'] = ['type' => Entity::INT, 'default' => ''];

It's should be 0 cause you are use Integer type.

 

[Sperber]

@Jumuro ,

could you please check that? I stressed Truong more as enough with that for a few days until he looked into it, as it collides with his Social Groups addon (Thanks, @truonglv !).

 

[Jumuro]

Hello. I have found an issue of this add-on.

$structure->columns['language_id'] = ['type' => Entity::INT, 'default' => ''];

It's should be 0 cause you are use Integer type.

Thanks for the observation

 

[Improvs]

What about 2.1?

 

[kick]

Again violation of standards:

The following should be adhered to with respect to schema changes:

1. New tables must be prefixed with xf_ and additionally an identifier for the add-on e.g. xf_mg_.
2. New columns to core tables must be prefixed with an identifier for the add-on e.g. xfmg_.

 

[Chris D]

Again violation of standards:

The following should be adhered to with respect to schema changes:

1. New tables must be prefixed with xf_ and additionally an identifier for the add-on e.g. xf_mg_.
2. New columns to core tables must be prefixed with an identifier for the add-on e.g. xfmg_.

There are no new tables in this add-on but there are additional columns added to core tables so they should be prefixed ideally.

This vastly reduces the possibility of issues should another add-on attempt to add columns with the same names or, significantly, we ever add columns with those names.

There have been many failed upgrades in the past due to poor naming conventions hence why these points exist in the standards and should be addressed.

 

[Chris D]

@Jumuro please provide an ETA as to when the reported issue will be resolved.