after uploading one wordocument to dms bitfarm archive
enabled -coloured- / -high solution- the preview window
shows the coloured word document
in the following workflow we re-opened the word
document
open original file
with word from microsoft
then we make a simple change, for example some
addional text and save that in the prefilled
physical path, file is named automatically by bitfarm as
166171222437953.doc
After that we re-opened the word document again to check the changes.
Changes are very well done, but now the preview shows
a black and white coloured document!
The coloured preview is lost!
-
this is a very bad effect and to fix it indicated
a lot of worktime.
Has anybody a solution?
problem was after re-opening and change a wordocument
with the button -open original file-
it needs a lot of time to see the change in the viewer.
in some cases it is necessary to stop and start the server
again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
two problems with bitfarm open gpl version
after uploading one wordocument to dms bitfarm archive
enabled -coloured- / -high solution- the preview window
shows the coloured word document
in the following workflow we re-opened the word
document
open original file
with word from microsoft
then we make a simple change, for example some
addional text and save that in the prefilled
physical path, file is named automatically by bitfarm as
166171222437953.doc
\OurServer\Archiv-NRS$\Tool-Manager17062016121538\062016\17\166171222437953.doc
After that we re-opened the word document again to check the changes.
Changes are very well done, but now the preview shows
a black and white coloured document!
The coloured preview is lost!
-
this is a very bad effect and to fix it indicated
a lot of worktime.
Has anybody a solution?
with the button -open original file-
it needs a lot of time to see the change in the viewer.
in some cases it is necessary to stop and start the server
again.
There is already an existing thread with the same question here:
https://sourceforge.net/p/bitfarm-archiv/discussion/947775/thread/35c0a4a7/?limit=25#7856
This Bug is reproducible and will be fixed in the next release.