Active
Project:
Flexifield
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
12 Nov 2009 at 00:33 UTC
Updated:
16 May 2024 at 00:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
markus_petrux commentedSearching for "javascript add another item" reports a few issues that may be related to your problem.
If none of those issues match, then we need a recipe to reproduce the problem. Do you see errors in Drupal logs? Apache logs? Javascript? Could it be caused by another module that breaks the autocomplete?
Comment #2
Anonymous (not verified) commentedI've discovered that the problem only occurs for fields within a flexifield, specifically autocomplete node reference fields in a flexifield.
Also, the problem seems to have changed: Javascript keeps working after the 'Add another item' button is clicked, but any previously entered values are replaced with a single space...
Moving to the FlexiField issue queue.
Comment #3
Anonymous (not verified) commentedChanging title...
Comment #4
Anonymous (not verified) commentedOk, it seems this bug is limited to autocomplete fields - multivalued textfields work fine...
Comment #5
Anonymous (not verified) commentedLooking at the code, it seems the problem lies somewhere just before
$aBuiltForm = form_builder($_POST['form_id'], $aFormCopy, $aFormState);on line 275 of flexifield-widget.inc...The #value of the fields in $aBuiltForm are not the same as what was entered before the form was re-built.
Not sure where exactly the problem lies or how to fix it...
Comment #6
effulgentsia commentedI'm not replicating the bug in my development environment. I sent BWPanda an email asking for more details, and will set the issue back to active when I can replicate the bug.
Comment #7
Anonymous (not verified) commentedThanks for the email effulgentsia! I may as well reply here, for the benefit of everyone else...
My dev site (where the problem occurs):
Drupal 6.14
AHAH Response 6.x-1.1
CCK 6.x-2.6
Flexifield 6.x-1.0-alpha5 & 6.x-1.x-dev (tried both)
Exports of my content types attached.
'Multivalued Fields' is the FlexiField content type, while 'Story' has the FlexiField field in it.
Creating a Multivalued Fields node works fine - the autocomplete fields don't muck up at all. It's only when creating a Story node that the problem occurs, and then only for the autocomplete fields.
The Node Reference field in Story that isn't part of the FlexiField works fine if that's the first thing you add, but if you start entering values in the FlexiField then try to use the other Node Reference field, it starts mucking up too...
Hope that helps!
Comment #8
Anonymous (not verified) commentedOops, forgot to attach exports, sorry :)
Comment #9
effulgentsia commentedThanks. The attachments helped. This bug uncovered a bug in the ahah_response module. Please try again with version 1.2 of that module.
Comment #10
Anonymous (not verified) commentedDoesn't seem to have worked... Tried again on the story node, but same problem.
Also tried setting up the multivalued fields in the page content type, but again, same problem.
Comment #11
Anonymous (not verified) commentedHow's it going, any progress?
Comment #12
effulgentsia commentedPlease try again with latest dev of flexifield (get from CVS or wait until dev snapshot has later timestamp than this comment).
Comment #13
Anonymous (not verified) commentedThat seems to have done the trick - autocomplete fields in FlexiField working now!
Thanks a bunch effulgentsia!
Comment #15
amclin commentedI seem to be seeing the same issue. If I have any Text Fields with "autocomplete for existing field data" widget as part of a FlexiField, then the add another button doesn't work, and when saving a content item, the FlexiField data is not stored. I'm using the Nov 28 timestamp.