In Site configuration -> Multilingual system, I have the content selection mode of my bilingual site set to "Current language and language neutral". This behaves as expected throughout the site, hiding pages from language-a when user is browsing using language-b. Except for the "Translation overview" page.
When accessing the "Translation overview" page, it seems that the content selection mode is ignored totally, and the menus display links to pages in *both* languages. This only happens when accessing the "Translation overview" page.
This can be more than just a small annoyance, as in sites where users have lots of languages - or lots of links in the menus - it can potentially populate the menus with far too many links, and break the theme's layout on the "Translation overview" page.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Multilingual settings + menu under English | 61.47 KB | icouto |
| #3 | Menu under Esperanto | 53.41 KB | icouto |
| #3 | Menu under Translation Overview page | 60.37 KB | icouto |
Comments
Comment #1
drewish commentedcould you post a screen shot demonstrating what occurs?
Comment #2
drewish commentedIf anything we'd need to be disabling the i18n query rewriting. Basically it's just getting in the way of what the module is trying to do. I'd suggest the Active Translation module instead.
Comment #3
icouto commented@drewish, here are the screenshots, as per your request.
This is a site I'm working on at the moment, and have just started. I've setup both languages (English and Esperanto), and I've setup a page on both languages - the page is called "About AEA" in English, and "Pri AEA" in Esperanto. The first screenshot shows the multilingual system setup, in English, and you can see that the menu displays only the English version of the page.
The second screenshot shows the "Pri AEA" page. The site is now being browsed in Esperanto, and you can see that "About AEA" is no longer in the menu, and has been replaced by "Pri AEA".
The third screenshot shows what happens when we visit the 'Translation Overview' (All) page: both pages show up in the menu. This happens regardless of whether we browse the page in Esperanto, or English. It seems like the Translation Overview page is ignoring multilingual system settings.
Comment #4
drewish commentedit's hard to tell because your screen shots didn't include URLs but i don't think it's really a bug in the translation_overview module. translation_overview doesn't have anything to do with the menu items displayed on it's pages other than the tabs. based on your initial report i'd assumed you were seeing the same nodes listed in the translation_overview table, not the menus. this is starting to sound more like an i18n bug or something with the menu system.
Comment #5
icouto commentedThis problem occurs *only* while browsing the Translation Overview page - it doesn't happen anywhere else in the site.
If there is anything else you'd like me to try and do to help troubleshoot, just let me know.
Comment #6
drewish commentedI've got no ideas what would be causing that. Unlike active_translation, this module doesn't take any steps to disable i18n so I don't know why you're running into it. If you figure something out please follow up.
Comment #7
icouto commented@drewish: leaving the issue marked as 'needs more info', seems to imply that there is more information that the developers need about the issue, from the users experiencing the problem. Because this is a totally reproducible and well-documented bug, I doubt that there is any more info that could be provided. As I said, if there is anything you'd like me to try and do from my end, please do let me know, and I'll gladly do it for you.
If you believe that this is *not* a bug in 'Translation Overview' itself, but instead, a but in i18n, or in Drupal core, then perhaps you could move this report to *their* project's queue. Either way, *something* should be done in order to get the issue resolved, now that is *has* been documented.
Comment #8
drewish commentedi've got very little patience for your tone but the other night someone suggested replying to issues like your mother was the person who'd submitted it. i'll give this technique a try and hopefully it'll help moderate my response. what the heck, i'll even be a bit verbose in case this turns into something i decide to copy and paste it into another issue when someone gets this demanding.
the first thing is that you're the only one that's reported running into it at this point. if there were three duplicate issues for this problem i'd be a bit more concerned. but with one person encountering the issue it's just as likely that you've screwed something up and didn't notice it. if there were several people the odds would clearly be pointing at me.
and let's not forget that basically this is a pretty trivial problem: you've got extra menu items on your translation overview page. who'll be seeing that? admins and translators right? it's not like ever visitor to your site is getting duplicate links, are they?
so put yourself i my shoes. how excited would you be to try to track down a relatively trivial issue that's only one person has run into? personally, i'd rather be working at getting #142995: Add hook_file and make files into a 1st class Drupal object committed for drupal 7.
at this point, i've calmed down and you're welcome to do what ever you'd like with this issue, leave it as needs more info, move it to the i18n queue, mark it as by design because you don't think i'm interested in fixing it. it doesn't make much difference to me. if you figure out something i'd love a follow up. if not maybe someone else will come along and have some additional information. but as it is i'm fine with leaving it as needs more info.
Comment #9
icouto commented@drewish: your unkind tone is totally unnecessary. Reading through my comments above, I fail to see what is it that I've done that has given you the right to be personally rude to me.
I've spent quite a lot of time trying to ascertain that this bug is reproducible. This included time setting up a test site, downloading clean versions of Drupal and necessary i18n modules, installing, configuring, etc. - to ensure that it was not something in my particular setup that was causing the problem. As reported above, this IS a reproducible bug - and reproducible on a CLEAN instal. I went through all this trouble, because I thought this would be *useful* to the maintainer.
I can imagine, that there are indeed more pressing issues that you could be working on at the moment. Nevertheless, trying to belittle the problem being presented to you is not going to help you in any way. What may seem to be a 'minor' issue to you, as I explained in a previous post, can be quite a big issue for others. In my case, because the menus in the Translate Overview page overpopulate, this throws the entire CSS layout - this happens even using the Garland theme - and this means that I would either have to redesign an entire new theme for the client, or deliver a product that behaves less-than-professionally when the client is using it.
You seem to believe that I'm the only person experiencing this. After searching through the forums, I don't believe so. I have seen the same problem being reported in other modules, elsewhere, and have come to believe your assessment that this may be a Drupal core issue.
I have been reporting problems with modules for a little while now, and have come across this situation before - ie., a problem that you suspect to be a module problem, turns out to be part of a core issue. In these situations, the maintainers simply report that to the users, and move the issue over to the appropriate core issue queue. That is the logical procedure, and no user minds that.
I have given you steps to reproduce the issue, and have repeatedly offered to troubleshoot further, or run any experiments as necessary. I have received no requests for further info from you, except for your initial request of screenshots, which I provided promptly. Nevertheless, you respond in a totally unnecessarily personal and aggressive manner, and go as far as suggesting that *I* can do "whatever I'd like" with this issue.
As long as you are maintaining this module, the issue is *yours*.
Based on your reply, I've marked this issue now as "won't fix", which is really what you are saying. Perhaps in the future, when you've got more time to troubleshoot these "minor" issues, you will eventually get around to this. Or perhaps others will see this in the database, and reactivate it at a later date.
Ideally, though, you should just spend an hour of your time, reproduce the bug in your own setup, and then report it to the appropriate Drupal team.
In the meantime, I am unfortunately having to remove "Translation Overview" from my sites. There is no point in adding a module that is supposed to provide extra goodness, but which creates unwanted problems - including the very unpleasant problem of having to deal with module maintainers with no manners.