Yes, I understood brother, let me explain why is it happening.
pdf certificate's front editor is built-in javascript & dependent on pdf certificate library. as you stated one of the plugins is conflicting with the code of pdf certificate, it could be anything like the same selector or id. this wicked plugin is compelling to change pdf certificate plugins's default behavior.
we can't do anything about it, because of its a very tedious and time-consuming work to read someone's code and identify the origin of the issue.