Hi all,
I'm using CCK 6.x-2.5, FlexiField alpha5, FileField 6.x-3.1, Drupal 6.13.

I have a node type with a FlexiField that contains two fields: (1) an image file field and (2) accompanying caption text field. It is set to unlimited values, allowing users to add a number of image/caption pairings to a given node, and it is not a required field. Other fields in the node type (but not in the FlexiField) are a Date Range field, and a couple of text fields.

I'm experiencing two types of odd behavior:

  1. When users create a new node of this type and enter their data *without* adding an image/caption pair (as it's not a required field), and hit Save, only the title of the node is saved -- all other data (date information, text fields, etc) is gone. If they then edit this node again, adding the missing information (but still not using the FlexiField) and hit Save, everything is as it should be -- no information is lost.
  2. When users create a new node of this type and enter their data *including* adding an image/caption pair or two, none of the other data is lost upon saving. *However*, when that node is edited, the image/caption pair disappears, and needs to be re-entered. Once it is re-entered, it sticks around without any more issues.

So with both issues, it's only in the initial creation of a node that these issues arise. Through disabling various fields and modules, I've been able to link the behaviour to FlexiField, but I haven't the slightest as to *why* it's happening. I'm hoping someone out there may have some insight -- thanks in advance!!

Comments

I'm experiencing the same issue regardless of the caption field. My flexifield contains one select list, one text field, and one image field. On initial save all data is lost. If I then edit the node, re-enter the data, and save, all is well.

Also, I can't configure my flexifield once I've created it. On the manage fields page, if I select configure for my flexifield, I receive the following:

Fatal error: Cannot unset string offsets in /usr/home/.../sites/all/modules/cck/includes/content.node_form.inc on line 60

Same here.

- I have a flexifield containing a filefield, a text field and an integer field.
- Upon creation, if my CCK content type uses this flexifield, all CCK field values (both from the flexifield fields and from the actual content type) are lost on initial save. This makes default values useless, which in my case is critical. Taxonomy, path, title, etc. are, however, saved.
- I narrowed it down to the filefield being the culprit. If I remove it from the flexifield, everything works correctly. From reading the posts above, I guess things point to that direction.

I would really appreciate it if somebody could shed some light on this issue. The usage of default values and being able to save data upon creation is critical to me.

Drupal 6.14
CCK 6.x-2.5
Filefield 6.x-3.2
Flexifield 6.x-1.0-alpha5

I'm also experiencing what bluewrath is describing with same core/module versions

Category:support» bug
Priority:Normal» Critical

Changing category from "support request" to "bug report" and Priority from "normal" to "critical" (fits better to Priority level of Issues specifications). It renders initial input, including default values, useless.

I'm also experiencing what bluewrath is describing (#2).

It really seems to be the file-field which is disrupting the flexi-field.
After removing the file-field, nodes which originally where not showing the data entered on node creation, are "repaired" again.

so probably we should concentrate our efforts on the influence of file-field on flexi-field. Unfortunately I can't code php. Would be cool if someone can help us on this!

any ideas?

I am experiencing the exact same issue. Here's to hoping another voice will push this issue up in priority.

Hi, no solution on flexi-field, but instead, I started to use the multigroup-fieldset available in cck 6.x-3.x-dev. Cool Stuff! http://drupal.org/node/484068

Version:6.x-1.0-alpha5» 6.x-1.x-dev
Status:Active» Fixed

I committed a fix to CVS.

Status:Fixed» Needs work

I downloaded 6.x-1.0-alpha5.
But it still does not work.
If I create a node and attach an image (file-field inside a flexifiled) it won't save.
Same issue exaclty as the original post.

Status:Needs work» Fixed

Hi yanku. Fixes always go into the dev version, so 6.x-1.x-dev. I may release alpha6 at some point, which will then contain all fixes since alpha5, but past releases are locked.

The second issue identified in #1 still exists and is rather problematic. I'm using the most recent dev version.

Fatal error: Cannot unset string offsets in /usr/home/.../sites/all/modules/cck/includes/content.node_form.inc on line 60

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Was this fixed? I have the latest dev and I'm still getting the error.

In the file flexifield.module , line 181 in case 'insert': only need to insert a break;

Status:Closed (fixed)» Active

Hello,

i have same issue too, i couldnt find any solution or fixes. What should i do?

Thanks,

#15 works. Items are saved.

flexifield.module , line 181 (insert break:)

    // Storage operations that simply cascade to the child fields.
    case 'insert':
    break;
    case 'delete':
    case 'delete revision':
      flexifield_items_invoke($sOperation, $aItems, $oNode);
    break;

but I noticed that the item_id is empty on initial save. (check with devel)
Is this normal?

Any news here?
Is this fix tested?
Committed to Git?

This is really important, thanks all.

Thanks
Issue resolved

Issue tags:+services, +D6

I am still facing the error as shown in #1. I had a discussion here about my problem . Please have a look as my problem is directly related to this issue queue.

@Vijayan.nat how was it resolved by you ?

I had the same issue myself. I thought I would post as this is what I found. What I did was download schema then compare the tables. The first issue I found was that the table structure was missing three columns. I dropped the table and tried to manually create the table. That came back with an error. There is a limit in mysql to how much data is in one table. So I had to limit the length of many of the fields. I don't know why I never got the error building this through the interface but that was the case for me at least.

So I built the table and everything saves now.

confirming #15/#17 works.