Create an account

Very important

  • To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
  • You will only see chat messages from people who are at or below your level.
  • More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
  • Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)


Thread Rating:
  • 456 Vote(s) - 3.54 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Magento : CMS upload image fail silently

#1
I am trying to figure out why the tinyMCE WYSIWYG editor in the CMS module of Magento will not upload images. I can create/delete folders but any file will simply not get uploaded, and there seems to be no message as to why the file is not successfully written on the server.

Anyone may have an idea why?

### ** Update **

I'm using Magento 1.6.2. I have tried to track down the problem and it *seems* that the controller never gets executed. I have added a line to log the arguments in the `uploadAction()` action (in `Mage_Adminhtml_Cms_Wysiwyg_ImagesController`) and nothing gets logged.

This is project inherited from someone else, and was modified to some extend, but nothing seems to point out that this part of Magento would have been touched in anyway by the modifications.

### ** EDIT**

The project associated with this question has been dropped and I no longer can provide an answer to this question. If anyone can confirm a working answer (as this problem was apparantly common with Magento), I will gladly mark that answer as "accepted".

Otherwise, I will flag this question for removal for the aformentioned reasons.

Thank you.
Reply

#2
Are you using flash uploader with https? If so, is your secure address in differente domain (usually used in shareds ssl)?
I got some trouble with this. I solved by installing a flash uploader disabler plugin.

You can download the plugin with this downloader key:

>

[To see links please register here]


I hope it helps.
Reply

#3
There are some known issues with flash image uploader on Magento. Unfortunately when it falls, it falls silently. Here are some cases when smth can break it:
<ol>
<li>if you try to use it with secured connection using open ssl certificate</li>
<li>if you're using it on server with apache authentication</li>
<li>on some Magento versions with prototype 1.7</li>
</ol>
I think the latter is your best bet. Maybe you should try to apply the patch from here:

[To see links please register here]

Reply

#4
In my case it was a cross domain problem, and one quite hard to find if you ask me...

What was puzzling me was that the uploader for product images was working like a charm but the one in the CMS section was failing completely silently. We are serving the skin folder from an Amazon S3 bucket, and the flash uploader lives under that folder.

Interestingly enough, our version of Magento (1.7.0.2) is using two different methods to calculate the path to the SWF file, depending whether you are under CMS or Product update.

The CMS file (app/design/adminhtml/default/default/template/cms/browser/content/uploader.phtml) is using the following method to embed the Flash Uploader:

<?php echo $this->getSkinUrl('media/uploader.swf') ?>

While the Product image uploader is using:

<?php echo $this->getUploaderUrl('media/uploader.swf') ?>

In our case, the first one resolves to the AWS S3 url, obviously in a separate domain, while the second one will still reference the local domain's url.

So yeah, the quick, dirty fix would be to replace getSkinUrl for getUploaderUrl in app/design/adminhtml/default/default/template/cms/browser/content/uploader.phtml. Alternatively you can extend the core to load a different template in which you would have replaced that method.

I hope this helps somebody... I wish I had found something like this five days ago when I first stumbled upon the issue :-)
Reply

#5
Other than solutions provided here, it may occur when you use a CDN (_or a different domain_) for your javascript and media files in admin panel. If you use CDN, use it for your **website(s) scope** and use your own domain for **default scope**. It will make your website(s) media and javascript files to be loaded from CDN, and backend's media and javascript files to be loaded from your own domain. This will solve your problem.
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

©0Day  2016 - 2023 | All Rights Reserved.  Made with    for the community. Connected through