on this page:
https://tagdiv.com/updating-the-core-of-tagdiv-themes/
it says if you don’t have a child theme follow the instructions below..
but what if you DO have a child theme?
I have several customizations in a child theme that disappear after updating to 9.7
Thanks
thanks
Same question. If I use custom code in category.php, single.php, page.php, loop-single-1.php and others, what can I do to save my changes?
same here!
You shouldn’t release this new update without proper documentation as to where one should apply the child theme customizations as of this new update. And as it is crucial update, you should release a beta for testing ahead so site owners could get prepare ahead.
You just say to us: we’ve changed the theme, as we wanted to or instructed to, whatever, go find yourself.
This is a disgrace!
Hi,
We recommend to make first an install to a copy to your website on sub-domain or localhost -> https://www.screencast.com/t/wVH9sfkTV312 in this update all that is changes are some files that was moved in our theme, and is possible some settings that was made in child theme to have a different path.
Thank you for your understanding!
Well that doesn’t help whatsoever. My changes are already being tested in a staging environment. As noted in @raqys response you should have been prepared with some documentation of how to migrate if using a child theme, not just “use a testing environment”.
Agreed
Hello,
Most of the theme files were moved into the tagdiv composer plugin as per the requirements of envato: https://help.author.envato.com/hc/en-us/articles/360000472383-WordPress-Theme-Requirements.
We wrote an article on the subject here: https://tagdiv.com/updating-the-core-of-tagdiv-themes/
Moving forward with such requirements, a child theme will only work with functions.php, and style.css as there are very few files left in the main theme as envato requires all functionality to be added through plugins.
Sorry for the inconvenience and thank you for understanding.
So pls write a document as to how to child theme the plug-in or whatever necessary to make it work.
Because what you are telling us right now is No More Customization – is it not?
So what all your paying!!! clients with customizations would do?
And pls stop copying your useless excuse note all over the forum and give us some operational advice pls.
Hello, I am a recent user in this community. Until now what I have seen is an excelent support by tagDiv and tagDiv always answering. But after this child theme issue I am concerned.
It appears that you released the update with no worries about child theme as it is barely mentioned on your solution article. Please check for the ‘child’ word in that article too see.
I think we all have clear the envato reason but not at all the tagDiv solution.
Regards
We changed our theme to tag/div recently, hoping that we would have a top notch theme with great and well thought out upgrades and support. Needless to say we are disappointed in knee jerk changes (getting rid of built in amp support and relying on mobile theme and wp amp) and this latest upgrade is unacceptable. Our site simply does not work and gives this td-api error and the site itself is code 500).
Al we can tell from you – is sorry you are on your own. I would say this is the beginning of the end for you company if you don’t change you attitude.
Hi,
We tried to get your attention for child theme in our article, for the moment that a lots of files was moved in tagDiv Composer plugin, these files that was moved will not work in child theme because now these are in plugin not in theme -> https://www.screencast.com/t/z5pqD3i116Uw -> https://tagdiv.com/updating-the-core-of-tagdiv-themes/
Unfortunately, the old td-api-plugin plugin does not work anymore and we recommend using this -> https://forum.tagdiv.com/developer-info/
You can create these modules that you made with that api using the flex blocks and you can save the element in a shortcode to can use it later in orders pages -> https://www.screencast.com/t/a2ikt4tq
Thank you for your understanding!
Come on guys, really. Stop repeating this mantra and start working on a reliable solution if you want to keep your operation going. Your credibility and reputation after this fiasco is going down the drain and you are not helping yourself one bit.
Is it the end of TagDiv? As I’m sure we’ll find other theme who can deliver.
Why don’t you listen to your clients? Or is it that you have decided in advance to give up on us? and any other prospects who would clearly decide on other themes after getting to know this.
Some customizations can’t be made through the TD composer, like coauthor integration, rtl adjustments etc. Elements that you also refuse to integrate yourself.
I’m really sorry now for choosing you over other themes that do support those things.
Really disappointing.
Thumbs down in all possible fora from now on.
I really hope you get back to your senses. ASAP!!!!
i disabled the child theme and the td-api plugin in a test server environment. when i update the theme the site no longer gives the 500 error. however, the plug ins do not update or activate. (it looks like they are updating and activating) but when you refresh it is not active. hence nothing is working because the plugins can not be updated or activated.
Not to sound frustrated, we outsource all our development efforts. when we moved to you theme we spent $2K to customize the theme and now we cant upgrade and potentially have to spend another 2k to go through the upgrade.
Same here. I posted several comments in this forum regarding this topic with no helpful answer. Common guys, it’s a simple question: How can we overwrite files in the composer plugin? This is not rocket science, is it? If we cannot do this, all customization would be lost (or at least not update-safe). Both is not acceptable.
Hi,
Unfortunately for the moment we do not have a solution for this ( something like child theme ), what you can do for them moment is to save the changes you make in tagDiv Composer plugin and when you make the next update if there will be no solution for override, you can set the website in maintenance mode and set the saved changes quickly in tagDiv Compose plugin files.
Sorry for the inconvenience and thank you for your understanding!
If I understand you correctly what you are saying is to reinstall the theme from scratch and hope that the child theme customization you made will work.
I guess we will hold off on this upgrade and find another solution since it looks like this is not a very reliable company that we want to work with for the long haul.
If I was in your situation – I would pull back this update and redo it so that it is more manageable and addresses what your customers are telling you here as feedback.
Otherwise – it looks like a clusterfuck from about 5000 miles away.
Good luck folks.
If I understand you correctly what you are saying is to reinstall the theme from scratch and hope that the child theme customization you made will work.
Unfortunately, you’re wrong. Modified files in the child theme will not work anymore for files that were moved to the plugin folder. You have to replace those files there. After every update, of course. This update is an epic failure.
I stand corrected. Thank you. We will just don’t do the upgrade and wait/hope for the folks here to get some business sense and correct this issue or find an alternative.
Cheers
Hi,
The changes from current update was not our decision to make, these was the envato requirements: https://help.author.envato.com/hc/en-us/articles/360000472383-WordPress-Theme-Requirements
I’ve noted this as a request to our developers team to try to find a solution for child theme.
Sorry for the inconvenience and thank you for your understanding!
Thank you for your understanding?
Sorry but doesn’t seem to be too much “understanding” here when you implement this type of change that has major implications and use Envato as the fall guy.
IMHO what you should do is continue to support the current 9.6.1 (which currently has a cross scripting vulnerability) and release 9.7.x as a new theme or some other option to allow those of us who are using the theme not strictly “out of the box” to continue to use it without having to spend many hours or ask our clients to expend hundreds if not thousands of dollars to continue using a theme, that we recommended to them and now look like chumps for having done so.
That being said Envato’s documentation which you choose to use as cover also states
“To reduce the chance of users being negatively affected if they do not install/update the plugin, themes may choose to include a fallback until 30 November 2019. This is not compulsory.”
Reading through this post, I think what Calin is saying is that doing this major change to the structure of their theme was not by their choice, it was a requirement by Envato. These guys rely on Envato for the sales of their theme, so I’m assuming they have no choice but to comply with these Envato requirements. This is not them providing bad support (they are actually pretty amazing at support), its them being stuck between a rock and a hard place.
I think tagdiv should release patch for Newspaper 9.6.1 users. Because a lot of users, include me, use old version 9.6.1 because in 9.7.* cannot save current customization from child theme.
@smehr: I think the comment before yours shows they could still have provided a temporary solution.
This is the first post of this account of my client here. We’ll be keenly following (and many others I’m sure) this thread and hopefully there will be a solution soon.
Thanks.
