Hello!
This morning I’ve noticed something very strange on our site: http://www.n3rdabl3.co.uk. All of the featured images within posts have disappeared as if I’ve turned the “Featured Image” option off in the theme settings, something which I have not done.
I’ve tried a number of things, from deactivating the Featured Image option and activating it again, changing the Featured Image layout, and more. Oddly, videos still appear as normal. It’s a very odd occurrence which I’m completely baffled about.
Any help on this situation would be appreciated!
Hi
Try to deactivate all plugins except Visual Composer, clear all caches, browser cache too, make sure that the Show Featured Image is enabled: http://screencast.com/t/txJm270T8M5 and test again.
Let us know how it goes and if the problem persist please send us an email at contact@tagdiv.com with your login credentials and we will inspect this issue as soon as possible, also include a link to this topic.
Thanks!
Okay,
I forgot to mention that I’m currently using the Child Theme (as we’ve added a few customisations to the footer and functions.php)! I activated the main theme and found that the Featured Images have returned. I also discovered that deactivating all of the plugins (but Visualiser) caused the site to white-screen, so we’re looking into that at the moment.
It seems it’s entirely likely that some code we added to the Child Theme files have conflicted with the Featured Image. We’ll do some digging and update the post accordingly. Alternatively, I could send over the Child Theme files (via the email address you provided) to discuss things in more detail?
To quickly add to the above:
I received the white-screen when deactivating all of the plugins while the Child Theme was active, not the main theme. The main theme saw no issues when I deactivated all plugins.
Final update:
Good news. I’ve fixed the problem.
It seems the new version of Newsmag has an updated td_module_single_base.php which is different to the one I’ve been using in the Child Theme. The reason I have that file in the child theme is because I followed this tutorial to hide the ads on a per-post basis:
https://forum.tagdiv.com/topic/function-to-hide-ads-and-function-to-show-author/
I have since copied the updated td_module_single_base.php and re-applied the above code found in the tutorial and things are back to normal.
I understand that this may be a totally incorrect use of the Child Theme, but it works! If you have any advice on how to better implement these changes then please let me know: aaron@n3rdabl3.co.uk
Sorry to butt in, but in my experience this is exactly why I don’t use child themes as they may change over time with major updates and kind of defeats the purpose.
You might consider modifying the “main” theme for customizations, and simply keep track of the files/folder and ‘snippets’ (e.g., line xxx, block of code) in text files, so you can replicate that after an update.
This is what I do, and proves more “consistent” and limits site failure and debugging due to the main/child being out of sync.
With all the functional changes to WP of the past year, this has proven to be even more true.
Sorry, editorial over 🙂
Hey Chris,
Don’t apologise for butting in. This is personally my first experience with Child Themes as usually I’d edit the “main” theme as it were, but times before I’d tweaked so much, updates usually broke the site, leaving me to either revert to a previous version, or just to refuse to update the theme entirely.
I may consider your approach as I’ve barely touched this theme due to its many customisation options.
Thanks!
🙂
I usually have to hack couple things for header, author template (remove comment count), 404 template, remove remote loading google fonts, add some stuff to functions.php, and minify the CSS, and make one change the default hit counter field to match our pre-existing field name “views” — so not too hideous; most of the rest is done with CSS.
In our case, just safer to get update, make mods to update work folder; then upload that to replace old version; check all works; if not roll back.
Fairly safe way to live without “hoping” updates will work (color me paranoid!) 🙂
Hi
@azzronulation glad you could manage to solve the issue, but is important to note a few mentions about this. Moving the td_module_single_base.php it’s not incorrect because it’s supported by the theme, you can check the files that can be moved in child theme in our documentation: https://forum.tagdiv.com/the-child-theme-support-tutorial/ However when the theme is updated, many of its files are modified and there is a chance to appear some conflicts with customizations from child theme. That’s why you need to check at every theme update if your customization are compatible with the new theme version, and eventually adjust them properly.
Thanks!
Hello,
Ah, that’s fantastic to hear.
As I mentioned above, I’m new to Child Themes, so from now on I’ll be sure to keep an eye on compatibility with any new updates.
Thank you for your support.
