Issue: Imported wiki images do not show on wiki image entry

It looks like the images you imported were on an external server, or the location is jailed to your XenForo installation, or your VW3 installation is owned by a different FTP user that is not readable by XenForo. In any of these cases, it is not possible to access the original file-data of the images, unless the original images were stored in the database.

In the case of an external import from VW3, the old attachments directory must be copied to a directory that is accessible to XenForo, and the new directory must be set as the attachment path in the config file.

In all my import tests, the problem of importing 0 size images does not occur when the paths are accessible.

Its on the same server, but I do serve my images from a cookieless domain. They are not in the database.

Whats interesting is that yesterday I copied the text from the main wiki page of my live site to the dev install and these pasted img bbcodes did not work either in VW, but did work in XF.
My vb forum attachments are my vw3 wiki attachments. xenforo imports vbforum attachments well. Why should vaultwiki not import these?

Looking at your live source site, it looks like all the attachments on there are broken. This includes images served from both attachment.php and picture.php. I have not tested other outlets, but this leads me to believe that the images are no longer stored where your source database thinks they are, or the permissions on the files have been changed. Thus, VaultWiki will not be able to import them. I don't think XenForo could import these either. It's likely the files were moved or disappeared since you last did a XenForo test import, or that you moved them to assist with that import.

That was a permissions issue. Guests could not see albums on my live site and therefore the thumbs did not load on the main wiki page for guests.

Fixed in the next release. Attachments from vBulletin 3 were not working properly. vBulletin changed the name of the primary key before vBulletin 4, and the alternate name was not exposed to the importer. Confirmed on your site and after exposing the new primary key the files were reported as existing.