Update to New Version Failed

I tried to update Newsmag to the version released last week. It failed miserably.

Before installing, the old version was deleted and the new zip file was uploaded. The wordpress panel indicated the theme was installed and activated. When trying to access the site, I get these wonderful things:

wp booster error:
td_api_base::mark_used_on_page : a component with the ID: td_block_1 is not set.
/home/rebellio/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_api.php

wp booster error:
td_api_base::mark_used_on_page : a component with the ID: td_block_2 is not set.
/home/rebellio/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_api.php

wp booster error:
td_api_base::mark_used_on_page : a component with the ID: td_block_3 is not set.
/home/rebellio/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_api.php

There were four pages of these. I tried the update twice and both times it failed with the same errors.

Fortunately, reverting back to the old version seems to have worked. I’ve updated the theme previously with no issues.

What’s going on? I need some of the features of the new theme, but can’t afford to risk dealing with poorly developed themes.

Did you also update the included plugins ?

No, I didn’t update the plugins. How?

In the Newsmag documentation it says: Step 5 – Update the plugins. The theme required and recommended plugins are included in the theme package inside the ../Newsmag-tf/plugins folder.

Yes, there’s a plugins folder in the new theme version that I downloaded. So, where are the instructions on how to install those? The instructions state to install the Newsmag zip file. The plugin folder is separate.

Are you absolutely certain that the lack of plugins caused the issue? If so, why doesn’t the documentation explicitly state and show how this is done?

Hi @awtown

If you want to update at the latest version please make sure you do a clean update, meaning that we recommend that you delete the old version of the theme before uploading the new one – https://forum.tagdiv.com/newsmag-how-to-update-the-theme/ update also the plugins that come with the theme files. The update process for each of the plugins included in theme path it’s the same: delete the old version of the plugin then install the new version from same path with the theme. For example if you update at the V 2.3.1, which is the current version available on themeforest, the plugins must be installed from Newsmag-tf\plugins folder which you downloaded from themeforest.
If you’re using child theme deactivate it during the update process, switch to default wp theme and make sure that you also update it from Newsmag-tf\code\Newsmag-child.zip
If you use child theme for files customizations it’s a good practice to check update_log.txt file for each update and see what files had been modified so if those specific files are used in the child theme you will have to check your customizations to not break the functionality of the theme.

Let us know how it goes.
Thanks!

• This reply was modified 10 years by Andrei L..

Your answer is very similar to what the documentation says. I’ve read that and done that.

I’ve performing the update through the wordpress panel.

My question was, how are the plugins installed. I see plugins in the new theme version I downloaded. Your instructions say delete the old version of those plugins and replace it with the new.

Where are the old versions of the plugins? They’re not in the plugins section of the wordpress panel.

Also in your answer, you mention updating the child theme. What? Isn’t the point of having a child theme that it contains the modifications? If you update it the mods will be written over and lost.

You folks make the update process much more difficult than needed compared to other themes.

Please completely read my questions and provide thorough and complete answers.

Your support is usually very good, but it seems to be going downhill.

Hi

Sorry for the inconvenience, we try our best to provide the best quality themes and support.
First please backup the whole current theme installation as well as the database and wp install: https://codex.wordpress.org/WordPress_Backups
Version 1.7.1 which you have it installed: http://screencast.com/t/BUr9CmZE have this plugins included in its path: http://screencast.com/t/tpdW0mTb You need to delete them, also delete the old theme: http://screencast.com/t/xrHoImmmQZ and install the V2.3.1 of the theme. After this step install the new plugins, only Visual Composer is required, install the other ones only if you need them: http://screencast.com/t/bMVnQrywy – http://screencast.com/t/V8j2YSlZt1

The differences between V1.7.1 and the current one are major. Lots of files are changed, lot of code was modified and your customizations from child theme may not work properly with the latest version of the theme.
The point of a child theme is to keep the customization even if the main theme it’s updated. But this is not always valid, because once in a while the child theme it’s also updated, or if the main theme pass through a major update it’s possible that some customizations not work well anymore.
Since V2.0 the include system for css has been changed in child theme: http://screencast.com/t/UKZpoPCiw and using the old child theme instead of the updated one could cause issues with theme’s style. That was the reason why I have mentioned the child theme update.

Let me know how it goes!
Thanks!

Wordpress how to install plugins:
https://codex.wordpress.org/Managing_Plugins

Manual Plugin Installation

There are a few cases when manually installing a WordPress Plugin is appropriate.
◾ If you wish to control the placement and process of installing a WordPress Plugin.
◾ If your server does not permit automatic installation of a WordPress Plugin.
◾ The WordPress Plugin is not in the WordPress Plugins Directory.

