DNN 7.0.2. Using the html module, trying to upload an image, the upload dialog says "Max file size allowed: 200.KB" I need to be able to upload images bigger than 200.00 KB.

I have edited the HTML Editor Manager, in the Everyone Configuration and increased the Image Manager Settings, Max File Size to over 309248 bytes, which should be over 300KB and saved. Then I have cleared the cache, restarted the application pool and restarted the application. When returning to the html module and trying again to upload an image, the upload dialog still reports there is a "max file size allowed: 200.00 KB" it is unchanged and I cannot upload a file larger than that. Also, if I return to the HTML Editor Manager, i see that the Max File Size has returned to the default of 1024KB.

I have also increased the max file size settings in the web.config following Chris Hammond's video. The file manager now says I can upload 80MB.

What do I have to do to successfully allow larger uploads in the radEditor image manager in DNN7?

I was able to change these settings in DNN6. DNN7 seems to not be working for uploads for me.

Thanks, Mark Buelsing

I believe that I'm able to reproduce this. I don't have a solution at the moment.

Well, you should be able to use the File Manager to upload files. Then you have access to them in the editor.

Joe, thanks for the help. Sorry that you now have the same issue. Here is a follow up with a solution.

The changes to the HTML editor were not saved because of two different reasons. Both needed to be handled.

1. The Plesk control panel had mangled the folder permissions and denied my ability to save, silently.
2. There appears to be a glitch with the html editor manager that causes it to remove the settings for the max file size and max document size. I found a link here:

http://www.dotnetnuke.com/Resources...age/1.aspx

Which has the solution in it. The solution is to edit the configuration file for the rad editor manually and bypass the html editor manager. This solved my problem as well as a few others.

Thanks, Mark.

I was actually having trouble finding the config file. Now I know where to look!

From reading the release notes, it appears that this issue is fixed in 07.00.03 released the past week.

Upgrading has its benefits. (Usually) Thanks Joe!