Blank admin/content/flashnode screen
spopovits - March 27, 2008 - 00:30
| Project: | Flash Node |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
Trying to use the admin import function. I have ftp'd the file to the file location and can see it for selection I get a confirmation request and after I confirm . The admin/content/flashnode screen goes blank and does nothing. The file is a video swf and is veiwable , I can click on it and open it and it looks fine. I have checked the db table and it never gets loaded. Can I insert any debug statements into the php file that would show me what progress the functions are making. I can import using the user function and it works fine, but fails on the larger files, which is why I need this to work. Could this be a php configuration problem, my host controls the php.ini and limits what I can do with the htaccess.
#1
It shouldn't be a config problem - if you are seeing the file for selection all that is supposed to happen is that the database gets updated!
Leave it with me and I'll test again locally to make sure I didn't accidentally break the import function recently!!
If you want to try debugging look in flashnode.import.inc you will need to add debug around flashnode_import_confirm_submit and flashnode_import_file as these are the "business" parts. The file is reasonably well commented so you should be able to work out where to put some lines if you want to try debugging too!
#2
I tried adding debug statements to show the form_status array fields and was unsuccessful, probably because I was guessing on how to make the values print on the screen. I will continue trying to see what values the form and node and file have at each step. thank you following up on my issue
#3
Sorry for not getting back sooner - did you get the import to work, or is it still an issue?
#4
Yes it is still an issue, just not a high priority on my list. I had memory issues with IMCE module that have a higher priority.
#5
Hi I had the same problem.
I did this:
1) upload a small file, i.e. ciao.swf (or the file you want) via FTP to your server;
2) Import this (with small files the module works well;
3) Edit the node created with the width and height of the bigger file you to show on your website, Save it;
4) Upload the bigger file CIAO2.swf via FTP ;
5) Delete ciao.swf;
6) Rename CIAO2 to ciao.swf
7) Insert the flash node into the page with the [ flashnode | nid=102 ]
Just to temporary solve the problem.
#6
Thank you, very good work around. I do appreciate the help
#7
I can't recreate this error on my local test system (using Drupal 6.2 and flash node 6.x-1.1)
Post #5 suggests that the problem is occurring with large files. I don't really know why that should be as the import routine simply adds the relevant file data to the table (at least, that's what it is supposed to do!). The whole point was that large files often can't be uploaded via HTTP. All the import does is scan the directories, suggest files for import, and the include the ones you pick. None of that should take any time since the file itself doesn't have to be read - only the directory system.
Can you let me know how large the files seem to be that are breaking the import? I have just tested with some small files, and an 8 Mb flv file, and they all came in with no trouble.
Thanks.
#8
Ah jeez just saw this post -
I tried #5 - it seems to work for me too... will use this until a fix (hopefully) arrives.
The files I am dealing with are 14MB - 63MB SWF
#9
I noticed that the work around only works if you don't plan on editing the node at all once you rename the large SWF to the name of the smaller successfully imported SWF. I forgot to change the title of one, and had to start the process all over again.
#10
Can you try switching on PHP error reporting, as described here, then try the import, and post what error messages are occurring.
The issue with large files when uploading via the node form might be due to a time-out, but I'm not sure what is wrong with the import, but a few people have now report this!
Thanks.