Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Is it just me or is the alpha1 version not saving variables? If I hard code the variables in my config file everything works as it should, however if I remove them and just rely on the module nothing is saved. I reinstalled the module, cleared cache, and even tried the dev version. Is anyone else running into this?
Comment | File | Size | Author |
---|---|---|---|
#8 | jquery_update-not_saving_variables-2494283-8.patch | 1.8 KB | mpv |
#4 | not_saving_variables-2494283-4.patch | 1.13 KB | netsliver |
Comments
Comment #1
Shane Birley CreditAttribution: Shane Birley commentedI can confirm. Variables are not being committed and remain at installed defaults.
Comment #2
Christopher Riley CreditAttribution: Christopher Riley commentedI downgraded to a older dev copy before the settings were moved into a separate file and got the site back up.
Comment #3
TarKHaoS CreditAttribution: TarKHaoS commentedIssue confirmed here.
Comment #4
netsliverHi,
I have the same problem.
Try the attached patch.
Regards
Comment #5
Christopher Riley CreditAttribution: Christopher Riley commentedThank you for the patch. Would like to see it get committed unless the maintainers want to go a different route.
Comment #6
BrankoC CreditAttribution: BrankoC commentedMarked #2496425: Configuration fails to store some values as duplicate.
Comment #7
BrankoC CreditAttribution: BrankoC as a volunteer commentedNote that my solution in the duplicate issue was to set the #tree attribute of the fieldsets in jquery_update.admin.inc to FALSE. This will let Drupal store each field in its own record, rather than combine them per fieldset. This seems to be a cleaner solution than the one proposed by the reporter, but I am happy with anything that would fix this.
Comment #8
mpv CreditAttribution: mpv at gcoop Cooperativa de Software Libre commentedI don't like the solution in #4 because it's explicitly setting the variables in the validate handler. What @brankoc suggested in the duplicate issue seems like a better solution. Here's a patch implementing his suggestion.
Comment #9
Denes.Szabo CreditAttribution: Denes.Szabo commentedI have just tested the patch #8, seems fine, the admin page now saves the settings. Thanks @mpv!
Comment #11
RobLoachComment #12
RobLoachThanks guys!