Installation of a WordPress Plugin manually requires FTP familiarity and the awareness that you may put your site at risk if you install a WordPress Plugin incompatible with the current version or from an unreliable source.

Backup your site completely before proceeding.

To install a WordPress Plugin manually:
1. Download your WordPress Plugin to your desktop.
2. If downloaded as a zip archive, extract the Plugin folder to your desktop.
3. Read through the “readme” file thoroughly to ensure you follow the installation instructions.
4. With your FTP program, upload the Plugin folder to the wp-content/plugins folder in your WordPress directory online.
5. Go to Plugins screen and find the newly uploaded Plugin in the list.
6. Click Activate to activate it.

There’s been a number of modifications made to the child theme on our site.

So if I read your message correctly, you’re saying that to update to the new version the child theme needs to be replaced and the modifications from the previous version will likely be lost.

Fabulous!

I generally like your theme, but after this wonderful update process, we’ll probably be moving on.

Most themes work this way, so welcome to WordPress.

I’ve been using wordpress for at least 15 years. I’ve never had to write over the top of a theme file and lose modifications. Child themes exist to avoid losing the mods.

There are more excellent themes then ever that are developed to make the administration easy. Who wants to hassle with redoing the mods. It’s a waste of time.

Wow. Must have a great time machine, considering WordPress launched in 2003. You are a grand master of the universe. Based on the ‘How do I install a plugin’ question, I didn’t peg you as an expert as that is a newbie type query. Most folks look into the download folders, know how to FTP, etc.

Child themes are “normally” meant to allow basic mods without touching parent, except when major changes are made to WP core which has happened a lot this year, or if there is major theme upgrade to bring entirely new feature set at which point the child theme also needs to be upgraded.

Most of us using WP the past decade are aware of this.

Not trying to argue about it, but of course lots of themes to choose from. I love this one and we use it for our news network and have no troubles, but then we edit the main theme and never use child themes as they are a redirect of the CSS and you are eventually going to run into the issues you are now.

I’ve used dozens of themes and the child themes often change to address changes to WooCommerce, WP core, security patches, etc. And WordPress 4.4 next month brings additional changes to core.

In any case, I don’t work here — so sorry I posted anything here — didn’t intend to upset you.

It’s all good. Peace! 🙂

• This reply was modified 10 years by simchris.

I can confirm that update to 2.3 and 2.3.1 was absolute nightmare. I get the same errors as @awtown. It is too risky for me to update, and I am staying with 2.2.

I’m pretty novice when it comes to anything remotely complicated on WordPress, but I managed to update to both Newsmag v2.3 and v2.3.1 easily enough.

Yoast SEO was giving me some grief, but that seemed to sort itself out once I updated the theme to v2.3.1.

In this guide, https://forum.tagdiv.com/newsmag-how-to-update-the-theme/, there’s no mention of updating the child theme.

In this thread, first you folks say the child theme needs to be updated. Then, only the code for the theme’s functions needs updated. Then, if we follow your guide for the Update Via WordPress section, the child theme is not mentioned, so it reads like no update is needed of the child theme.

The update process for my site failed. I asked a basic question and got different three answers. Can you clearly and easily answer this?

My comment was not directed at you. It’s a frustration with the update process.

The folks at tagdiv could code the best theme in world, but if it’s not easy to work with they’re sales will decline. I’d prefer they be successful.

I can also agree that updates were easy enough for me to do too. No complications at all. Not saying you are wrong the one that says used WordPress for like 15 years but updating the theme is not that hard. I even used both methods with dashboard and ftp and they work just fine either way. I did not even update the plugins from v2.2 to v2.3 and v2.3.1. Nothing gave me issues. Last two times updating. I just uploaded the folder of new version, overwriting the older via ftp and it works just fine as before, and I am not even using the child theme.

All my modifications are in the custom code section of themepanel. That does just as good as using a child theme to me. This is one of the best and simplest updates with this theme as possible and I had no hiccups yet with it.

I should not say no plugins were updated. Visual Composer was updated every time they gave a new update to the plugin with theme update. I don’t use Revolution Slider because that is one hard to use plugin for just a slider. Way too many options on it. So the only plugin I updated was Visual Composer and I kept the Social Counter the same and still was fine with no errors.

• This reply was modified 10 years by doucare1971.

Just read you last post awtown about child theme being updated but it does not need to be. It is the theme that needs the update, not the child theme. Child theme is the same every theme update. Consists of functions.php and the css file.

If you are using the child theme then do the ftp overwriting the old theme with newer version way. You don’t have to delete the theme at all just unzip the new folder package and unzip theme folder and make sure you just upload the unzipped folder of the name with all the files of theme right over the older one on your server. It will just overwrite what is on your server.

Really, it is that easy. You don’t even have to deactivate the child theme this way either.