Hi,

has anyone started looking into a Drupal 8 port of select_translation?

Thanks,
Antonio

Comments

ao2 created an issue. See original summary.

ao2’s picture

OK, I started looking at the issue myself.

I converted the code to run on D8 but obviously the filter conditions need to be rewritten as well, based on node_field_data table because the node.tnid field is not there anymore.

I was wondering if the maintainers could create a 8.x-1.x branch with the latest 7.x code in it?
This way I can port things incrementally and share the work on the official repository.

Thanks,
Antonio

ao2’s picture

Hi,

I have the module working on Drupal 8, how should I publish it?

Can I have permissions to create the 8.x-1.x branch myself on the official repository?

Or do you prefer that I publish the changes somewhere else for the maintainers to review them before giving me direct access?

Thanks,
Antonio

alcroito’s picture

Hi,

I've granted you permissions for the project.
You can create a 8.x branch and push the code.

Regards.

ao2’s picture

@Placinta, thanks!

I pushed a first version of the working module.
All the steps can be followed in the git history.

Please note that for now I disabled the include_content_without_translation option, quoting from the commit message:

The "include_content_without_translation" option has been disabled for
now, because there is no immediate way in drupal 8 to characterize
content without translations, and maybe it does not even make sense.

Any opinion on that? I'd like to discuss that before closing this issue.

Thanks,
Antonio

ao2’s picture

Assigned: Unassigned » ao2
ao2’s picture

Version: 7.x-1.x-dev » 8.x-1.x-dev
Status: Active » Fixed

Closing, the 8.x-1.x branch now contains a version of the module which works on drupal 8.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.