Hello,
We are trying to update Newsmag from 4.7 to 4.9.1 and the previous developer made extensive use of the Theme API within the child theme.
I see that this is no longer supported in 4.9
What are migration steps to support this new version? Do you have a guide?
Functions from API used are:
td_api_category_template()
td_api_category_top_posts_style()
td_util::get_category_option()
td_util::get_option()
td_page_generator::get_pagination();
td_page_generator::get_category_breadcrumbs()
td_api_header_style::_helper_show_header()
td_api_footer_template::_helper_show_footer()
td_global_blocks::get_instance()
td_social_icons::get_icon()
They also created custom classes by extending the td_module and td_block classes so need direction on whether that is still supported in 4.9.x and if not, I’ll need documentation on how to migrate.
Let me know if you need any additional information.
Thanks for your help!
Hi,
The modification that you have in the Newsmag v4.7 the code that you have it need to be integrate in the last version of the theme by a developer, indeed this is not very ease to achieve because the theme functionality was moved in tagDiv Composer.
You can check our documentation for how to update the theme -> https://forum.tagdiv.com/newsmag-how-to-update-the-theme/
Thank you for your understanding!
Yes, I am a developer and I have already downloaded and installed the theme from themeforest 😉
What I need is documentation from you on how to migrate the functions I mentioned above to their equivalent in 4.9.x
Using the new theme pulls up PHP fatal errors due to new theme structure.
Thanks again for your help!
Hi,
All those are customization and unfortunately there is no documentation for customization, only all we have is a simple guide for a new plugin that can replace the td api.
Form the moment that the td api is not longer working there is a new plugin that can be use, but the code from td api need to be set this new plugin.
Developer info -> https://forum.tagdiv.com/developer-info/ just download the plugin, install it and try to move some of your old customization in this new plugin files.
Hope this will help you!
Thank you!
Yes, this is a step in the right direction. The developer page is for Newspaper, but I assume this applies to Newsmag as well, correct?
Also, I have a few more questions..
Is the API still supported? If I’m understanding correctly, API code needs to be in a plugin now instead of a child theme, correct?
Our client uses Visual Composer and it will not be possible migrate to the TagDiv builder as they have over 8,000 pages on their site.
– Can they still use Visual Composer without issue?
– Can we still use the API to add blocks to Visual Composer? see: https://forum.tagdiv.com/api-blocks-introduction/
Thanks again for your help!
Hi,
Yes, the plugin explain in developer documentation is working on both themes, at the end of documentation you can get a prev of this plugin -> http://prntscr.com/owe9yv
The api is not longer supported, and yes the code need to be move in the new plugin, this should work.
Also is possible that in the last version of the theme the Visual Composer to make some conflicts with taDiv Composer, this depend the settings that was made on pages and posts with Visual Composer.
This will work, but with the new plugin for developers, the old API will not longer work.
Also we recommend to make a test install and try there all those settings, including the update from v4.7 to v4.9 in this way the live website will not be affected.
Thank you!
Thank you. Where do I find documentation on the TagDiv classes/methods, etc. I can use within the new plugin for developers?
I saw these in the example you sent.
td_api_block::add()
td_util::tdc_is_live_editor_ajax()
td_util::get_block_error()
td_util::tdc_is_live_editor_iframe()
Thanks!
Hi,
You can use the code/documentation for api with the new plugin (creative plugin) -> https://forum.tagdiv.com/the-theme-api/
Thank you for your understanding!
Ok. I’m unclear on this. You had mentioned in your previous comment that the API is no longer supported, but now you are saying I should use it.
Please advise.
Hello,
What I mean is that you can use the example of the code for blocks from AMP inside the creative plugin, the code to create blocks / modules / templates … remain the same.
Hope this time I was more clear.
Thank you!
Hello,
Quick question…if our child theme is referencing files that were in the /parts directory of 4.7.x, theme, how do I access these parts in 4.9.x if the /parts directory does not exist?
Example:
Our header.php file contains these calls:
<?php locate_template( ‘parts/menu-mobile.php’, true ); ?>
<?php locate_template( ‘parts/search.php’, true ); ?>
How would I duplicate this functionality in 4.9.x?
Thanks!
Hello !
API files have been moved and this will require highly skilled developer skills in order to ADAPT the api. We suggest in contacting a freelancer or you can contact our custom work department in order to get a quotatin for this implementation.
Thank you !
Yes, I am a skilled developer.
Please send instructions.
Thanks!
Hello !
Unfortunately API modifications are not covered by the support due to our support policy:https://forum.tagdiv.com/newsmag-theme-support/
We are sorry for the inconvenience !
Thank you !
Hello,
I believe I am within your guidelines to ask for support since this is related to migration steps to your 4.9.x theme.
Please advise.
Hello !
Unfortunately due to our support guidelines the API is not covered.
Please note that we cannot offer support in this matter.
We are sorry for the inconvenience !
Thank you !
According to Envato policy, the author is required to:
“Provide some guidance on the way the item is designed”
Maybe the phrasing of my question was misunderstood. I am simply asking where I can find files that were in the /parts directory on the 4.7 theme that are no longer in the 4.9.x structure, not specific steps in how to customize the API.
This seems as it would fall under the support policy under guidance.
Please advise.
Hello !
Sorry for the missunderstanding !
Since the update of the core the files have been moved into the composer plugin: https://tagdiv.com/updating-the-core-of-tagdiv-themes/
The files are located here now: plugins\td-composer.zip\td-composer\legacy\Newsmag\parts
https://www.screencast.com/t/PjjhJdfrAgZ
I hope this was helpfull !
Thank you !
