I created my own class deriving from FileStorage and it works fine. I am able to upload files, create folders, etc The only problem is that I can't rename files. My understanding is that I should simply be able to override the RenameFile method which I have done. Notice that I even placed a break point but it never gets called.

When a user tries to rename a file, my overridden RenameFile method does not get called and instead the following error is displayed:

PLEASE NOTE: the user gets this error message no matter what he types. For example "aaa" gets rejected. Therefore the problem is not related to the user typing spaces or special characters.

 

I found a few other people who had the same problem and asked the samequestion here and here but their question was never answered.

We are investigating this issue and will get back to you as soon as possible.

Hi,

 

Did you ever change the

 

CuteSoft_Client\CuteEditor\Configuration\Security\Default.config ?

 

the code should contains <security name="filenamePattern">^[a-zA-Z0-9\._\s-\#]+$</security>

 

When you get the "File name not allowed" , the reason is the typed name is not match for the filenamePattern

 

Regards,
Terry

I did not modify the Defualt.config file at all. The filenamePattern is indeed the following:

Any update?

Any update?

Any update?

Any update?

frJericho,

Terry already asked me this question two months ago and I said this value was never modified. Here's a copy of the Default.Config: /forum_uploads2/Default.config.txt

 

There are 3 configuration files in cuteeditor installation,

 

CuteSoft_Client\CuteEditor\Configuration\Security\Admin.config

CuteSoft_Client\CuteEditor\Configuration\Security\Default.config

CuteSoft_Client\CuteEditor\Configuration\Security\Guest.config

 

Please do the following test:

1. Modify "filenamePattern", restore it to the default value in all of these 3 files. Does it work fine?

2. If you remove the following line, does it work fine?

<security name="filenamePattern">^[a-zA-Z0-9\._\s-\#]+$</security>

3. When you upload one file every time, test it several times with different file, does every file have this issue or only some specific file have this issue?

 

Regards,

Eric

1. As I said before, this value was NOT customized. Therfore there isn;t anything for me to "restore to the default value".

2. I removed the line from all three config files as you suggested and I observe the exact same problem.

3. Every single file has this problem

 

Is there any way to unobfuscate the JavaScript code so I can help you pinpoint the problem?

Unobfuscated javascript code is only available for source code license user. You can extract your code to one runnable project which can reproduce this issue and send it to [email protected], we will investigate this issue on our end.

 

Regards,

Eric