This is actually unrelated to the ISBoxer update, and is a bug in Inner Space exposed by WoW 3.2.0. They changed a minor detail in how they load files, which happened to cause this bug. This bug is fixed in Inner Space build 5020, and you can simply restart Inner Space to correct the problem.

Enjoy