Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

DataObjectManager Module /

Discuss the DataObjectManager module, and the related ImageGallery module.

Moderators: martimiz, UncleCheese, Sean, Ed, biapar, Willr, Ingo, swaiba

SOLVED: Uploadify file upload popup not working


Go to End


8 Posts   15663 Views

Avatar
BartM

Community Member, 9 Posts

6 May 2011 at 1:49am

Hello all,

First off, the DataObjectManager and Uploadify modules look great. They are exactly what I needed to provide convenient image-upload functionality to my site. Unfortunately I'm having some trouble getting it all to work.

I am trying to allow a content manager to add several images to a page, which will then be shown as a slide show in the header. Installing the required plugins was no trouble, and writing the code to add the image upload manager to the CMS page wasn't too hard. However, when I click the 'Add Image' button the file upload popup that appears doesn't function. A screenshot can be found here.

I can click the 'choose file' button and select a file, but when I click OK, nothing seems to happen. I have checked the file system, and the image was not uploaded.

I have no idea what the problem could be. I don't think it's in my code, since the field seems configured properly, otherwise I wouldn't be able to try and upload an image, would I? I also read about uploadify liking to have the latest version of Flash, which I am using.

Any hints or suggestions would be most welcome.

Sincerely,
Bart

Avatar
UncleCheese

Forum Moderator, 4102 Posts

6 May 2011 at 1:23pm

None of the JavaScript is loading. Check for errors.

Avatar
BartM

Community Member, 9 Posts

6 May 2011 at 8:31pm

The Chrome console shows the following errors:

GET http://localhost:92/SVN/Customers/True/sapphire/thirdparty/tinymce-advcode/langs/nl.js?m=1245029368 404 (Not Found)
GET http://localhost:92/SVN/Customers/True/cms/javascript/tinymce_ssbuttons/langs/nl.js?m=1245029368 404 (Not Found)
Refused to set unsafe header "Connection"

As far a I can tell they are unrelated to the uploadify pop-up. (Which doesn't mean we're not trying to track them down and eliminate them.) Using the developer tools I tried seeing which javascript files the pop-up loads, and as far as I can tell all files are present in the file system.

There must be something silly that I'm missing.

Avatar
Quadra

Community Member, 16 Posts

17 May 2011 at 9:30pm

Bart,

Long shot but what is the case of the folder containing the Uploadify code? I had an issue that presented in the same way and it was because I had the folder called Uploadify which works fine on my development machine (a mac) but broke on the live server (Linux). By changing the case of the folder name to lower (uploadify) it started to work right away.

Might not be your issue, but worth a try.

Cheers
Jason

Avatar
BartM

Community Member, 9 Posts

17 May 2011 at 11:43pm

Well what do you know, that actually solved my issue. Although my folder was entirely lowercase, it did have some relatively odd characters in it. (It was called 'modules-uploadify-r534'.) Seems Silverstripe is particular about its filenames.

Many thanks for your help, our customers will be grateful now that they can upload all the images they want. :)

Sincerely,
Bart

Avatar
Quadra

Community Member, 16 Posts

17 May 2011 at 11:46pm

Glad to help Bart,

As well as case you need to watch out for hard coded module names. Something to remember.

Cheers
Jason

Avatar
moonchild100

Community Member, 18 Posts

20 May 2011 at 7:19am

I had the same problem, but changing the folder's name doesn't help me :( Any ideas that the js files are not loading?

Thanks

Avatar
moonchild100

Community Member, 18 Posts

20 May 2011 at 7:43am

Edited: 20/05/2011 7:44am

I figured out it does caused by the folder's name, not "upoadify" but the name for DOM module. Just as reference for others, the folder name should be "dataobject_manager"

If the name of folder has been mentioned in the documentation that would be great....