cancel
Showing results for 
Search instead for 
Did you mean: 

Document editing/upload failures in 4.0d

pj_neil
Champ in-the-making
Champ in-the-making
Hi all,

Some of the documents I have report failures on upload using the flash uploader in Share. There is a known issue with Flash and the workaround is supposed to be to use the Explorer interface to upload . The problem is that the documents that fail to upload in Share also fail to upload in Explorer - at least in Share the Flash tool reports a failure; in Explorer the browser tab just hangs. It's not just up-versioning, but metadata also fails to update (such as amending the document title using the interface) and the documents won't checkout. It doesn't affect all documents, but the list is growing. The documents don't appear to be corrupted as they can be downloaded and viewed.

I'm using Alfresco community 4.0d for document management. Installation environment is Windows with bog standard PostgreSQL DB. For the client I'm primarily using Chrome (but also occasionally Firefox and IE9 (both 64 and 32 bit)). I've disabled the document previewer as I had some large Word docs (not my fault!) that were crashing the OOo service, but this has not changed the issue described.

I have looked at the log files' timestamps (and contents) when these documents are updated and there is no change… so there's no log to upload here.

Is there a database repair I can attempt?… or any other suggestions?

Any pointers would be appreciated,

thanks, Neil
2 REPLIES 2

digihorse
Champ in-the-making
Champ in-the-making
Your biggest problem is Chrome. I've found that the Chrome implementation of HTML5/Javascript breaks features in Alfresco (and others to be fair).  THe upload is one of the biggies that doesn't work as expected.  You should be able to go in, via Firefox on the Explorer side and find and "fix" the problem.

pj_neil
Champ in-the-making
Champ in-the-making
Hi,

thanks for your response. I'll use FF exclusively with Alfresco Share/Explorer and monitor for the next week.

Thanks once again, Neil