I have created 2 fields (title and body) bundled with a field collection for a content type. I added several records and later when thinking to add again more records, realised I can't add any more. The ajax seems loading infinitely. There are some errors captured with the browser developer tools in Chrome and firefox. Wondering is this related to IMCE? How to solve this?

The following message was captured in the recent log messages:

Location:
http://mydomain.com/system/ajax

Message:
Notice: Undefined index: form_build_id in ajax_get_form() (line 320 of /myDomainPath.../public_html/includes/ajax.inc).

Files: 
CommentFileSizeAuthor
#3 imce#2067641.patch1.85 KBoushen
issue.jpg230.24 KBsimone960

Comments

simone960’s picture

Issue summary:View changes

typo

ufku’s picture

That page should not include the imce script. Find the module doing that and disable it.

ufku’s picture

Issue summary:View changes

extra info

dahousecat’s picture

I have the same problem that occurs after an ajax event I attached to the title field of a node edit form is fired.
The IMCE script should be on this page.
Any ideas?

oushen’s picture

Issue summary:View changes
Status:Active» Needs review
StatusFileSize
new1.85 KB

This happens because imce attach global error handler to jQuery.ajax()

boshtian’s picture

I got the same error. I tried disabling modules and the error went away when I disabled Clientside Validation.

So obviously there is some compatibility issue. I am yet to discover this in details, but maybe someone will get some clue when reading this.

I've also tried with the patch above, but it didn't solve my problem.

blueblot’s picture

also tried patch with no luck

TechnicalDWM’s picture

We suddenly have this exact same error. We have an block with an field collection. As soon as we click on "Add another item" we also get this Type Error. As soon as I remove the html formatted field from the collection, it doesn't give this error, as the html field uses wysiwyg editor that uses imce. Any suggestions we can try?

aaronbauman’s picture

I don't really understand what patch #3 is doing, but it worked to eliminate the error for me.