Closed (works as designed)
Project:
Flag
Version:
7.x-2.0-beta5
Component:
Views integration
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Sep 2011 at 03:33 UTC
Updated:
19 Aug 2012 at 07:27 UTC
Whenever I try to add a flag relationship in views and even with a flag type chosen "Flag This", I get the error message in red:
You must pick a flag to use for the relationship "Flags: (Please select a flag) by current user".
This prevents me from saving the view.
Comments
Comment #1
quicksketchCould you describe how to reproduce this issue from a fresh view? There are a lot of different relationships you can add with Flag module, it's not clear which one is causing you trouble. It sounds like you have multiple relationships added to your view, one of which is not correctly configured. Try removing all the relationships and adding them again.
Comment #2
quicksketchComment #3
BeaPower commentedI was able to resolve this by using the views dev version.
Comment #4
apmsooner commentedI get this error too using views recommended version. To reproduce is easy, just add flag relationship of seemingly any kind and the error pops up. I specified the flag to be used on all views displays and the error shows no matter what. I even removed the relationship from all views displays to see if i had done something wrong and for some reason even with absolutely no flag relationship remaining, and after saving the view, the error persists as if the flag relationship is still there. I even deleted all flags and checked the view again, the error is still there. I guess its a views rc issue. Perhaps i should move to views dev version also....
Comment #5
Wario commentedSubscribe. Using Views 7.x-3.0-rc1.
Comment #6
artatum commentedsame problem here...
Comment #7
pierrecw commentedSubscribe
Comment #8
quicksketchPlease don't "subscribe" to issues, just use the new "Follow" button at the top of the issue to get updates.
Comment #9
kari.kaariainen commentedThis seems to be a problem of Views, not Flag. If there is only one display, there is no problem, but if there are more than one display, the relationship gets added to all displays no matter what you do. The added relationships are somehow misconfigured. The error message is not reporting which display it concerns. If it did, the problem would be easier to find. Nevertheless, tweaking the view by overriding and removing relationships won't help, saving will not be possible.
The same behaviour is happening or has happened with many other settings too, like fields, access, pagers etc. and many people seem to agree that the overriding behaviour needs overhauling.
Here are some of the issues concerning this:
http://drupal.org/project/issues/search/views?issue_tags=override-problem
Comment #10
pierrecw commentedok, work for me.
I create a new view with just one page with the relationship to flag:node and everything works fine !
Comment #11
alibama commentedThis is bizarre - am having the same issue in views 6 = recreating all the views is a pitiful option = i've got ~15 displays in this view and they are complex. anyone got leads on fixing this?
Comment #12
hitfactory commentedThis will happen if Views is not configured to show the Master display at admin/structure/views/settings because when you add the Flags: Node flag relationship to, for example, your Page view, the flag type doesn't get set correctly on the Master view.
The error being thrown relates to the Master display not to the display you're configuring. To get rid of the error,
1. Go to View settings at admin/structure/views/settings
2. Tick the 'Always show the master display' checkbox
3. Go back to your view where you will now see the Master display.
4. Either delete the Flags:Node flag relationship on the Master view or set the flag type.
Comment #13
ressaI was working with Openlayer maps, and changing "From: This page (override)" to "From: All Displays" under "Configure Relationship: Flags" fixed it, thanks!
Comment #14
ANDiTKO commented#12 Worked for me. Thanks! Still not sure if this is a bug or configuration issue.
Comment #15
joachim commented> The error being thrown relates to the Master display not to the display you're configuring.
Ah, that's a known problem in Views, which is now fixed: #1345934: default display being hidden makes it possible to be unable to save a view with validation errors. Hence closing here.