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.I was troubleshooting this issue #814428: latest 6.x-1.x-dev (2010-May-22) used with Views 3.x and CCK 3.x dev versions I was having with Views Galleriffic when I came across this bug...
I almost always use dev versions of modules wherever available, cause I want to help the development with testing. So, I followed all the 2.x series of dev before I switched to 3.x dev of Views at some point at the start of 2010. I had already created a view with 2.x and now I was trying to troubleshoot this issue. The developer of Views Galleriffic suggested I disabled the 'Group Multiple Values' setting on fields used. No matter what I tried, even when saving the view and getting a message saying that it was saved successfully, the setting was not switched off. I tried downgrading to different dev versions of Views 3.x, but none worked. I then tried with the latest version of 2.x dev and I then was able to disable the setting.
So, I guess this is an issue with the upgrade path from 2.x to 3.x. I am not sure if the same thing happens with other field settings or views' settings in general, but if the developers decide to work on this one I am willing to help track it down and squash it. So, let me know.
PS: It would be nice to know if others had similar issues after upgrading from 2.x to 3.x.
PPS: I hope this is no duplicate, cause I'd hate me for adding to an already big issue queue. I did try to search for similar issues, but perhaps I wasn't using the right search terms. So, sorry beforehand if it is a dup after all.
Comments
Comment #1
klonosTurns out that after upgrading to Views 3.x and editing/saving views previously created with 2.x, auto-enables the 'Group Multiple Values' setting for fields. What is worse is that there is absolutely no way to switch it off! The message shows saying that the view was successfully saved, but the setting is always on!(?)
Temporarily switching to Views 2.x allows you to switch the setting off and then you can once again switch to Views 3.x. The thing though is that trying to edit/save the view at a later point, once again auto-enables the setting. The only relatively-user-friendly workaround I came up with is this stupid switching between 2.x and 3.x versions of Views, but that is not a real solution.
I honestly don't know what causes Views to 'lock' this setting and I didn't experiment with other settings, but I will test this in a vanilla setup (to eliminate interference of other modules or custom themes) and report back.
Comment #2
merlinofchaos CreditAttribution: merlinofchaos commentedYou need to upgrade to the latest CCK -dev to get that field to save properly.
Comment #3
klonosI use 6.x-3.x-dev (2010-Jan-26) of CCK. Isn't that the latest dev?
I see that CCK 2.x dev is dated 2010-May-29, but I thought that 3.x is where the action is. Maybe I am wrong.
Comment #4
klonosPerhaps I need to start a new issue in the CCK's queue about syncing 3.x dev with latest changes in 2.x dev then (?)
Comment #5
dawehnerklonos: Download the new version. The dev release just got published at this date, but the code is newer.
Comment #6
klonosDownload which version of what module (CCK or Views?). Do you mean I need to re-download the CCK 3.x dev?
Comment #7
dawehnerCCK. Download the current development version of cck. Thats totally not a views issue.
Comment #8
klonosThanx dereine, but I've figured this one myself already as you can see in #3 & #4. The thing is that I am not so sure on downgrading from CCK 3.x dev to 2.x dev (even though people say that there have been no db changes here: #791256: downgrade from CCK3 to CCK2).
Anyways, I've let people know in these two issues in the CCK queue (they seem the more relevant ones):
#690140: Status of CCK3 and plans for D7 (post #50)
#717608: Cannot save 'Group Multiple Values' option in Views 3.x (post #3)
Comment #9
klonos...changed title to reflect latest findings.
Comment #10
markus_petrux CreditAttribution: markus_petrux commented@klonos: The same patch was applied to both branches of CCK.
http://drupal.org/cvs?commit=319610 (CCK3)
http://drupal.org/cvs?commit=319604 (CCK2)
Comment #11
dawehnerAs i said. There is a difference between the date showed in the release annoucement and the latest change.
The date in the release annoucement describes the date when the accouncment was changed last, but this has nothing!! to do with the code.
Comment #12
klonosHow about md5 checksum then? I checked and they are same with the version I had already downloaded.
I re-downloaded the 3.x version just to make sure and I am using this one now.
Comment #14
klonosI haven't confirmed this to be fixed (or not) and I am busy with something else atm. Let me set it to postponed till I find some time to do some more testing.
Thanx
Comment #15
dawehnerIt's fixed already :)
You can see this in quite a lot of other bug reports.
Comment #16
klonosok then, I'll have to trust you ;)
Comment #17
axtolf CreditAttribution: axtolf commentedHi,
I still have the problem.
I used last versions (DEV) of both modules, Views and CCK. I'm using them to create a calendar of events with differents views.
When I try to change "Group multiple values" for a date field to avoid duplicated entries, I got the error described above.
In the begin I used only the stable versions of the module, after reading these posts, I tryed to upgrade both module.
ALready tryed to delete the views created, delete all the module, rerun update.php, reinstalled both module and recreated the views.
Nothing changed.
Comment #18
dawehnerYou should know what you are doing when you update to views 3.x
I think you need the dev version of date and calendar too.
Comment #19
DamienMcKennaUnfortunately the Drupal 6 version of the Date module is no longer supported. That said, we appreciate that you took time to work on this issue. Should this request still be relevant for Drupal 7 please feel free to reopen it. Thank you.