Teaser data is not saved in the teaser column in the node_revisions table when a blog entry is submitted in 5.3. I just upgraded a straightforward blog site from 4.7.6 to 5.3, and since then, no teaser data is saved when I either edit an existing blog entry or create a new one.

To recreate the error all I have to do is create a new blog entry or edit an existing entry that was previously displaying a teaser. After submission, everything else but the teaser is displayed for the node on the front page. Inspection of the node_revisions table reveals only a <p> tag in the teaser column for that node.

Comments

vm’s picture

vm commented
Component: blog.module » database system
vm’s picture

vm commented

when you updated did you goto 4.7.8 before hoping to 5.3 ?

wonder95’s picture

wonder95 commented

No, i just went straight to 5.3.

ellanylea’s picture

ellanylea commented

I'm encountering the same problem by upgrading from 5.2 to 5.3, when using a CCK type. Whether I create a new page of that type or edit, the teaser is gone.

gpk’s picture

gpk commented

May be the same issue as this http://drupal.org/node/155337. There is a patch for 5.x and 6.x-dev. Does this fix it?

@wonder95:
Could be caused by the max teaser length setting being lower than when you originally created the node(s). So that the first complete <p> element is now too long to be the teaser, and the teaser end is being calculated as the newline after <p>. If so, then the patch should do the trick.

drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Postponed (maintainer needs more info)

Can not reproduce. Please provide instructions for how to reproduce from a clean install. Maybe it is the fault of a contrib module?

gpk’s picture

gpk commented

I suspect this is caused by content such as:

&lt;p>
Here is a long paragraph that extends beyond the character count limit for teasers on the Post Settings page for this content type ... extend as long as necessary ... etc. etc. etc.
&lt;/p>

If the length of the first (and in this case only) p element exceeds the max teaser length, node_teaser() then looks for a newline to use as the teaser break point. It finds one after the opening p tag, before the content actually starts.

Often this problem arises when something like TinyMCE is used to create content, since this is how it lays out the HTML. Of course you get the same problem if you input the above content (with a sufficiently long paragraph) by hand.

The title of this post is perhaps slightly misleading - teaser data of a sort *is* being saved in node_revisions, but only the opening p tag itself (as returned by node_teaser()) (this is what the original post in this issue used to say but while the code.module problems following D5.6 update continue it's not readily visible!).

The patch here http://drupal.org/node/155337#comment-643187 fixes this problem - it's already in D6 and seems to work well. IMO it's well worth including in D5 since I believe many users of Drupal are affected e.g. a couple of recent ones http://drupal.org/node/205114 who sadly didn't elaborate ...

gpk’s picture

gpk commented
Status: Postponed (maintainer needs more info) » Active
drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Closed (duplicate)

Appears to be a duplicate of http://drupal.org/node/155337#comment-643187