Home » discuss » Public forums » iMIS Community

iMIS WCM overwriting images/documents

Posted April 7th, 2010 by james_schwartz
|

I'm having an issue with updating images/documents in iMIS WCM, and I was wondering if there is a way to prevent this from happening.

Basically, let's say I have a version of an image or a document, and I insert it into WCM content using the iMIS rich text editor. Let's say I've done this with hundreds of images and hundreds of documents.

Now I want to update 50 of those documents or images (for example, I want to bulk add metadata to a bunch of PDF files). So I upload the files directly to the file system.

The problem is, the next time iMIS publishes the content that links to that document or contains that image, it reverts back to the old version of the document. I can understand why this feature was added (to support multiple front-end servers). But there has to be a way to update multiple files at the same time without having to go into every piece of content that links to a document and re-upload that document, then re-insert it into the content.

Has anyone else ran into a similar issue and found a way to work around it? I have over 600 files that were updated, and there is no way that I can manually go into the content that links to those files to re-insert them...

Thanks
James

‹ Creating Activity Records with iBO Generating and Displaying unique number for order line items ›
login or register to post comments | printer friendly version

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

I'm not sure there is an

On April 14th, 2010 Courtney Robertson says:

I'm not sure there is an easy work-around.  When you upload a PDF file in a ContentFile, WCM will store a copy of the PDF in the content record (in the document system) and when you publish it will write the PDF to the file system.  I think there may be an RSE out there somewhere requesting the ability to bulk upload files, but it certainly wouldn't hurt to add a new one.  The only other option I can think of is if you upload the files directly to the file system to begin with (i.e. skip the ContentFile step) you might be able to reference them using hyperlink within a ContentHTML or a ContentLink.

Good Luck
Courtney Robertson

login or register to post comments

It wouldn't be easy, but if

On May 13th, 2010 kstoute says:

It wouldn't be easy, but if there are enough, it  might be worth updating the binary files directly in the database blob.

login or register to post comments

Did you submit this as an

On September 15th, 2010 Andie Millet says:

Did you submit this as an SMR? We have the same issue on all of our sites as well. The images that are uploaded by the image manager reside on the server. If you upload them from your web view they will propagate to your web server when you publish. If you upload an override an image using surf-to-edit, save and publish then it will get the image from the applications sever and replace the image on your web server. A quick fix is to update you images through the web view not surf-to-edit.

login or register to post comments