Closed (fixed)
Project:
EU Cookie Compliance (GDPR Compliance)
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 May 2018 at 09:36 UTC
Updated:
7 Apr 2020 at 14:14 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
svenryen commentedIt's an old module, so we have carried along some legacy names for variables, as new ones were introduced.
I don't think this will be a prioritized task, but you're welcome to provide a patch. Please don't break backwards compatibility :)
If it's okay, I'm classifying this as a feature request, since it's not really a bug per se.
Comment #3
svenryen commentedComment #4
eduardo morales albertiHi, here is my patch to help you to rename that variables.
Comment #6
eduardo morales albertiUpdate patch.
Comment #7
eduardo morales albertiReady to review.
Comment #8
eduardo morales albertiComment #9
svenryen commentedThanks. The patch would need a port to drupal 7 before we can add this to the module.
Comment #10
eduardo morales albertiThe Drupal 7 patch is ready to review.
Comment #11
svenryen commentedThe problem here is that you're changing the template twig file. This means anybody who made a custom template will have to update their twig when these changes are introduced. I thank you for your enthusiasm in making this patch, but we can't change this variable in the theme and twig due to legacy reasons. It may break some sites when they upgrade the module.
We can make these changes, but we can't change the _theme() and the twig.
Comment #12
svenryen commentedComment #13
svenryen commentedSo just to clarify my previous comment.
The old template has a variable called {{ disagree_button }} . Some sites may have created a template in their theme folder to override the default template, using this variable.
When you introduce a new variable such as {{ more_info_button }} , you need to keep providing the old variable, even though that does indeed mean having duplicate variables for the same purpose.
We can't accept a patch that may break an existing site. Can you please update the patch so that it doesn't remove any existing variables? Let me know if this was unclear or if you have any questions.
Comment #14
eduardo morales albertiThank you svenryen, I'll work on it today.
Comment #15
eduardo morales albertiAdded deprecated variable disagree_button to avoid problems in customs templates.
Comment #16
eduardo morales albertiDrupal 8 Added deprecated variable disagree_button to avoid problems in customs templates.
Comment #17
eduardo morales albertiComment #19
eduardo morales albertiPatch needs update to apply in actual version.
Comment #20
eduardo morales albertiComment #21
eduardo morales albertiUpdate patch Drupal 8 to apply in the latest version.
Comment #22
eduardo morales albertiComment #23
eduardo morales albertiPatch applied successfully.
Comment #24
ijsbrandy commentedI was not able to use the patch from #21 with stable version 8.x-1.5. Attached patch to apply to stable version 8.x-1.5
Comment #26
svenryen commentedThe patch seems ok (although haven't tested it yet), but we need a port to Drupal 7 before this can be committed.
Comment #27
svenryen commentedDidn't notice there was a d7 patch in #15. Marking this for needs review. Thanks for the patches.
Comment #28
dennis_meuwissen commentedAttached a patch that applies to 1.8.
Comment #29
dennis_meuwissen commentedComment #30
svenryen commentedThe 7.x patch no longer applies, so I'll go ahead and patch 8.x to resolve this issue.
If anybody feels strongly about the 7.x patch, feel free to reopen the issue with an updated patch.
It's time to give some more love to the 8.x version, and accept that we can't keep adding every feature to the 7.x branch.