Drupal 6 moving out of dev

I agree. I use viewfield in an intensive way for solving very different problems:
- I use a unique content type which change the view in a viewfield field: simplifies the development and offers a lot of flexibility.
- I use view field for a recursive hierarchical structure
- When nodes are atached to other nodes (using node field), viewfield is a good solution for viewing the atached nodes in the father node by means of a fashionable view.
- I format a node using a view of the node. This view is included in the node and shows a fashionable presentation of the node. For me is a better solution than the static and low level formatting provided by Content template

You can see http://aporia.ugr.es/lsi/jparets (it includes 4 viewfields fields)

For me viewfield is one of the most useful and flexible modules in drupal. I love it and I am using it in a production environment (I know, it is dangerous, but no module in drupal offers so elegant and simple solutions than view field). I tried with node reference or including a text field with php but....
I think viewfield is the (atomic) bomb because it is a way of dynamizing (chanching the views) the dynamics (views)

Best regards.

We can not contribute the D6 translation of this modul on the http://localize.drupal.org, becasuse many Localization Servers skips the development snapshots (l.d.o too). See: http://localize.drupal.org/translate/languages/hu/view?project=viewfield There is not a d6 version in the release combo, so we cannot translate and contribute our d6 translation of this modul.

Please, make a D6 release!

I'd like to see this happen, too. Nice work!

I'd like to see this as well; for one thing, this module is recommended by the Multiple galleries and taxonomy site recipe.

would really love this too! like rhelwig and others, would make things a lot less awful for getting this site we have off Drupal 5 once and for all.

Subscribing... We probably need to accomplish this soon so that we can start moving Viewfield to a Drupal 7 (and Views 3!) version.

--Ben

Subscribing.

subscribing. gonna use this one on a new project - all these comments make it look pretty stable ;)

Still no news ey? Wonder if this thread is actually read by the maintainer...

I understand people's concerns about using dev releases, but if you push maintainers to provide a release before it is actually ready, they'll simply rename the latest dev to 'stable' and get it released with whatever glitches might come with it. What good is that?

On the other hand, I do not understand this 'obsession' to only use stable releases. Do you realize that this doesn't help progress? Don't be afraid to try, but make sure you backup everything first!

I think that since there is a 6.x dev you should just go on and install it, test it and report bugs back in the issue queue. That will eventually help get a stable release out. This behavior I think should be adopted generally for all modules out there and not only this one. Nagging does not help. Testing and reporting back does. Please don't get me wrong, and do try and see this from the maintainers' point of view and do keep in mind this is open source. It takes time and that's how it works.

btw... the 6.x dev was updated to day.

PS: If it is of any comfort to anybody, I use only the latest dev versions of all modules in two of my production sites. They've been ok for more than half a year now. Even in some rare cases where some minor issues came up (usually after the regular weekly upgrade of any new versions), reverting to the previous dev I keep backed up saved the day. 90% of these cases were solved shortly after the issue was reported to the respective module's issue queue and a new dev was released to replace the faulty ones. So, have faith (but as Ive said remember to backup!).

PPS: sorry in case I took this issue off-topic.

Well I totally agree with you there klonos. I have used the dev version of viewfield in 3 live sites now without problems!
Because I haven't encountered any problems I was wondering why it wasn't released as a stable version yet!? :)

Cheers

I guess because there are currently 8 critical bugs still withstanding. Even if some of these are 'false-positives' and thus not-really-so-critical, still there are critical issues to resolve.

I too like seeing stable releases out, but they are no good if they are forced.

Subscribe. This module is really great, thanks for it!

What klonos said. If you want to see a release, you need to help to squash those bugs.

I actually see 2 critical and both are fixed ;-)

Yes, I know... most of them were hanging around since 2008 and last week sun has set most of these to 'won't fix'. No reaction from users to that, so I guess good news.

...there is a new one btw in 'critical' and still 'active' :P

Before a stable release is done I would like to see something done about #416922: Viewfields reset to none after updating when Views name + display name > 32 characters (field_attached_view_vname too short).

You find my patch for this issue in comment #37 http://drupal.org/node/416922#comment-2835954

I am sorry, but I am not having this issue so I can test.

If you really want it in the next release, perhaps you can propose to set it to 'critical'. I always like to propose setting an issue to 'critical' and let the maintainer decide and set it so if they agree. Most of the times taking the initiative and setting it to 'critical' yourself you risk causing their wrath for messing with issues' status :P

btw, almost everyone uses the drop-down menu to set the priority, but only few of us take the time to actually read the link underneath it:

Descriptions of the Priority ...

+ stable

This issue is not fixed now. But it is only my point of view.