possible bug report
| Project: | Content Construction Kit (CCK) |
| Version: | 6.x-2.0-rc4 |
| Component: | General |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
the cck seems to work fine except for two things.
1... when I goto /admin/content/node-type/fsbo-listing/fields
MANAGE FIELDS. all of the fields are there, but they are separated by
all of the fields have blank fields between them. The first blank section is 9 lines. then there are 5 lines between each cck field.
2... I think this may be related, so I thought I would post it:
when I setup a contemplate teaser and body type on this cck node type. I get an error:
While traversing node variables your recursion limit of 15 was hit 33 times
I am pretty certain that this is an error in the contemplate module, as I have played with the:
http://www.zzfsbo.com/admin/settings/contemplate
the contemplate settings, and I get a different kind of error with each change of setting.
I think that this error may be caused buy the issue I list in number 1.
but its still a potential bug.
the CCk is this version:
; $Id: content.info,v 1.6 2007/07/04 23:46:29 yched Exp $
name = Content
description = Allows administrators to define new content types.
package = CCK
core = 6.x
; Information added by drupal.org packaging script on 2008-07-10
version = "6.x-2.0-rc4"
core = "6.x"
project = "cck"
datestamp = "1215694805"
#1
Please update to CCK 6.x-2.x dev version and see if the problem about 'blank fields' persists.
#2
i did absolutely when I double checked to make certain of my version. but the problem fixed itself with this version:
; $Id: content.info,v 1.6 2007/07/04 23:46:29 yched Exp $
name = Content
description = Allows administrators to define new content types.
package = CCK
core = 6.x
; Information added by drupal.org packaging script on 2008-07-10
version = "6.x-2.0-rc4"
core = "6.x"
project = "cck"
datestamp = "1215694805"
don't know what to say other than I am on a really cheap shared host.
#3
OK, thks for reporting.
#4
Automatically closed -- issue fixed for two weeks with no activity.