Well, then you could add them again and test this issue again.
We can not solve the problem if we cannot receive the required data to solve it.
In order to not waste time, I downloaded the package and performed all the tests that I mentioned earlier and more.
Let me describe my steps and what I found.
At the begin, I could not even log in as I received this warning:
INSECURE PASSWORD: Your login attempt has been blocked because the password you are using exists on lists of passwords leaked in data breaches. Attackers use such lists to break into sites and install malicious code. Please reset your password to reactivate your account. Learn More
That because I had reset the password on the replication process of the site, but even resting it to a very strong password didn't solve this issue so I disabled all non-Toolset Plugins via the Plugin files.
I was finnaly able to log in.
I updated Toolset CRED and made all the suggested tests and more (replaced themes, plugins, etc).
The issue was not solved.
I noticed that the duplicate does not load a specific CRED Style file (wpt-toolset-frontend.css) in .../cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/css/, while on my fresh install with stable Toolset, that file loads fine.
I finally managed to load the CRED Custom Styles from wpt-toolset-frontend.css on your duplicate, after I as well re-installed WordPress and cleaned the Install files (wordfence, etc).
Only then, after creating a new form, this started to work!
There must be something on the install that blocks the update to properly deploy and blocks the scripts from Toolset CRED.
I tested this on your site, with a Test Form and a Test Page.
hidden link
hidden link
Without the whole process, as I did it above, this does not work on your site.
Fortunately, now we know that this seems due to another Plugin and/or any of the many custom folders and files and database entries they make.
I suggest following my steps above on a staging site to pinpoint which of the 3rd party Plugin data breaks this.
This may very well be a security plugin or code, that somehow stops certain files to be loaded.