Home User profile
chasedesign
tagDiv Member
This user did not write anything. So we are just showing here some random text to make the profile page look nice :)
chasedesign
tagDiv Member
Migrating Theme API from 4.7 to 4.9.x - reply
#313037
Sep 19, 2019 at 9:21 am

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.

chasedesign
tagDiv Member
Migrating Theme API from 4.7 to 4.9.x - reply
#312986
Sep 19, 2019 at 3:24 am

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.

chasedesign
tagDiv Member
Migrating Theme API from 4.7 to 4.9.x - reply
#312809
Sep 17, 2019 at 6:10 pm

Yes, I am a skilled developer.

Please send instructions.

Thanks!

chasedesign
tagDiv Member
Migrating Theme API from 4.7 to 4.9.x - reply
#312685
Sep 17, 2019 at 6:53 am

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!

chasedesign
tagDiv Member
Migrating Theme API from 4.7 to 4.9.x - reply
#309995
Aug 23, 2019 at 5:12 pm

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.

chasedesign
tagDiv Member
Migrating Theme API from 4.7 to 4.9.x - reply
#309922
Aug 23, 2019 at 9:13 am

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!

chasedesign
tagDiv Member
Migrating Theme API from 4.7 to 4.9.x - reply
#309831
Aug 22, 2019 at 3:43 pm

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!

chasedesign
tagDiv Member
Migrating Theme API from 4.7 to 4.9.x - reply
#309815
Aug 22, 2019 at 2:41 pm

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!

Viewing 8 posts - 1 through 8 (of 8 total)