Errors happened during tdcIframeData.init() -> bindViewsModelsWrappers()!
Hi,
I believe you are getting that error when you are editing a page. Does it happen if you edit a new page with the composer? if it only happens for a specific page only then the problem is there. Edit pages that were built with the tagDiv composer only, don’t edit pages built with a different editor or contain elements that were not added with the tagDiv composer.
Or maybe you are receiving the error while trying to access the Cloud library section. If that is the case, please re-save the permalinks in WordPress settings and try again
– https://www.screencast.com/t/bi2MeCnHhU1
Let us know.
Thanks
Hi guys,
I’m jumping here as I have the same issue.
If I create a new page, I don’t have it.
But for the existing page, I have the “Errors happened during tdcIframeData.init() -> bindViewsModelsWrappers()!” message that appears.
How to fix this and be able to build back and make some changes on the existing page, and moreover my Homepage ?
Cheers,
Jo
Hi,
@Johann You can edit the page in the back-end
– https://www.screencast.com/t/O9kkhtkM8CQ
If you entered any code or non-composer element in the page you could remove it from there. Then try to edit it again. Once the problem element is removed the error should not be displayed anymore. Pages should contain only elements that were added with the composer, adding other content or code may cause such problems.
@Johann We could take a look, send us an email at contact@tagdiv.com and provide admin login. We will take a look at the homepage issue. Please include a link to this topic in the email.
Hi,
@fmarkin@gnail.com Did you solve the problem by reinstalling? Usually this is something related to a specific page. If you still have the problem, send us an email at the address mentioned above, also mention more details about it. Include a link to this topic in the email.
Hi, I am having the same issue, i dont have .htaccess since i am using nginx.
How to solve this?
Hi,
@tusharbhayana If it is the same for you and it happens only with a specific page, then that page contains something that causes the problem.
Maybe you entered some custom code in it, like ad codes or scripts etc. Remove them from the backend if you did that, as mentioned above.
Or try the same and return to a previous revision of the page like Johann mentioned.