Hello,
just updated from 9.74 to 9.8 without problems and deleted loop-single and single files in child-theme folder.
Everything works as expected and error is fixed. Thank you!

Hello Simion,
has this bug been fixed in 9.8? Can those two files be deleted in the child-folder?

This has still not been fixed in Version 9.7.4. Please fix this with next version!

Hello Simion,
for me this solution worked.
But coping those files is just a hotfix for me.
When will this error be fixed, so I can delete those two files?
I can see it coming that with one of the next updates, these files may cause problems and the support-answer will be, that there are two files in the childtheme directory, that shouldn’t be there 😉

Hello Vlad,

yes, with these two files I’m able to switch back to the default layout. Thank you!

But I hope, that this is not the final fix for this problem, because I don’t want to have too many files in my child theme to keep it as most upgrade save as possible.

• This reply was modified 7 years by be2name.

Hello Vlad,
right now switching to Style 2 is only a very hot hotfix for this bug, because Style 2 is NOT the same as default. The Headline in Style 2 runs over the whole width, while in default it only is above the content area on the left.
Good you were able to recreate the bug, so hopefully you will be able to offer a fix for that error today.

I also did a manual update now. Nothing changed and the error still exists, no matter if I use my own child-theme or the one provided with the theme. The error does not occur when using standard Newspaper theme. So there is definitely a bug in 9.7.4 with child-theme.

@Jaddy1219 and @Vlad-S Please let me know, when you found the reason for this and how to fix it.

Hello Vlad,
I haven’t deleted anything manually but used the automatic WordPress/envato market/tagdiv update functions. So does the automatic update not work? Do I have to delete everything manually and install it again? I’m not sure, if this will really fix that issue.

• This reply was modified 7 years by be2name.
• This reply was modified 7 years by be2name.

You could downgrade to 9.7.3 if you have a copy of it.
Otherwise you have to wait until tagDiv is fixing this bug. I hope they will fix this soon.

Yes, this is a bug in 9.7.4.
When using a child-theme, the default post template is not applied.
Should be fixed urgently!

Yes, this is a bug in 9.7.4.
When using a child-theme, the default post template is not applied.
Should be fixed urgently!
Had to downgrade to 9.7.3 (which does have the bug, that individual templates can’t be applied when using a child theme).
So both versions (9.7.3 and 9.7.4) a buggy when using child themes.

Yes, this is a bug in 9.7.4.
When using a child-theme, the default post template is not applied.
Should be fixed urgently!

Same here! No sidebar, no related posts etc. Default post template completely messed up.

Thank you, Calin!
I now was able to change the title. I used the filter
add_filter( 'pre_get_document_title', 'custom_title_function' , 50);
but it still didn’t work. The reason was Yoast SEO, which has a stronger impact on the title, but it has it’s own filter, so I additionally used:
add_filter('wpseo_title', 'custom_title_function');
This finally worked!

Hi Calin,
ideally I don’t want to change template-files to make them update-save. So I thought I can manipulate the titles with a function in functions.php. I tried something like:

function custom_title($title_parts) {
if (in_category('categoryname') && is_single()) {
$title_parts['title'] = some code here ...
}
return $title_parts;
}
add_filter( 'document_title_parts', 'custom_title' );

But this seems to have no effect on the title.

Yes @momoko,
with the normal Newspaper theme the problem will not occur. According to tagDiv with 9.7.3 only styles.css and functions.php will work for child themes, which is quite ridiculous because normally you use a child theme for different kind of header-files etc. tagDiv says this is because of the new Envato rules, but a theme without the use of a child theme does not make sense in WordPress.
Due to the fact, that the update and the fix of this really bad bug lasts that long, I hope, that tagDiv is able to bring back a better support for child themes. As you can see in the forum, a lot of people use a child theme for Newspaper and it’s very bad that 9.7.3 just canceled the support for child themes without a warning.
So let’s keep our fingers crossed, tagDiv is able to fix this and support a wider use of child themes.

Hello @momoko
a well known (and severe) bug in 9.7.3 especially when using a child theme. Although it exists now since about a month, tagDiv still has no release date for a fix or update.
See https://forum.tagdiv.com/topic/bug-in-9-7-3-child-theme-does-not-use-custom-single-templates/

@Calin
Another week is gone and there is still no fox for this really severe problem. Please fix it as soon as possible. Since one month most of our posts und pages look not as they should.

@auscanoe

I do have this problem, too. Could you fix it?

It’s been two weeks now, since 9.7.3 has been released with the severe error, that single templates can’t be used with child themes. A fix was announced “as soon as possible”, but there is still no update or fix for that really bad bug. Any news here? It’s extremely urgent to be able to use templates again!

Hi Simion C.,
good to hear, that the child theme/template issue is under investigation. I hope this error will soon be fixed.
I do use a cloud template, but I think this (wrong) message does appear because of the template bug.

Thank you, Calin,
maybe this was a bug in the official AMP plugin. Today came an update of this plugin and shortcodes are working now.

It’s in
/wp-content/plugins/td-composer/legacy/common/wp_booster

I did this already (without that change the whole website is messed up), but this is no solution for the problem. As I told you: the problem appears even with the default child-theme. It must be a general problem.

@Beni

I don’t think so. On our installation the composer works as expected. I can even edit a single template, if I select the template via the composer. But when I click on “Edit template” on the admin bar of a post, that should be displayed based on that same single template, I get the message

Please select tagDiv Builder Template from the theme panel or set a default template. The current page/post uses a template that is not editable.

So with version 9.7.3 somehow the connection/integration with a child theme and the composer and it’s templates is somehow broken. The post is displayed in the standard layout and not with the single template it is connected with in the post settings.