BUG: Importing a snapshot with long images names fails on W7

[leehack]

When importing a snapshot that has long product image names with V10 on Windows 7, a fatal message comes up on screen saying process has been aborted and you get 'detail' of the large image name with a '! has been caught' message. However when trying same snapshot on XP, imports proceeds fine with no problems.

I fully endorse the limit on image name length, i think 31 characters is the recommended limit, but once actinic has allowed you to use longer names, it cannot then stop an import because you have done so. Even more so, OS should not be playing a part in the process.

Screenshot of error attached.

[NormanRouxel]

Whew that's some path there. Probably not the filename itself but the path + filename. Looks like there's a 255 character limit for the overall path + name being broken there.

[Duncan Rounding]

I think the OS will still interfere with this as the routines used will depend on the windows components. That is after all one heck of a file path!

I think that some servers may not even be able to handle an image name of the at length. I mean talk about descriptive image naming.

[leehack]

Fully concur and indeed have fed back the same, actinic should be stopping this at source though, not showing up errors down the line.

[Duncan Rounding]

TBH - If possible I think windows should stopping you even being able to name a file longer than the path limit.

[NormanRouxel]

I think windows should stopping you even being able to name a file longer than the path limit

Windows just did I think. Unfortunately, the file + path became too big during an automatic operation, hence Lee's error.

The problem is that the customers file is a just-legal path + filename so it was allowed.

It looks like the Snapshot was being imported from an earlier V10 version and the upgrader kicked in.

When Actinic makes an upgrade it copies the existing files + their Site-relative paths into a backup folder in case of disaster. E.g. "C:\Program Files (x86)\Actinic v10\SiteUpgrade\Backup v10.0.2.0.0.0.KIIA\3000rpm".

That's an extra 80 bytes getting added to every file path. Resulting pathname is now way too big and ka-boom!

Any warning when adding files would have to be issued with a very generous (say 100 bytes) overhead to allow for such scenarios.

[leehack]

It's a 10.0.2 snapshot into 10.0.2 so no upgrade involved, something specific to W7 for sure as never happens on XP.

[Krithika]

Hi Lee

I have tried the above, using a similar file path to yours, with different versions on both Win7 32 and 64-bit versions, but I do not get the fatal error here. Could you run a Compact DB(in case you have not done it already), export a fresh snapshot and try again please?
If it still breaks, suggest you contact support so they can have this checked.

Regards

[leehack]

Thanks Krithika. Client has now changed all images to be shorter names, snapshotted and it has imported fine my end this time, so without question it is linked to the length of the image names. Actinic needs to start providing warnings about this (like photoshop does) and stop people using something that can later break the site or is against recommended design limits (31 characters).

[NormanRouxel]

It's a 10.0.2 snapshot into 10.0.2 so no upgrade involved

O.K. It must be Actinic making a backup of the existing site before installing the Snapshot. Bit strange that it does it into a "SiteUpgrade" path.

[leehack]

Yeah i think you're right, seems to always backup now before you import, so i presume a failsafe has been added.