I have a page-style custom post type named “guides” that I want to use with TagDiv Composer. TD Composer was working properly at one point, but after some recent updates we began seeing an error when loading TD Composer. Unfortunately, Newspaper is still very much a beta-project for us (i.e. we have not launched the website using the theme yet; the live site is still using a custom theme we built years ago), so I do not have a clear timeline of when the error first appeared (since we aren’t checking it all the time).
When loading TD Composer on any “guide” post type, a red bar appears at the top of the screen with this error:
“Errors happened during tdcIframeData.init() -> bindViewsModelsWrappers()!”
The error prevents new elements from being added to the page.
TD Composer still works properly in the WordPress “page” post type. We considered just moving all our guide content to be listed as Pages instead, but there are hundreds of them. The custom post type is for organization more than anything else, and we would really like to keep it if possible. Is there a solution to this error?
The custom post types are added in function.php using the standard WordPress creation code.
I couldn’t say exactly if one of these cases are to blame, but there are some situations when that error is displayed by the composer
– https://forum.tagdiv.com/topic/errors-happened-during-tdciframedata-init-bindviewsmodelswrappers-14/
The composer should work for default WordPress pages, with custom page types we have not made any testing up to his point. If errors are displayed only when using it on these custom page types, that would suggest it will not work in these circumstances. The plugin and theme have received many modifications over the latest updates.
