Visualização combinada Visão plana Exibição em árvore
Tópicos [ Anterior | Próximo ]
toggle
Zsolt Balogh
Document library, file upload problem
15 de Setembro de 2009 04:18
Resposta

Zsolt Balogh

LIFERAY STAFF

Ranking: Expert

Mensagens: 463

Data de entrada: 23 de Março de 2009

Mensagens recentes

Hi,

It was really hard to find a bug in SO, but we've managed to find one emoticon

Our client thought if she uploads a document in a folder with the web uploader, it will overwrite the existing document. The problem is, that nothing happens when you have a file with the same name, the uploader tells you that everything was successful, but nothing happens.

I really don't know what should happen in this case, but an error message would be helpful, I think emoticon

I've created an issue for it: SOS-214
Bryan Cheung
RE: Document library, file upload problem
15 de Setembro de 2009 12:28
Resposta

Bryan Cheung

LIFERAY STAFF

Ranking: Expert

Mensagens: 363

Data de entrada: 26 de Agosto de 2004

Mensagens recentes

Thanks Zsolt, we'll take a look.
Vinod V Pisces
RE: Document library, file upload problem
4 de Maio de 2010 12:58
Resposta

Vinod V Pisces

Ranking: Junior Member

Mensagens: 31

Data de entrada: 29 de Setembro de 2009

Mensagens recentes

Zsolt Balogh:
Hi,

It was really hard to find a bug in SO, but we've managed to find one emoticon

Our client thought if she uploads a document in a folder with the web uploader, it will overwrite the existing document. The problem is, that nothing happens when you have a file with the same name, the uploader tells you that everything was successful, but nothing happens.

I really don't know what should happen in this case, but an error message would be helpful, I think emoticon

I've created an issue for it: SOS-214


This issue applies to the underlying Liferay portal too and not just for SO. In case it might be useful for everyone, check out the following issue in JIRA:http://issues.liferay.com/browse/LPS-8580.

It looks like it is not resolved even with 6.0; however there is a code-level fix recommended in the log. (I have not verified the solution yet)