To avoid this condition from occurring, you should disable these components within the template prior to them being assigned to the node. I know it's a kludgy workaround. Hopefully it's only temporary. We're tracking this as a bug internally under FB319266 and hope to have this addressed properly in an upcoming release.
↧