After upgrading Reptag to 5.x-1.5 and CCK to 5.x-1.x-dev I noticed that I Reptag is no longer parsing CCK custom fields. No tags are parsed whatsoever. I also use Content Template to customise the layout of fields. However, after removing all input filters and disabling the content template module and reverting to the default display of a CCK content type, RepTag still does not parse any of the custom fields.

I have created a testcase content type with 2 fields. 1) a custom cck field & 2) a normal default body field. I can confirm that on viewing the page, the body field is parsed properly but the custom cck field is not. I suspect it is something to do with the recent changes to CCK where they have started introducing new display property functions for both individual fields and fieldgroups. I have kept all of those settings to their default values.

Will attach a debug output soon.

CommentFileSizeAuthor
#4 cck_latest_fields.patch5.23 KBprofix898
#2 cckdev_fields.patch631 bytesprofix898

Comments

profix898’s picture

I just tried with CCK 5.x-1.2 and reptag 5.x-1.5(-dev) and it works as expected.

I suspect it is something to do with the recent changes to CCK where they have started introducing new display property functions for both individual fields and fieldgroups.

Yes, I will try the latest development version of CCK to confirm your issue, but it will take a day ;)

profix898’s picture

Title: Reptag is not parsing CCK fields again » Make reptag compatible with latest CCK
Category: bug » task
Status: Active » Needs work
StatusFileSize
new631 bytes

Here is a very simple patch that makes reptag parsing latest CCK's fields properly. It works at least with simple textfields. I didnt have time to try multiple values or fieldgroups. After installing the patch, you must re-save the content type settings on reptag's admin pages.

However I will need to take a closer look at the cck changes to find a better way to retrieve the path to certain content fields ...

Fajan’s picture

The patch is only for a specific field. Unfortunately, all my fields are within fieldgroups so they aren't parsed. I realise that irregardless of how the output is rendered and whether fieldgroups are displayed or not in the output, the content array has all the fields within fieldgroup arrays. I hope you would be able to get a solution for this soon. Thanks.

profix898’s picture

Priority: Normal » Critical
Status: Needs work » Needs review
StatusFileSize
new5.23 KB

Here is a new patch which adds support for fields in fieldgroups. It should hopefully work with the latest cck now. Marking critical because the new cck release (1.4) also includes the changes to the fields structure. As before you must resave the content types settings on reptag's admin pages for the changes to take effect.

Fajan’s picture

Thanks profix I can confirm that this patch has solved the issue totally! Working like a charm.

profix898’s picture

Status: Needs review » Fixed

Committed to Drupal-5 branch. Thanks.

Anonymous’s picture

Status: Fixed » Closed (fixed)