Custom fields not showing up in Views fields

I can't duplicate this problem. Using the versions you've mentioned, custom fields show up just fine in the 'Content' group.

p.s. it would be very useful, if the threads had the number of responses displayed (on the issues page)
you only can find out the time of the last response, but not how many responses a thread has :(

Sorry, I don't have any control over the issue queue software.

Hi there,

I've defined a new content type by writing a module (so I did not use CCK, though it is installed). The new content type has about 20 additional fields which also do not show up when creating a new view. I may only select standard fields like title and body.

Is there any way to let views module know about these additional fields and let me use them in a view?

sin

---------
version info:
Drupal 6.13
Views 6.x-2.6
CCK 6.x-2.4 (though not being used by this specific content type)

No update for more than 30 days.

@WatermelonMan

Did you ever figure this out? I'm experiencing the exact same issue right now and this seems to be the only non-duplicate thread I can find that deals with this issue for 6.x.

I'm using the same versions of CCK and Views that you listed above. I am not able to access the fields of my custom content via the "fields" tab in the views module. I have tried disabling/re-enabling and uninstalling/re-installing both CCK and Views, deleting my existing views each time and clearing the cache, but I am still seeing the same issue. Please let me know if you have come to a resolution on this issue, as I'm sure you can empathize with my frustration at the moment.

If you're really using versions that old, I'm not even going to address this. There's at least 8 releases since that version and a similar number in CCK.

using current versions
same issue here

Same issues . Current versions of CCK and Views using OpenPublish. I add the CCK fields but they don't show up in the views UI. The data is being stored in the DB properly and I have cleared the cache for the site the server and views with no luck.

Any help is appreciated

I had the same issue. Cleared the views cache in the tools section and that did the trick.

Greetings,
D

I finally had to disable views cache in the views>>tools section in order for the fields to show up. I tried turning views cache back on when I was done developing and it broke all my views using the custom fields so I had to leave views caching off(which is not my favorite thing).

-Trevor

Same here! Just flushing the cache does nothing, it only works when I disable views caching.

Greetings,
D

Are you really sure? What happens if you enable the cache again? Does it work?

No it doesn't. When I enable it back Views no longer finds the fields and reports them as broken/missing.

What if you clear all caches and the views caches on admin/build/views/tools?

Tried it and it stays exactly the same. No difference what so ever.

Same issue here. I've flushed all cahes & the views cache. Custom content types only show up when views cache is disabled. Anybody find a better solution?

If any of you are running a VPS like Linode, try rebooting it. I just did that and everything shows up now.

I am running into this problem today - clearing caches seems to have fixed it for me. So strange... someone mentioned none of their information was showing on the public website, and when I checked the view, I noticed a bunch of 'broken/missing handlers', and couldn't see any 'Content' fields in my View. I cleared the cache, and they thankfully reappeared.

I again hit this problem after upgrading to the latest filefield and views releases today - today, my filefield module automatically disabled itself. On another site I upgraded, views automatically disabled itself. Both times after running update.php. So strange.

[Edit: I've had this happen before with other upgrades—always views, imagefield, or filefield (and sometimes two or three!). I have no clue why this is happening, but it is, across at least five different sites in three different hosting environments.]

There is nothing in Views code that could possibly cause it to disable itself. I really don't know what's causing this. I suspect some contrib module gone wild. :/

Closing from a lack of activity.

Fixed.

I found, ultimately, that the problem had to do with memcache; something in memcache was stale, and it took a manual cache_clear_all() on the drupal front-end to get all the views updated so they'd show field data again.

Thank you for the update.

I can't get views UI to display some cck content fields within Fields. Both filefields and text fields will not show up. If I disable the views data caching within Tools as mentioned by somebody else the fields become available for selection but as soon as I re-enable the caching the fields revert back to being unavailable.

Any suggestions on how to fix this?

I'm having the same problem with Drupal 7.24 and Views 7.x-3.7. Like above if I disable views' caching I can see all of my fields, but when I turn it on again they disappear. I have cleared my cache, my views cache and reset my Linode several times to no avail.

Any suggestions would be appreciated.

I was also having this issue: drupal core 7.24, views 3.7. Interestingly everything worked just fine on production servers (linux-debian) - I was having problems (custom fields would not show up in views -> add field) only on my local machine (running mac os x).

Most likely the issue is machine/system-related - that is why it is hard to be reproduced.

I've had to roll back to Views 3.5 - and it solved the problem (views work on okay both environments).