Kriss has worked for Transition since 2002. According to Miles, she makes "an indispensable contribution to virtually every project we run". On a day-to-day basis many of you will know Kriss as the front line voice of our Lectora support. She also designs and delivers our courses for Lectora, CourseMill and our Lotus Tutorials. A Lectora Certified Advanced Author, Kriss has a City and Guilds certificate for teaching adults. With a great mind for detail and learning process, Kriss works on the production and publication of e-learning projects for clients, bringing together the skills many of our Lectora customers seek for themselves i.e. using Lectora to translate classroom teaching skills into the context of blended learning.
- Recent posts by Kristen Featherstone
- Other bloggers
Love Lectora gems no.33: Incomplete course publish with error – no.2!
Posted by Kristen Featherstone on 16 July 2013 · filed in Lectora
Back in the depths over 18 months ago I wrote a blog about a course that was giving me a red error and failing to complete the publish. Well, I have encountered another instance of this that left me scratching my head rather furiously!
The first instance of this error can be found at Love Lectora gems no.4: Incomplete course publish with error. This latest instance was in a course which was sent to me as a zip file. I extracted and opened up the title; selecting to run the Publish as normal, I was confronted with this error about copying a file:
What was interesting was the fact that the error had appeared
when creating the first resource, which happened to be an
Past experience told me, 'Ah ha, images again!' as it was an image that had caused the problem previously. Well, no amount of poking or prodding the image which had stopped the publish this time round seemed to get me passed the error to complete the publish.
After furious head scratching and a weekend later, I took another look at the error message and realised that somehow Lectora was trying to copy the image from the images folder in the file to the images folder within the newly created html folder, which is the normal process, but the course file names were different:
After getting this far I needed to understand the difference in
file names, which seemed to be an additional underscore in the name
of the folder where the Lectora .awt file was stored. The problem
seemed to be in the name of the course/title.
I went back and looked in the Title Explorer at the name of the course and there, where the extra underscore should have been, was a colon:
'Ah ha', I thought, 'it's the colon causing the problems'. Although this was true it still wasn't quite what I thought, because even after removing the colon I was still getting the same error.
The problem was caused by the fact that, granted there was a colon in the name of the course, but exporting the course to a zip file removed the colon from the course folder name and replaced it with an underscore. When the course was extracted from the zip file the extra underscore stayed in the name of the course folder, while inside Lectora the colon was still there in the name of the Title.
While running the publish, Lectora was taking a resource out of the images folder which was residing in the course folder with the extra underscore. It was then trying to create the html folder inside a course folder with only one underscore, completely ignoring the colon and the fact that a folder with that name didn't exist:
This issue had a double face on it: the use of a colon in the course name inside Lectora and exporting the course to a zip file.
So it is advisable not to use any special characters in
the names of courses or in page names as
Love Lectora no.13: Your e-learning course wants you to download
the next page tells you.
No wonder it had me head scratching!
NB While this error can be replicated in Lectora Version X, in Version 11 the colon in the name doesn't seem to cause any issues with publishing.
Have you been scratching your head as much over a publishing error? Share your experience with us below - perhaps we can save your scalp any further irritation!
0 comments · add a comment · this blog is moderated