In one of my OmniHelp projects the generated .html and .js files are not copied from my project directory to the wrap directory. The viewer files and the graphics are copied. I added a WrapCopyFiles command to the [Automation] section of my _m2omnihelp.ini, but to no effect.
On a sidenote, the project where I get this behavior is a copy (all Frame and .ini files copied to another directory and paths adjusted in the _m2omnihelp.ini). In the original project, the same postprocessing steps work as expected.
Problem solved
The generated files are also copied to the wrap folder now. Unfortunately I could not identify the exact reason for the misbehavior. I suspect that happened due to moving my Framemaker and mif2go files from a local drive to a shared network drive. I repeated all steps carefully one by one, and now it works.
Don't use a network drive!!!
Very, very bad idea to work on a network drive. Frame has serious known problems with files on a network drive; you could lose them real easily if Frame doesn't like the access time required. That is, your Frame files would be corrupted and unusable. ALWAYS work on a local drive; just copy your finished work to the remote drive when you are done.
This isn't a Mif2Go problem, it's a Frame problem. Mif2Go doesn't care where the files are. But of course, all paths would have to be absolute in that case, and you MUST NOT put %omsyshome% on a network drive.
Hm, I find this a little
Hm, I find this a little surprising as I never experienced any file corruption when working with Frame files located on a network drive. And why is %OMSYSHOME% not allowed to be on a network drive? This is a scenario described in the User's Guide (30.3.3 Configurations shared on a network drive: If %OMSYSHOME% is located on a network drive...). Having everything on a local drive is, IMO, not really an option when multiple writers are involved. Anyway, I will keep an eye on this. For time being it is working fine.