Answered Evo 1.0.15 KCFinder Problem

Hi,

I am currently developing a website using the latest MODX Evo 1.0.15.

One issue that is being encountered is when trying to upload using the KCFinder.

As can be seen from: http://snag.gy/bfqc5.jpg there are a couple of missing scripts which try to load when uploading an image. Result is that no images can be uploaded.

Checked the FTP and the files are indeed not there. But also checked the downloaded zipped file from the modx.com and they are not in it neither.

Did someone encounter same issue and solve?

Thanks

Did you check if the files were located on github and perhaps missed in the zip?

Yes, it was included in the zip file on Github in fact. Re-uploaded the whole manager folder from it.

I still got an error though when uploading, and noted the following from Developer Tools (loaded after uploading an image):

http://domain.com/manager/media/browser/mcpuk/browse.php?type=images&lng=en&act=upload - gives a 404 Error (Not Found)
http://domain.com/manager/media/browser/mcpuk/browse.php?type=images&lng=en&act=chDir - gives a 200 (Post OK)

The only difference between the two are the query strings. Do you know how this can be solved?

I came on here to see if anyone else was having trouble too. After seeing there wasn't any solutions posted and a bit of debugging, in my case it turned out the newer method seemed to be triggering a ModSecurity rule that it wasn't prior to upgrading to 1.0.15. The only thing that changed with this site (that was known to be working before) was the Evo upgrade.

If you haven't already maybe that's something you could check.

Hi dustinwalker, thanks for the hint

Could you please give me an indication which ModSecurity Rule I should switch off or add an exception?

I'm using WHM (with CPanel) as a Server Management Software.

To be honest, I'm not sure. This was also WHM/cPanel. Once I saw my IP address in the modSecurity log, I whitelisted the directory to disable it completely to see if it fixed the issue which it did. I then put out a ticket with the host and after a few messages back and forth they were able to adjust it so it worked. I am not entirely sure what rule the adjusted or what they whitelisted.

This problem might be affecting me.

The site is on Rackspace Cloud Sites. How do I find out if ModSecurity Rules are running on this environment?

You should check with Rackspace, and/or the person who manages your server.

Quote from: sparkyhd at Nov 27, 2014, 10:42 AM

This problem might be affecting me.

The site is on Rackspace Cloud Sites. How do I find out if ModSecurity Rules are running on this environment?

Create a script with phpinfo(). Access it and check: apache2handler > Loaded Modules. You should see something similar to: http://gyazo.com/bcba303469f23671f7213e1478788cbd.png