after the update, posts now look like this: https://prnt.sc/tFLKTwDUNpyc
The update deleted the composer and cloud templates plugins, and after the update had to reinstall them.
composer options are not there, even with the plugin being reinstalled.
Composer option gone screenshot: https://prnt.sc/j4kiFb7PC-C0
Yes, this happened to me as well.
There used to be ‘header styles’ and ‘footer templates’ that were built in and accessed in the theme panel. I bought 8 licenses of Newspaper and built all of my sites using these styles and templates, but now that I had had to upgrade to v12.x.x because of a malware infection, I find that they are simply not there and the sites look broken. I do not understand why they didn’t simply re-create the original templates in tagdiv-composer when they got rid of WPBakery builder and build them into the theme panel. Instead, I had to scour their cloud templates for similar looking templates and then customize them with tagdiv-composer.
While in the past everything was set and controlled from the theme panel, now with the latest versions you have to set some settings at theme panel and some from tagdiv-composer itself, making things even more confusing and harder to troubleshoot. Also, tagdiv-composer and WPBakery don’t play well together, so I have to switch the WPBakery plugin off when I need to work with tagdiv-composer, which is often because now it is central to everything. 80% of the content of the websites I work with was created with WPBakery, so its not an option to recreate all the content with tagdiv-composer. I did this for a handful of pages and it was too clunky and time consuming, so I gave up.
I hope this is helpful to you in some way.
Hi, I checked the screenshots and those errors appears because there is another plugin that needs to be installed, the tadiv Standard pack, please install that plugin from Newspaper > plugin (most of the time those problems are crated by child theme or extra plugins, sometimes it is better to disable them until the theme update is made).
Also, the standard template can be imported from the cloud and adjusted using tagDiv Composer after your needs.
Now all those that we made are 100% edited using the tagDiv Composer and cloud templates.
Thank you!
Thank you, I found it. I still don’t get why an “update” would be set to remove plugins. Which honestly is not so bad, If I had known about it in advance. I installed the standard pack plug-in which replaced the missing options. I thought that was the composer plugin. Thank you.
Hi CarlG,
This method t is used to have clean files at each theme update. Normally if there is nothing interfering the update goes like this: the theme is deleted then it it installed the new version, after that it checks the theme plugins that are activated, it store those in a transient and after that delete theme and try to reinstall those plugins from Newspaper > plugins.
Thank you!
Thank you, I will be prepared next time.
Dear support team,
same issue ongoing on my side. The update broken the website and it seems that the issue is caused by the composer and/or the cloud template plugin. Activating standard pack did not fix. Deactivating the newspaper theme makes the site working. I reached out server assistance and this is the response:
“From the analysis we made and my subsequent investigations, the issue is caused by the tagDiv Composer plugin.
I checked your PHP error log and the issue started immediately after this error was logged from tagdiv.
[14-Nov-2023 13:54:48 UTC] PHP Warning: file_get_contents(/var/web/site/public_html/wp-content/plugins/https://cloud.tagdiv.com/td_plugins/td-composer/3833ae26cf1f9d406448012ce1734aa1/td-composer.zip): Failed to open stream: No such file or directory in /var/web/site/public_html/wp-includes/functions.php on line 6805
Our recommendation will be to reach out to the theme/plugin developers support team with this as they are in the best position to assist you.
Can you please help me to understand how to fix?
Thank you,
regards
Pietro
Hi,
Please get in touch with us via email at contact@tagdiv.com and provide the wp-admin and cPanel access.
Thank you!
So, turning all plugins off then clicking (install update) worked for this error?
Thanks in advance for your help!!
Is this a Jetpack blocking issue, anyone know specifically which plugin?
Hello @TradersQue!
We always recommend it before any update, just to be sure nothing is interfering with our theme. You can see which plugin creates the issue by activating back plugin by plugin.
Thank you!
