This is a odd ball question, and I'm just hoping there is some know issue that explains it. I am importing a lot of content via REST into a relatively new Telligent instance and I am finding a single content blog post shows a broken image. Other images work fine, so I am having troubleshooting it. Here are the facts and anything that stands out about this image: A png It is a small emoticon (667 bytes) Shows as broken on the page Clicking the image for the enlarged view shows a page saying " You do not have permission to view this directory or page." When the blog post is created or updated it is NOT moving the temp image to the "communityserver-blogs-components-weblogfiles" CFS store, instead it is staying in the "CommunityServer-Components-MultipleUploadFileManager" CFS store. No errors when I look on the Monitoring page in the admin. If the image is manually added to the page it works fine. Verint Community version 11.1.6.14291 in Developer Mode My guess is that the file is being posted to the server, but something is failing with the processing and moving it to the correct CFS store. Unfortunately I don't know what is going on under the hood, and that is where I am looking for help. What processing or known issues might cause something like this?

Inline image fails to display when added via REST

This is a odd ball question, and I'm just hoping there is some know issue that explains it.

I am importing a lot of content via REST into a relatively new Telligent instance and I am finding a single content blog post shows a broken image. Other images work fine, so I am having troubleshooting it.

Here are the facts and anything that stands out about this image:

A png
It is a small emoticon (667 bytes)
Shows as broken on the page
Clicking the image for the enlarged view shows a page saying "You do not have permission to view this directory or page."
When the blog post is created or updated it is NOT moving the temp image to the "communityserver-blogs-components-weblogfiles" CFS store, instead it is staying in the "CommunityServer-Components-MultipleUploadFileManager" CFS store.
No errors when I look on the Monitoring page in the admin.
If the image is manually added to the page it works fine.
Verint Community version 11.1.6.14291 in Developer Mode

My guess is that the file is being posted to the server, but something is failing with the processing and moving it to the correct CFS store. Unfortunately I don't know what is going on under the hood, and that is where I am looking for help.

What processing or known issues might cause something like this?

Top Replies

Former Member over 4 years ago +1

After a certain amount of time, items in the MultipleFileUploadManager will be cleaned up and deleted. This is a temporary location for uploaded files, after uploading to this location you should receive…

0 Former Member over 4 years ago

After a certain amount of time, items in the MultipleFileUploadManager will be cleaned up and deleted. This is a temporary location for uploaded files, after uploading to this location you should receive a contextId that you would then provide when creating content via REST. Based on the info you provided, this is definitely where the issue lies, especially since uploading through the site correctly moves and maintains the image.

Are you saying you're updating other content the exact same way and the images are being converted correctly?
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Robert Hanson over 4 years ago in reply to Former Member

> Are you saying you're updating other content the exact same way and the images are being converted correctly?

Yes, even images in the same content item all work fine, which is what has me scratching my head. I've migrated a lot of content into Verint the last few years and this is the first time that I've seen this (that I know of), which is why I am wondering about the specifics of the mechanism that copies the file from one CFS store to the other. Perhaps it is the image, but that only makes sense if the image is being read or manipulated by Verint and that is causing some sort of error.

> after uploading to this location you should receive a contextId that you would then provide when creating content via REST

In this case I am using the URL in the response to posting the file to CFS. I then use the URL in a [View:] macro. Is there a way to use the Context ID in the [View:] macro as well?

I understand that it is impossible to guess at what the issue is here, but any wild guesses would be welcome.

Fortunately I have a way of detecting this issue in the imported content so I will have to see if this is a one-off or something that occurs in multiple situations. And if I see a trend I can let you know and will try to provide a way to replicate it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel