Hi there,

This issue was caused when WordPress v5.5 was released and was corrected in vSalient 12.1.1. Once you update to that, the problem should resolve: http://themenectar.com/docs/salient/updating-salient

Thanks.