Posted by strellman on October 26, 2010 at 10:16am
3 followers
Jump to:
| Project: | NodeReferrer |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
When I change a relationship and make it required, click update and override, then look at the relationship again, it is still not required.
I am using Nodereferrer module and the field that the relationship is on is one built by the reverse nodereference. I have been having similar issues with field specifics not saving either. Not sure if the culprit is views3dev or Nodereferrer, but this works OK on Views2.11 Unfortunately I would like to use the group-by on Views 3, and also hope that finding this issue may help the community.
Not sure if related to http://drupal.org/node/670344
Comments
#1
If you would click override and update you would get what you need , at least in theory.
#2
Now I've got another problem. Going back to Views 2.11 appears to not be an option. I can't clone or import any views. Is there a procedure like update.php for going backwards?
user warning: Unknown column 'view_php' in 'field list' query: INSERT INTO views_view (name, description, tag, view_php, base_table, is_cacheable) VALUES ('testingclone', 'test clone', 'reg', '', 'node', 0) in /home5/.../sites/all/modules/views/includes/view.inc on line 1722.
#3
It's not our fault that you downgraded to the lastest stable of views.
Better downgrade to the dev version of 2.x-dev.
#4
So this seems to not be a Views problem, but a compatibility issue with NodeReferrer.
Using Views 6.x-3.x NodeReferrer information is not updated for either a field or relationship.
#5
Definitely a views 3 compatibility issue. This and other compatibility issues are making this module worthless to me even though it looks like it should do exactly what I want. I'll see what I can do to work on it when I get a chance.