In drupal 5.x module i18n was functionality to choose the type of selecting nodes in different languages:

/admin/settings/i18n

Advanced settings -> Content selection mode:
- Only current language and no language
- Only current and default languages and no language
- Only default language and no language
- Only current language
- All content. No language conditions apply

But now I need to use Drupal 6.x for multilanguage on subdomains functionality, but in it (I try beta2, beta3 and HEAD versions) I can't find it!
Is it planned and not implemented today or maybe I need to install additional modules for it? Or may be I bad searcher? :)
If not implemented, does anybody have release dates or development versions for use?

CommentFileSizeAuthor
#5 lfilter-6.x-0.1-dev.tar_.gz1.79 KBmurz

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Version: 6.x-dev » 7.x-dev

It is not implemented, and is planned for Drupal 7. Please use i18n with Drupal 6 and you will get this functionality.

murz’s picture

murz
Primary language English
Location Yerevan, Armenia
commented

But I look that Drupal 6 have build-in module Content translation for multilanguage content that overrides some i18n functions in Drupal 5.x. How I can use it? Disable build-in module and use i18n?
I try to test a HEAD version of i18n for Drupal 6.x but it isn't working now with my current configuration. Does some working version of i18n for Drupal 6.x exists?

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

As with all Drupal 6 modules, you might need to wait for a stable release. I know Jose is working on porting the Drupal 5 features and using the Drupal 6 base when possible. He was one of the key people in implementing Drupal 6 language support so he knows how he plugs into it with i18n for Drupal 6.

Freso’s picture

Freso commented

Yes! (a.k.a. subscribing)

murz’s picture

murz
Primary language English
Location Yerevan, Armenia
commented
StatusFileSize
new lfilter-6.x-0.1-dev.tar_.gz1.79 KB

I try the dev version of multilanguage module, but it isn't work.
And I try to do my custom module with this functionality using some functions of i18n. I attach my version to message, maybe it helps somebody else, not only me :)

Freso’s picture

Freso commented

Murz: Perhaps you could take a look at this i18n bug which touches upon this? The current filtering behaviour of i18n (for D6) is definitely broken, and it would appear you now have some knowledge of how this may be fixed. :) If you make a patch, I promise I'll test and review.

murz’s picture

murz
Primary language English
Location Yerevan, Armenia
commented

Freso says: Perhaps you could take a look at this i18n bug which touches upon this? The current filtering behaviour of i18n (for D6) is definitely broken, and it would appear you now have some knowledge of how this may be fixed. :) If you make a patch, I promise I'll test and review.

I think this bug is a consequence of wrong working function i18n_db_rewrite_where(), which can't get right mode for selecting nodes and work with "simple" mode.
Because Drupal 6 beta 4 have all multilanguage functionality for my needs (and some functionality, that have dublicated i18n), but i18n module have a lot of ugly functionality for me, I decided to do a separated module lfilter.
But this module have many functions from cvs i18n module (i replace prefix from "i18n_" to "lfilter_") with some small changes. I think you can get it as example when writing a patch to i18n.

ar-jan’s picture

ar-jan commented

Subscribing (sorry, I was following #233242: Language selection requires i18n).

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented
Version: 7.x-dev » 8.x-dev

I am afraid this will have to wait for D8 :(

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Version: 8.0.x-dev » 8.1.x-dev
Issue summary: View changes

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: +stale-issue-cleanup

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

smustgrave’s picture

smustgrave commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

Since there's been no follow up and as a feature request going to close out. If still desired please re-open

Thanks all!

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.