Attached is a patch that does the following:

Allows admin to administer all languages for a site in one admin screen.
- For sites with large number of languages, I have one with 20, changing the language each time to administer each language is very time consuming
- I added a js file to make the admin screen easy to manage

Doesn't force users to accept for the same site in more than one language
- Currently if a user goes to the German language page, doesn't find what they are looking for, and then goes to a translated version of that page they must re-accept cookies
- This patch updates that so they don't have to accept for different languages if they use the same url

Code cleanup
Fix for #1588128: getCurrentStatus bug as well as update .module file to be in keeping with

Sorry that there are not multiple patches / issues for this.


Marcin Pajdzik’s picture

Category:bug» feature

I am changing this issue to a feature request as the #1588128: getCurrentStatus bug is fixed in 6.x-1.3

acouch’s picture

Category:feature» bug

I think it is a bug if a user has the pop-up screen reappear if they switch languages on the same site.

Marcin Pajdzik’s picture

Category:bug» feature

This is not a bug. The module is designed to work the way it works now. We can consider changing it so that it works the way you propose but we need some input form other people too. At the moment I don't know if what you are suggesting will be acceptable by the regulators. We also need to consider different ways a multilingual site can work. If the different language versions are set on different domains, can we still consider it as the same site? We need more discussion on this one.

Marcin Pajdzik’s picture

Status:Needs review» Postponed (maintainer needs more info)
acouch’s picture

It is a bug if a user has to click the same notice twice because they have switched languages on a site that does not change URLs when changing languages.

ie Switching from:

will require the same user to have to click the warning a second time. I can't think of a good justification for that. This patch fixes that.

With this patch, if the site is setup so different languages are on different domains then the user will also have to re-click the warning which makes sense since they are changing domains.

Denko’s picture

I have problem with the same bug in both version for D6 and D7.
My sites use Danish and English. Users have to accept cookies twice if they switch language - and that is not a requirement of the (Danish) "cookie-law".

Marcin Pajdzik’s picture

Ok, would any of you be willing to update the patch provided in this issue so that it works against the newest dev version? If so, then I will apply it, test it and commit.

Marcin Pajdzik’s picture

Status:Postponed (maintainer needs more info)» Closed (won't fix)

Closed due to lack of activity. Feel free to reopen if you want to provide a patch for this feature.

d.clarke’s picture

Version:6.x-1.x-dev» 7.x-1.x-dev
Issue summary:View changes
Status:Closed (won't fix)» Needs review
new17.17 KB
new2.78 KB

I ran into both of the issues addressed in this ticket. I've updated the original patch to apply against the 7.x-1.x branch. Also since the original patch addresses two different issues I've split the patch into two separate patches so that issues in one patch won't hold up the other piece.

Manage_all_languages_on_one_page-1593568-9.patch - Puts all the language config fields on one page and shows/hides the fields for disabled/enabled languages.

Remove_per_language_cookie_policy_acceptance-1593568-9.patch - Changes the user experience so that users don't need to accept the cookie policy per language.

Denko’s picture

Thank you d.clarke,

Remove_per_language patch worked for me.

friera’s picture

Both patches worked for me

Thank you

jcnventura’s picture

Status:Needs review» Needs work

Just my 2 cents:

1. THIS IS EXTREMELY USEFUL!! Even if it is a feature, and not a bug, please commit it.
2. Do we really need to setup all admin fields for all languages? I'm pretty sure that even if you have 20 languages, in 99% of the cases you'll want to setup most fields exactly the same, except for the message fields and the privacy policy link.
3. On the question that each user should accept the request once per language, I think this should be decided by the site admin. Would it be possible to add an extra setting where that behaviour can be configured.

Marcin Pajdzik’s picture

Would anyone want to become a co-maintainer and help with testing and committing this and other patches? I am busy working on non Drupal projects and can't give this module enough attention right now.

svenryen’s picture

Hi Marcin! I found this module really useful, though I also ran into the same issues that have been reported here in the issue queue, and ended up applying patches to make it work. I work with module development full time now, and would like to offer a hand. How do I best get in touch with you to become a co-maintainer?

  • Commit 3935e3e on 7.x-1.x authored by d.clarke, committed by svenryen:
    Issue #1593568-1 by d.clarke, acouch: Don't Make Users Agree in More...
svenryen’s picture

The popup will now only display once for all languages. The patch for editing all languages on one page (Manage_all_languages_on_one_page-1593568-9.patch) might go stale, since there's been a lot of changes to the code the last few days. @d.clarke or @acouch (or anyone), would you be able to check out the current 7.x-1.x and make a new patch?

  • Commit 3935e3e on 7.x-1.x, 7.x-2.x authored by d.clarke, committed by svenryen:
    Issue #1593568-1 by d.clarke, acouch: Don't Make Users Agree in More...