CCK fields not showing up in Views

I've been having this problem for months, and it comes and goes. Sometimes clearing all Drupal caches helps, other times it doesn't. I'm not sure if this is a CCK or Views problem, but it happens consistently (granted the "coming and going" nature can make it even more frustrating to track and solve).

There are 3 related issues:
http://drupal.org/node/271699
http://drupal.org/node/269516
http://drupal.org/node/227544 (this one)

I have turned off various cck related modules thinking at various points they were the problem, but even with all of these off and uninstalled, caches cleared, the problem still persisted.
I'm running Views 1.6, CCK 1.7, Drupal 5.7.

Thanks for your help.
-Michael

I can vouch for this issue and the frustration with trying to track down the problem. CCK fields randomly disappear and reappear from views...

This consistently affects views 6.x-2.x-dev (Sep-09).

Here is some info that might help someone track this down.

I just installed Drupal, views 6.x-2.x-dev (Sep-09) and CCK 6.0-2.x-rc6 and Advanced Help. To my knowledge I have done no configuration at all on this clean install except I enabled a theme, created a content type and then created some CCK fields for it.

I had the same symptoms described by the original poster (i.e. consistent, not coming and going) so I replaced the files with the views 6.x-rc-1. Now the fields can be seen = it works (after clearing cache). So there's a problem with the dev version of views.

Don't change versions on issues. The D5 code is totally and completely different from the D6 code and there is no possible way 'the same thing' can happen and have the same cause in both versions.

@fletchgqc : there has been a major API change in Views recently, so latest Views 6.x-2.x-dev will not work with CCK-RC6, you need to grab CCK 6.x-2.x-dev as well.

More generally, Views has changed so much between D5 and D6 that there are very little chance that switching an issue thread from D5 to D6 version makes any sense.
Setting this issue back to D5 branch.

Thanks yched.

Yeah since this issue has basically got 2 duplicates with the same posts in them I thought I'd commandeer this one. But I must admit I didn't consider the full views 2 rewrite.

If you ever think it's a good idea to commandeer an issue, stop, step back, and leave the keyboard.

The actual issue here is almost certainly about hook_init order; there are rare circumstnaces where a hook_init can trigger a views cache rewrite before another hook_init has happened to included views code. This causes those kinds of dropouts. Views can't fix these.

hah hah OK OK I get the message.

I have exactly the same problem

I have installed Drupal several days ago and later I've added the CCK and Views modules (I think, all were last versions)

I had been adding custom fields to existing data types and custom data types with custom fields as well, but none of them appears in the Views fields list. All the Drupal fields are there, but not mine.

Moreover, (in Views->Theme) Views fails to detect new templates, which I'm adding to the theme folder in the modules->views directory. But this is another issue. If at least the CCK fields issue will be solved, I will be already satisfied...

So could someone please tell me what is the latest configuration (Drupal + Views + CCK versions) which works for sure?

First of all, you're posting in a closed issue. Second, did you even bother to read this issue at all? Especially #4 and #5 where someone else tried to switch the version from D5 to D6 and was told not to do that. Any problem you are having in D6 is not ever the same as a D5 problem and the issues cannot be switched.

Sigh!

First of all, if this is a closed issue, someone should close the thread. The fact is that I was able to post here without any special privileges.

Second - I did read all the comments and I have consciously posted here, because this is the thread which is most related to the problems I'm having.

Third, I don't know who you are, and I basically don't care, but you should be much more polite. Nothing gives you the right to talk to people, whom you don't even know, this way. If you think you are very clever, leave this for yourself.

p.s. could someone please tell me what is the latest configuration (Drupal + Views + CCK versions) which works for sure?

Watermelonman: KarenS is one of the most respected developers of Views. She is absolutely right; and in your most recent response, you are flagrantly ignoring the rules that make this issue queue work. You will not get polite responses if you will not respect proper procedure in the issue queue. "Won't fix" is pretty much the same as a closed issue, and it's already been said that it's wrong to try to move a D5 issue to D6, yet you do it anyway.

Please stop. Views 1 and Views 2 are completely different pieces of software. It may seem on the surface that the issues are related, but they are not. All you're doing is polluting an older issue and at the same time, irritating the very people you're asking to help you.

I still believe that if someone doesn't understand the rules the same way you do, it's not a proper reason for being rude.
And being a good developer is also not a proper justification for a lack of politeness.
This is my personal view, of course. You may not agree.

Now I'll open a new thread for my problem, because you think that it's inappropriate to discuss it here...

This issue queue sees as many as 50-100 new issue messages per day. And we're volunteers; we don't get paid for this stuff. Sometimes our answers get written very quickly, especially when it feels like people expect us to do all the work, or when it's the same answer written for what feels like the hundredth time.

So yes, we get short with people. It's a cost of doing business in open source.

Also I would like to add, closed issue != closed thread. There are valid reasons to re-open old issues. The software doesn't automatically close the thread when it marks the issue closed. The Status: line on the issue is very important because it is one of the key fields that affects how we do work on these issues.

I am in fact going to close comments on this thread now.