With customisation the update process is somewhat painstaking.
Among other things, Custom Post Types and Custom Taxonomies are no longer working – even after rebuilding and references the tagDIV API documentation (which previously successfully allowed this).
• Is the API documentation current?
• What is the recommendation for getting Custom Post Types and Custom Taxonomies working in the 9.7 update? Following the API documentation – this is not being recognised in 9.7.
• What is the recommended process for identifying and installing any further files – Specifically, there are certain cross-references such as:
'used_on_blocks' => array('td_block_11', 'td_block_18'),
This refers to php in shortcodes however the entire shortcodes folder with contents was not part of the update. Is copying across from the old version the correct approach to restore or recreate?
Hi,
Regarding the issue, note that the old API plugin will not work anymore. You can use the new creative plugin for this purpose – https://forum.tagdiv.com/developer-info/
But maybe what you are trying to do is possible without resorting to this plugin. The flex blocks have multiple options and settings and can be customized in many ways. You could use a flex block instead of adding new ones.
Please check this topic about the Newspaper v9.7 -> https://forum.tagdiv.com/topic/important-new-update-newspaper-9-7/
TagDiv Cloud Library -> https://tagdiv.com/what-is-the-cloud-library/
Thanks.
For clarification, the API plugin is not being used. I have seen the announcement however the links refer to standard updates.
I am after more details on using custom post types with the new version and details on the key differences so that I have a clear overview of retired parts / components and can migrate my number of customisations so that they work in 9.7
Hi,
You still can use the Custom Post Types and Custom Taxonomies but now you can not longer set in child theme template for theme, you can use only the default template.
Now the post template can be found in wp-content/plugins/td-composer/legacy/Newspaper/parts/single -> https://www.screencast.com/t/tUeFJjisP
Sorry for the inconvenience and thank you for your understanding!
Thank you for this.
The good news is that I wasn’t using a child-theme.
For custom assets, these have been defined in the the themes > Newspaper > includes > td_config.php
In the update, these items defined in td_config.php with files in the Template still (mostly) work however as all of the original files are now moved into the plugin, what is the best approach… attempting to rebuild in the plugin or retain these in the theme folder.
To initialise the assets within the plugin, is the reference file td-composer > includes > tdc-config.php ?
Hi,
The best way will be to rebuild in the plugin; unfortunately, each way you chose, if you make any updates to the theme, all those customization will be lost, also now our developers team are trying to make possible to do all customization you need using tagDiv Composer and tagDiv Cloud library.
Thank you!
