I often rename my picture objects from the default 'pic' to a name that describes the picture.
If I later replace that picture, the actual file name 'xx.jpg' doesn't change to the new picture. The original picture file name is preserved although the changed picture shows.
Is there any way to avoid this besides keeping the original list of Pic 1 Pic 2 etc?
I am also experiencing this issue. Giant pain in the behind. We use temporary images in our courses while we are building them and then replace these images with the full image purchased from Getty Images. For tracking, I really need to be able to see "GettyImages-999999999" not "Cover photo 1" when I'm replacing them.
My workaround is to put the correctly named image into Storyline (where it shows up with the incorrect name). Then I export the original image and save it as the corrected name, and then put the exported image with the correct name back into Storyline. This is a lot of work to replace ALL the images in a course with the correctly licensed versions though. Sigh.
I'm also getting this. We created a project with an effect we wish to use for multiple clients. While we can change the layer name, the image name on the timeline seems baked in and when the image is replaced with a new .png file, the old file name remains on the timeline.
One thing I noticed - if you select the image on the stage (the image is outside of a group) and right click "replace picture>picture from file" the name on the layer then correctly reflects the image that you have replaced it with. If the image is in a group - this does not work. The image replaces but the old file name remains on the timeline. Only thing to do is bust everything out of the group, replace, then regroup. Problem here is if the group has triggers attached to it, paths associated with it, all of that is lost and you have to rebuild from scratch.
Just to clarify - when I say "bust out the group" I mean, ungroup, delete all the images and re-insert from file. Simply trying to "replace image" still doesn't work.
I was the original poster about this problem. And it IS a problem no matter how you workaround.
What I've found is that If your image has no styles applied to it, (no outline, shadow etc) replacing it with another image works just fine. The file name updates in the timeline. However if you have any effects applied to the original image, the file name doesn't change. This applies to both jpeg and png or changing from one format to the other.
My workaround is to duplicate the image in question with its formats and then move it off the original to someplace on your workspace. Then I remove all the format effects on my target image. Do not remove animation or triggers. I then replace that picture with the picture that I want. It should show in the timeline with the updated file name.
Finally I use the format paint tool to pickup the formats from the duplicate I previously made, and paste on the newly replaced image. The formats are copied and now I can delete the duplicate. This way is usually easier and safer than rebuilding the effects.
As noted above, some things do not copy with the paste brush so you may have to use trial and error to see exactly what works for you. I have found that entry/exit animations, paths and triggers won't copy, but they do not interfere with the replace picture function.
I am having this same issue. Storyline is up to date. I duplicated a slide then replaced some of the pictures on the new slide. The file name on the timeline does not reflect the newly replaced images.
This isn't a huge deal but it does make it confusing when editing the slide under "Form View".
Hello. I am also experiencing this issue. However, Emma Brown's work around did not work for me. I opened the renamed file in Photoshop and saved with a different filename. Storyline 360 still imported it with the old filename. In Photoshop, I even copied and pasted the image into a new .psd file and saved a new .png with yet another different filename. Storyline 360 continues to import the picture using the old filename. This is very frustrating, especially as I use different edited versions of the same picture and describe each difference in the filename. With Storyline 360 displaying multiple edited versions of the same picture, using the same filename in the timeline, it's easy to see where this would be frustrating as it slows down my workflow!
I am seeing the same issue in a new project. I created one "story" using a selection of images. For the other "story" projects I used the first one as a template, replacing each image with a different one. The file name of each image persists from the original, initial project, regardless of the other changes I make. On the timeline, therefore, all the image file names are incorrect in the second and third projects.
Sorry, this bug is affecting your workflow! We are currently prioritizing other bug fixes in upcoming releases, so it's not on our current roadmap. We'll be sure to update this discussion when it's slated for an upcoming release.
So I seem to have solved the problem of even a new project remembering an old file name. I went into the temp files and deleted all the associated files and my renamed images are showing up correct.
I'm glad Jennifer was able to help! It looks like your email footer came through by replying via email. This Peek video will show you how to edit it out if you’d like!
I've been having this issue as well. I noticed that some of the image filenames in one project had some special characters in them, I didn't want that to be an issue "down the line", so I renamed the original files. But no matter how I tried (import, drag/drop, replace picture), the new image would arrive with the old filename. Very frustrating. I also tried deleting the temp files, and saving the file again from an editor (Snagit Editor) but that didn't seem to work either. The image would always import with the wrong filename.
I then started a new project and imported the renamed image. Success! But when I tried to import the new slide from the new project into the old one, the image would arrive with the old filename! Argghh.
So, I went back to the new project and since the Media Library has an export feature, I thought I'd try to export the image with (another) new filename from there. When I imported that file into the new project, it worked. SUCCESS! The filename did not revert to the bad one.
Maybe this was a one-off solution (I was trying a bunch of different things before I found this thread), so YMMV.
When is this going to be fixed? We often have to hand off projects to other developers and if I've replaced images (with formatting applied), they don't match the revised and renamed images I provide to other developers. It makes it difficult to collaborate on projects.
We just released another update for Storyline 3. In Update 16, we've included important fixes and new features. One of the fixes we've included is: The object name didn't update on the timeline when replacing one image with another.
I am experiencing the same bug. I just updated to the latest SL and it still does it. I even drag a new pic and it insists on naming it after the previous pic. I copy/paste the file in Windows and increment the name (pic4.png vs pic5.png). When I drag pic 5, it shows up as pic 4. I have to open it in PSD and export again. I tried removing the outline with no difference. My image is cropped so maybe that is why, but still, even when importing a new pic??
If you are working locally, would you also be willing to share a copy of your image and project files here or in private by opening a support case so we can observe the behavior on our end? We'll delete the files as soon as we're done testing them!
45 Replies
I am also experiencing this issue. Giant pain in the behind. We use temporary images in our courses while we are building them and then replace these images with the full image purchased from Getty Images. For tracking, I really need to be able to see "GettyImages-999999999" not "Cover photo 1" when I'm replacing them.
My workaround is to put the correctly named image into Storyline (where it shows up with the incorrect name). Then I export the original image and save it as the corrected name, and then put the exported image with the correct name back into Storyline. This is a lot of work to replace ALL the images in a course with the correctly licensed versions though. Sigh.
I'm also getting this. We created a project with an effect we wish to use for multiple clients. While we can change the layer name, the image name on the timeline seems baked in and when the image is replaced with a new .png file, the old file name remains on the timeline.
One thing I noticed - if you select the image on the stage (the image is outside of a group) and right click "replace picture>picture from file" the name on the layer then correctly reflects the image that you have replaced it with. If the image is in a group - this does not work. The image replaces but the old file name remains on the timeline. Only thing to do is bust everything out of the group, replace, then regroup. Problem here is if the group has triggers attached to it, paths associated with it, all of that is lost and you have to rebuild from scratch.
Major pain.
Just to clarify - when I say "bust out the group" I mean, ungroup, delete all the images and re-insert from file. Simply trying to "replace image" still doesn't work.
I was the original poster about this problem. And it IS a problem no matter how you workaround.
What I've found is that If your image has no styles applied to it, (no outline, shadow etc) replacing it with another image works just fine. The file name updates in the timeline. However if you have any effects applied to the original image, the file name doesn't change. This applies to both jpeg and png or changing from one format to the other.
My workaround is to duplicate the image in question with its formats and then move it off the original to someplace on your workspace. Then I remove all the format effects on my target image. Do not remove animation or triggers. I then replace that picture with the picture that I want. It should show in the timeline with the updated file name.
Finally I use the format paint tool to pickup the formats from the duplicate I previously made, and paste on the newly replaced image. The formats are copied and now I can delete the duplicate. This way is usually easier and safer than rebuilding the effects.
As noted above, some things do not copy with the paste brush so you may have to use trial and error to see exactly what works for you. I have found that entry/exit animations, paths and triggers won't copy, but they do not interfere with the replace picture function.
I hope this helps.
I am having this same issue. Storyline is up to date. I duplicated a slide then replaced some of the pictures on the new slide. The file name on the timeline does not reflect the newly replaced images.
This isn't a huge deal but it does make it confusing when editing the slide under "Form View".
I've posted a separate discussion post here: https://community.articulate.com/discussions/articulate-storyline/file-name-not-refreshing-when-replacing-images
Hello JD!
Popping in here to note that I responded to your discussion post here. Both conversations are linked, and we'll check back in with any updates!
Hello. I am also experiencing this issue. However, Emma Brown's work around did not work for me. I opened the renamed file in Photoshop and saved with a different filename. Storyline 360 still imported it with the old filename. In Photoshop, I even copied and pasted the image into a new .psd file and saved a new .png with yet another different filename. Storyline 360 continues to import the picture using the old filename. This is very frustrating, especially as I use different edited versions of the same picture and describe each difference in the filename. With Storyline 360 displaying multiple edited versions of the same picture, using the same filename in the timeline, it's easy to see where this would be frustrating as it slows down my workflow!
I am seeing the same issue in a new project. I created one "story" using a selection of images. For the other "story" projects I used the first one as a template, replacing each image with a different one. The file name of each image persists from the original, initial project, regardless of the other changes I make. On the timeline, therefore, all the image file names are incorrect in the second and third projects.
Hi Megan!
Sorry, this bug is affecting your workflow! We are currently prioritizing other bug fixes in upcoming releases, so it's not on our current roadmap. We'll be sure to update this discussion when it's slated for an upcoming release.
This post was removed by the author
So I seem to have solved the problem of even a new project remembering an old file name. I went into the temp files and deleted all the associated files and my renamed images are showing up correct.
Worth a try perhaps?
Thanks for the tip! It works perfectly.
Hi JD!
I'm glad Jennifer was able to help! It looks like your email footer came through by replying via email. This Peek video will show you how to edit it out if you’d like!
I've been having this issue as well. I noticed that some of the image filenames in one project had some special characters in them, I didn't want that to be an issue "down the line", so I renamed the original files. But no matter how I tried (import, drag/drop, replace picture), the new image would arrive with the old filename. Very frustrating. I also tried deleting the temp files, and saving the file again from an editor (Snagit Editor) but that didn't seem to work either. The image would always import with the wrong filename.
I then started a new project and imported the renamed image. Success! But when I tried to import the new slide from the new project into the old one, the image would arrive with the old filename! Argghh.
So, I went back to the new project and since the Media Library has an export feature, I thought I'd try to export the image with (another) new filename from there. When I imported that file into the new project, it worked. SUCCESS! The filename did not revert to the bad one.
Maybe this was a one-off solution (I was trying a bunch of different things before I found this thread), so YMMV.
Hello Everyone!
I'm happy to return to this discussion with an update—we've fixed the issue where:
The object name didn't update on the timeline when replacing one image with another.
Be sure to install the latest Storyline 360 Update 60 to take advantage of all the recent features and fixes.
If this happens again, please let us know! Or you can work directly with our support engineers here.
When is this going to be fixed? We often have to hand off projects to other developers and if I've replaced images (with formatting applied), they don't match the revised and renamed images I provide to other developers. It makes it difficult to collaborate on projects.
Hi, Susan.
Thank you for reaching out!
As Becca mentioned above, the fix for this issue was released in Storyline 360's latest update:
Here are the instructions to update your desktop application.
Oh, you made my day!! This is going to make my Life so much easier! Thank you! (I just updated, and it's a fabulous thing.)
Hi folx! I have great news to share!
We just released another update for Storyline 3. In Update 16, we've included important fixes and new features. One of the fixes we've included is: The object name didn't update on the timeline when replacing one image with another.
Make sure to download the newest version of Storyline 3 by following these step-by-step instructions.
Please let us know if you have any questions by posting here, or reaching out to our Support Engineers directly.
I am experiencing the same bug. I just updated to the latest SL and it still does it. I even drag a new pic and it insists on naming it after the previous pic. I copy/paste the file in Windows and increment the name (pic4.png vs pic5.png). When I drag pic 5, it shows up as pic 4. I have to open it in PSD and export again. I tried removing the outline with no difference. My image is cropped so maybe that is why, but still, even when importing a new pic??
Hello D R,
Sorry to hear that you ran into this issue! I'd like to ask a few things to help clarify your experience:
If you are working locally, would you also be willing to share a copy of your image and project files here or in private by opening a support case so we can observe the behavior on our end? We'll delete the files as soon as we're done testing them!