I am fast losing patience and confidence in SCRIBUS.
I'm running version 1.5.8 on 64bit Windows10 Home.
Losing links to embedded images is an ongoing issue I have had on a number of occasions now and I don't believe it has anything to do with moving sla files or where the source of the images reside! There is another mechanism in play here somewhere.
Initially when I kept having this problem I decided that I would store all the images in a common directory and make sure the images were embedded and this seemed to resolve the issue.
However the problem has returned.
I produce a monthly village newsletter and as a consequence of such, a number of images are repeated in the same position month after month. I also keep an archive of each monthly issue going back some months.
Whilst creating the May issue this time I closed down my PC last evening, exiting all open windows beforehand.
This morning I login and load up the .sla file for this month and all the images, both new images for this month and regular images that are repeated every month, are not displayed. There is just the "X of doom" and the info pop-up tells me no image is loaded. Yeah, thanks for that!
Except for one image!
No files were moved in the interim between last evening and this morning.
I looked in the Image Manager and although in the path field it displayed the correct path to the directory where all the images are stored it only displayed the last .JPG file I copied into the image directory yesterday. All the others had the "X of doom".
I then loaded up last month's issue from the archive and all the images are displaying correctly and, in the Image Manager all the images are shown in the image directory.
Why is that?
It seems to me that something in the .sla file for the May issue has got corrupted and it no longer knows where the Image Directory is and yet it does for that one image. Very strange.
Looking at the failing .sla, the one for the May issue, if I do a get image on one of the image frames that has lost it's image, I am able to locate the correct image in the image directory and crucially if I now look in the Image Manager that image is now visible!
This is insane!
What is more important .......... what is the resolution to this exasperating error.