Is there a ContentHub bug about the problem with loading it asynchronously? By the looks of it the fix is to work-around that.
Is there a ContentHub bug about the problem with loading it asynchronously? By the looks of it the fix is to work-around that.