We are also experiencing these WP Booster Errors. A lot of them. We recently updated the theme so it may be related to that. I Googled the issue and saw that the recommendation was to update the template settings but the Theme Options panel doesn’t load (or rather loads blank). Are there modifications we can set via the database to remedy this? The site is generating about 20 errors like those below.
This is for a client’s site, so rather urgent. If we could hear back ASAP that would be great!
Thanks!
Paula
wp booster error:
td_api_base::mark_used_on_page : a component with the ID: td_block_1 is not set.
wp booster error:
td_api_base::mark_used_on_page : a component with the ID: td_block_2 is not set.
wp booster error:
td_api_base::mark_used_on_page : a component with the ID: td_block_3 is not set.
wp booster error:
td_api_base::mark_used_on_page : a component with the ID: td_block_4 is not set.
Hi
Make sure that you have updated the theme according with our documentation: https://forum.tagdiv.com/newsmag-how-to-update-the-theme/ also try to deactivate all plugins except Visual Composer, deactivate the child theme if you’re using, clear all caches then test again.
If you still can’t manage to solve this provide your site url so I can have a closer look.
Thanks!
Hi Andrei,
We will try to reinstall according to the documentation in case there is something we missed. However, we have some technical resources. So is there a way to set those templates via the backend? In case reinstalling doesn’t help, we’d like to be able to fix this ASAP instead of waiting another cycle to get support feedback.
Thanks,
Paula
Hi
The theme is tested and shouldn’t be any issues with its functionality if the install was made correct and there is no additional code which may affect it. Usually these errors appear when the child theme is active and there is some code which does not work anymore with new theme’s version.
Regarding the code from child theme there is an important aspects that must be considered if you’re using it:
– if in previous theme’s version a specific code added in child theme worked fine that doesn’t mean that will work with the new theme version. When theme is updated many of its files are changed and 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.
Hope this help.
Thanks!
