Closed (works as designed)
Project:
Viewfield
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 May 2009 at 22:08 UTC
Updated:
1 Jun 2009 at 13:53 UTC
Dears
I was using viewfield for a long time to include in views (for instance, showing a node and its sub-nodes o showing a node and related nodes through viewfield.)
Things work wonderful and a I also implemented recursive views. But the last version (may, 24, 2009) destroyed my views. In addition nodes with an optional default value was automatically overrided.
I noted that the default value in settings dissaperad, is that true?
For instance, if you visit http://aporia.ugr.es/lsisecre the menu on the right is a recursive view constructed dinamically depending on node relationships.
Any idea?
Thank you.
Comments
Comment #1
darren ohThis version is still in development. The last update fixed issues with upgrading from the Drupal 5 version. Before this update, fields would set
<default>as the view name if the default value was not overridden. Now the default is indicated by an empty view name, as in the Drupal 5 version. Also note that the default value is a global setting, below the allowed views setting.If you were using the development version before, you should remove
<default>from your database to restore the previous behavior.We are still waiting on an update to the patch in issue 165321 to support recursion.
Comment #2
darren ohComment #3
jparets commentedDear Darren Oh, thank you for your explanations. In fact this solved an important part of the problem. I removed <<>default<>> and default views worked again.
But there is another important question: default viewfield fields DO NOT APPEAR when they are included in a view, i.e. views which includes a content of type viewfiled do not show results IF THE the viewfield field is set to default (non default or default overriden works well).
In fact recursion I am talking about implies the use of this possibility (including a viewfield into a view, including a viewfield in the same view set in viewfield).
I know that this version is under developement, in fact I installed each revision from 5.1 to 6.12 and I reported some problems, but I think the module can be used and it is very near of stabilility, isn it? . I am grateful to the effort in developing it and, for me, is the most powerful module that I am using in Drupal. In fact I think that should be included in the core of CCK (only my opinion)
Thank you again.
Comment #4
jparets commentedI reopened
Comment #5
jparets commentedI resend my comment. I have no response. Excuse-me.
Dear Darren Oh, thank you for your explanations. In fact this solved an important part of the problem. I removed <<>default<>> and default views worked again.
But there is another important question: default viewfield fields DO NOT APPEAR when they are included in a view, i.e. views which includes a content of type viewfiled do not show results IF THE the viewfield field is set to default (non default or default overriden works well).
In fact recursion I am talking about implies the use of this possibility (including a viewfield into a view, including a viewfield in the same view set in viewfield).
I know that this version is under developement, in fact I installed each revision from 5.1 to 6.12 and I reported some problems, but I think the module can be used and it is very near of stabilility, isn it? . I am grateful to the effort in developing it and, for me, is the most powerful module that I am using in Drupal. In fact I think that should be included in the core of CCK (only my opinion)
Thank you again.
Comment #6
darren ohThat is by design. See the issue I referred to in my first comment if you are interested in working on a solution.
Comment #7
darren oh