Mod Organizer 1.2.10 has a bug preventing LOOT 0.7.0 from working properly. This has been fixed in Mod Organizer 1.2.11, and later versions.
Mod Organizer can also interfere with LOOT's startup, causing causes LOOT's window to be blank when started through Mod Organiser: this can be avoided by adding the --single-process argument to Mod Organiser's LOOT launching settings, though doing so may have negative side effects.
I would suggest to rephrase the answer to:
In case that LOOT's window is displayed blank if run through Mod Organizer, update both LOOT and MO to the latest versions, which should fix the problem. In the unlikely case that you still experience this issue, start LOOT with the following command line argument:
--single-process
Currently the answer given in the FAQs is:
I would suggest to rephrase the answer to:
In case that LOOT's window is displayed blank if run through Mod Organizer, update both LOOT and MO to the latest versions, which should fix the problem. In the unlikely case that you still experience this issue, start LOOT with the following command line argument: --single-process