As much as I would like to get into i18n some patches like this one #1182058: Add Entity Translation (entity_translation) support for menu items using Menu Translation I don't think we should be doing any kind of integration before there is at the very least a tagged release of this module (alpha, beta, whatever...)

The reason is that in the case of an API change of Entity translation this will leave us out in the dark with a bug but without any release tag to refer to on this module's side. So we won't be able to tell things like it works with this release of ET, but not with this other one.

So please if this module is somehow already working, which I believe it is, and development is still active (last commit is more than 2 months old?) and with intentions of going ahead, having tagged releases will help integration with i18n and possibly other modules.

Comments

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented
Status: Active » Postponed

The developemnt is still active, at least in theory. I had not much time to dedicate to it because in my agency we are not using D7 all the time so I have only my spare time to work on ET and most of my (few) spare time is taken by core work. I did not create any tagged release yet exactly to avoid breaking integration with other modules, since a major API change could be imminent, i.e. integrating CTools to solve issues like #1155134: Integrate pathauto bulk generation and #1123610: Menu item translation in a clean way. I hope to have this fixed soon.

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Status: Postponed » Reviewed & tested by the community

We can do alpha releases anytime (like, now). If that turns out to help others, we should do it.

Jose Reyero’s picture

Jose Reyero CreditAttribution: Jose Reyero commented

@sun,
Yes, an alpha release would be fine.

@plach,
That's exacly the point. While API changes in alpha releases should be ok, basically we need a way to tell 'this works with ET alpha1, but not with alpha2, etc..'

So I think at this point alpha releases would help everybody, including this own module issue tracking.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented

alpha1 will be available in minutes. To keep everything in-sync Title has an alpha release too.

Jose Reyero’s picture

Jose Reyero CreditAttribution: Jose Reyero commented
Status: Reviewed & tested by the community » Fixed

Thanks, that is great.

So I can tell you now next i18n versions will provide some minimal integration. Basically keep hands off nodes handled by entity translation, patch is here, #1182058: Add Entity Translation (entity_translation) support for menu items using Menu Translation

das-peter’s picture

das-peter CreditAttribution: das-peter commented

Awesome! :)
Thank you all for pushing this.

Status: Fixed » Closed (fixed)

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