When loading the applet I get the following error message:

10:36:34.691 [ERROR] java.lang.NullPointerException: null (Unable to access to the postURL: 'http://www.ho.st/cms6/jifupload/fotoalbum/field_foto/0?PHPSESSID=7eededb...')

I have created a CCK content Type FotoAlbum containing an imagefield and have selected this field in the jifupload setup. I have also granted all users access to 'access jifupload' and the user I using to add the content also has the 'administer jifupload' rights.

I am running Drupal 6 in a subdirectory /cms6 within the public_html folder.

Any Ideas what the problem could be?

Thanks for your help,
Phoenix77

CommentFileSizeAuthor
#8 1.jpg30.29 KBsalateenoo
#8 2.jpg86.45 KBsalateenoo

Comments

awolfey’s picture

awolfey commented

Hi, sorry about the error.

1. Can you tell me more about the server you're using so I can investigate?

2. Make sure your php.ini or .htaccess does not have a line like this: php_flag session.use_trans_sid off

3. Try to load the uploader again. View html source. Look for a line like postURL: "'http://www.ho.st/cms6/jifupload/fotoalbum/field_foto/0?PHPSESSID=7eededb...'". copy that to your browser address bar and see if it works. If not, remove the ? and everything after than and see if it works.

4. Also, try this on an existing node and see if if works. Your users must be able to create this content type fotoalbum to use the uploader.

Let me know what you find out.

Aaron

Phoenix77’s picture

Phoenix77 commented

Checking phpinfo from my provider if find session.use_trans_sid = 0.

It is set through the settings.php of Drupal 6, so I changed the value to 1 and it now works.

But googling the parameter gave my this:

PHP will add a unique PHPSESSID query pair to URIs within your site if cookies are not available and session.use_trans_sid is set. While this helps people who do not accept cookies, search engines will rank your site low.

So will changing that value screw-up my search ranking?

Phoenix

awolfey’s picture

awolfey commented

I don't believe so. Regarding this module, the only reason the sessid is needed is so that the applet has the same access as the user. The post url with the query is never available to search bots, or anyone except your drupal install. Even if you let robots access your node/edit pages they won't see that because they are anonymous users.

I also don't believe this changes any drupal uri building, so I think you're fine.

My servers, shared and dedicated came with that php setting on.

Aaron

Phoenix77’s picture

Phoenix77 commented

Aaron,

thanks for your help :)

Much appreciated it works like a charm know.

Phoenix77

Phoenix77’s picture

Phoenix77 commented
Status: Active » Closed (fixed)
awolfey’s picture

awolfey commented
Status: Closed (fixed) » Active

Actually, this may not be necessary in the new version of the applet, which is supposed to use the browser cookie. I will look into it and report back here.

awolfey’s picture

awolfey commented

Phoenix77: If you get the new dev version of the module 5/10/2009 this should be fixed and you can change your session.use_trans_sid back to 0 or off.

Let me know your results, please.

Aaron

salateenoo’s picture

salateenoo commented
StatusFileSize
new 2.jpg86.45 KB
new 1.jpg30.29 KB

Phoenix77 :

i did what you made by changing the session.use_trans_sid to 1 instead of 0, but i still have the same problem . and if i try to click OK on the Alert message and start to upload the images , i receive this error:

wjhk.juplod2.exception.JUploadException: unexpected EOF (in header)

i attached to images for the two errors.

i running a WAMP server on windows XP.

any help please ?

awolfey’s picture

awolfey commented

Hi, please make sure you are using the latest dev version of the module.

THanks,

marrch_caat’s picture

marrch_caat commented

This problem can be fixed by upgrading to jUpload applet v. 4.5+ (4.6 recommended). The problem is probably caused by that earlier versions of jUpload were broken when HTTP request header contained empty strings. I'm not sure why they appear when jUpload is used inside of Drupal, but I've reproduced the bug (and one more bug as well) with the 4.3.2 applet version that's bundled with the module, and it was there on two Drupal installations when using three different browsers and two Java machines. Then I've upgraded to 4.6, and the problem was gone in all cases. So I'd advice you to change the applet version bundled with the module to the 4.6 version.

And thank you for the best mass upload module I've found!!! It's a pity to see it's not developed anymore :(