Child theme and 9.7

At least tagdiv should implement a function to insert php code to templates/pages/posts via tagdiv composer..

I will NOT be updating anymore until Child theme support is back.

I use child theme for :

-Adding Trending News ticker in the /parts/header-style-9.php
-Adding Facebook Comments shortcode to loop-single-2.php
-Custom pages using loop-customposttype.php
-Adding Google Translate icons to td_module_single.php
-Remove some Meta info from td_module_slide.php

and other things. We need child theme support. Please find a way to let us edit the php code.

thanks

/Johnny

• This reply was modified 7 years by bananaj.

Newspaper is not my only Theme.
I have several other envato Themeforest WordPress themes including X Theme and Avada Theme.
They are still up and running with a child theme following envato requirements. So whats the issue?
We all know it is best WordPress practice to use a child Theme.

• This reply was modified 7 years by knaggsy.

@raqy couldn’t agree more. I’ve decide to stay at 9.6.1 till they deliver a right solution for child theme

The treatment given at this time is so much disrespectful. A decision was made away from the interests of your customers and you seek to exempt yourself by hiding behind the new envato requirements.

Maybe you guys were just rushing to make this update available, which is really a downgrade, since it worsens in every way the functionality of the template. You know there is no possibility in wordpress to make child plugins, and even then you moved the theme files to plugins folders.I’ve checked that a header template file (just like some others) still remains in a folder structure in the theme directory. All others have already been moved to plugin folders. So this was not a well done update, it was a trick, was a workaround that worsened the quality of the template.

Come on guys, you can do a lot better for your customers. I hope this is not a complete abandonment of your customers, and you intend to support your customers in the sense that you know it is right.
But do it quickly away because it’s already obvious to everyone here including my team that the effort to get a new template is minor than looking for alternatives to save the mess you guys have made.

Agree – we also work with multiple themes and the other themes still work with the child theme while meeting envato requirements.

We are also going to wait and see if they will make this situation right. If not we will stop using this theme all together. it is a shame since we already invested alot of hours and money it getting this theme customized. but we will cut our losses.

I was able to migrate my customizations to the footer in a child theme by moving all of the customizations to /footer.php and disabling the footer in the theme panel.

When I tried to do the same with the header..no love. I even experimented with deleting the file in /parts/header one by one and they and no effect.

So I did what was suggested and tried to build the header in tagDiv Cloud library.

WHAT A NIGHTMARE!

I’ve been working a lot with ELEMENTOR lately which is pretty much drag and drop with granular control over everything you do.

To get things the way I wanted, requires extensive CSS manipulation (there are only limited options for creating columns) and worse when I tried to create the mobile version of the header, I started getting a barrage of error messages, which ended up nuking the whole template (hours of work lost) which I now have to go in and recreate and hope it doesn’t happen again.

If you want your big plan was to “require the use the tagDiv Cloud Library” then maybe you should have made sure that it was up to the task before this release.

And oh by the way, how the heck do I migrate from my staging site, to the live site. I don’t see any way to export anything from the library. Since your initial post said to use a staging site first to test, then what accommodations did you make for getting the template from point A to point B?

• This reply was modified 7 years by pmats777.