I'm using Drupal 4.7 beta 5 and latest version of CCK grabbed directly from CVS. If I enable CCK in the modules admin page and then I visit my blog, teasers for blog entries stop showing up (i.e: you can only see title, submitted by, categories and read more link, but no actual entry). Accessing the node individually and also according to the devel module shows that the teasers are all still there and indeed if I disable CCK teasers show up correctly again.

I tried changing themes to see if it was a theme-specific bug, but teasers don't show up in any theme (I tried bluemarine, pushbutton, friendselectric and spreadfirefox) so I'm guessing it's not a theme-related bug.

I made this a separate bug report since this affects nodes generated by blog module rather than by CCK itself, but I wonder if this is somewhat related to this bug?

Comments

Permanently Undecided’s picture

Permanently Undecided commented

I just noticed that this happens to book pages as well, which led me to believe the bug had something to do with the fact that under administer -> content -> content types -> fields, there is a field called field_body, and it's defined for: book page, personal blog entry, story.
I thought that this field_body was to blame for the disappearance of teasers with blog entries and book pages, but the third content type, story, instead behaves normally. I do not know what to think.

jonbob’s picture

jonbob commented
Component: Code » content.module
Priority: Normal » Critical
Permanently Undecided’s picture

Permanently Undecided commented

I tested the just-updated files from CCK, but the problem persists.

Permanently Undecided’s picture

Permanently Undecided commented

Updating to Drupal beta 4.7.6 does not solve this problem.

Permanently Undecided’s picture

Permanently Undecided commented

I've just found out that this doesn't happen with fresh installations, where the teasers show up fine.

However, if you have a working site and then enable CCK this still happens.

karens’s picture

karens commented

This is related to http://drupal.org/node/51091.

I have an idea what is causing the failure of teasers on blog and book. Both of those modules are evaluated before cck (modules are evaluated alphabetically). No has reported any problem with teasers from modules that come later in the alphabet than cck. The handling of teasers in cck is not yet working correctly, and I think the current code has the effect of wiping out any teasers already created by blog or book. I think that fixing cck's handling of teasers will fix the problems with both book and blog's teasers.

karens’s picture

karens commented

Ignore the last post. Further digging indicated that teasers do look like they working right in the latest version, so I doubt this is the issue.

Permanently Undecided’s picture

Permanently Undecided commented

Further digging indicated that teasers do look like they working right in the latest version

They are? But how? CCK has not been updated in the meanwhile. Or are you telling me I'm the only one experiencing this issue?

karens’s picture

karens commented

I was not trying to say that something had changed in cck, just that I have figured out that they worked ok.

My original confusion was that there is no value saved in the database for cck node body and teaser, but after digging around in the code I see that it is designed to create them at runtime, so that is by design, not a bug. I don't know if that is a good thing or bad thing -- it takes more work at runtime, but means that you can change the layout at any point and have it apply to all cck nodes. Anyway, I can see the teasers just fine on any page where they ought to be showing up.

As to book and blog. I don't have book enabled, so can't speak to that, but I just tested blog on my setup and blog teasers also work fine for me.

My original post was thinking that if there is a pattern that nodes lower in the alphabet are the only ones affected, it might be something done by cck that is erasing their value, since modules are called in alphabetical order. Then I realized the problem wasn't affecting me, so I was wrong in my assessment of your problem.

I am running the latest cvs version of everything.

Permanently Undecided’s picture

Permanently Undecided commented
Status: Active » Closed (fixed)

Thanks Karen for your reply; it made me realize things worked fine for other people, so I suppose something must have gone wrong at some point with my particular installation: thus I'm changing this issue's status to closed.

My reason for not changing it to 'fixed' is that I followed all upgrading procedures correctly, am running latest CVS of everything, and again, disabling CCK made my installation work smoothly again, so I'm not totally convinced it cannot happen to somebody else. In case it does, feel free to reopen this.

This said, here's how I managed to work around my problem: I took a fresh installation of Drupal (which, as I pointed out above, does not suffer of this problem) and then gradually moved over database tables from one installation to the other. The moment I tried replacing the fresh installation's system table, blog and book module broke down again. This is as far as I could narrow down the issue, but it makes no sense at all to me, especially since I didn't have flexinode installed. Needless to say, it was a minor nightmare, so I really hope this doesn't happen to somebody else too.