I have a nodetype that has a CCK Filefield which is designed to work primarily with text documents. It functions normally without panels.

My goal is to enter either the FileField or the Group it exists in, into a panel page variant designed for that nodetype. When inserted as a Pane, the Filefield seems to appear correctly, with a "browse" and "upload" buttons.

Issue 1:(File Does Not Upload)
If you try to use the pane to upload a file, it browses correctly, but when you click the Upload button, the entire pane's content (except the title) just disappears. The file does not upload, nor display.

If you Edit the node, and use the same Filefield to upload a document, and Save the node, (panels doesn't control the node edit screen) it works fine. It also displays in the Pane correctly a link to the file with a "Remove" button.

Issue 2: (Remove button throws error)
The remove button doesn't work, but does throw a hugely long error sometimes, other times it just reverts to the behavior in Issue 1, only a pane title is visible. If you refresh it shows the file as still being there.

I'm wondering if this is a bug, or am I not following best practices with using FileField and Panels? Any suggestions on how the CCK FileField should be set to display, and/or the Pane that is meant to display it?

Thanks

Current Settings:
Both the CCK field itself and the Pane are set to work with Ajax, on a pure Zen theme. I am using the Ajax and jquery modules as well as a a few dozen others, mostly the top 50 standards modules.

Comments

merlinofchaos’s picture

Status: Active » Postponed (maintainer needs more info)

Did you ever find out any more information on this? This probably should've been filed against filefield but I'm not sure they have any real knowledge of how the Panels integration works over there, and it's not something I've ever tried.

martinyde’s picture

Version: 6.x-3.2 » 7.x-3.0-alpha3

I'm experiencing the same upload issue using drupal 7.4 and the latest panels out of dev.

The error message I get is:

An unrecoverable error occurred. The uploaded file likely exceeded the maximum file size (100 MB) that this server supports.

Attempting to upload an empty .txt file.

Letharion’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

In an effort to clean up the many hundreds of open issues in the Panels queue, I'm going over all issues with the "Postponed, needs info" status.
As per the Panels Issue guidelines, http://drupal.org/node/573062 section 2.2, I'm closing all issues that haven't been updated during the last month.
I realise that some issues will be closed, that should remain open. In these cases, most of the time, they have simply been left in the "Postponed, needs info" state by mistake.
If this is the case, and you still have an interest in this issue, please just re-open it, setting the appropriate status.

8ballsteve’s picture

Version: 7.x-3.0-alpha3 » 7.x-3.3
Status: Closed (cannot reproduce) » Active

I am still experiencing the exact same issue as StratisFear with the latest D7 release (7.15) and Panels 3.3

Any theories on what may be the cause of this - am confused as to why image widgets seems to function fine in a panel pane whilst the file widget produces the following message when clicking the upload button:

"An unrecoverable error occurred. The uploaded file likely exceeded the maximum file size..."

Any help would be greatly appreciated!

sime’s picture

If this is the same problem that I have, it also applies to image fields. $_POST['form_build_id'] is not set in file_ajax_upload(), which triggers the error. The error does not occur when you turn off Javascript.

But. I have two panels - it happens for one panel and not the other. Still nutting it out.

sime’s picture

Oh that was interesting. The panel was missing the submit button. Adding the submit button made the form functional. I wonder if it was ever functional. Anyway, maybe that was op's problem too.

sime’s picture

No it didn't... it adds an additional form button, which seems to cause the problem to go away. A form button was in fact already there, but file upload button appears submits the wrong form build ID of the nested forms. Something is really wrong here, but it's deep in the rendering logic and it does my head in.