I just came here to ask the same thing. Thanks for jumping on it!

Agree completely with simchris. It’s like with the Newspaper theme now. Whenever they do a big update, you’re better off waiting for the next two or three bugfixes before updating as they always seem to be buggy now.

Or maybe they could just fix this in the theme hopefully!

we wound up getting rid of WPBakery with the 7.5 update and recreated homepage with TagDiv and have had no problems. I really liked WPBakery also, but I could tell that they were doing their own and we had to move with it.

I have the ‘Show Comment Count’ turned off on the Meta Block in the Theme Panel but it continues showing up on individual Authors Pages

https://movietvtechgeeks.com/author/jeffrey-lang/

It lists the posts they’ve created and next to that comment count. I am just trying to find out how to get rid of the comment count box.

Thank you.

Hi Catalin,

I have looked all over on the Theme Panel but there is no place to disable black square box that has the comment count. I have checked in the module boxes and anywhere we can think, but oddly this doesn’t seem to be an option.

Is it something that needs to be done with CSS code?

Thanks!

Great idea and I thought Newspaper already had this unless it changed with the latest updates. We still are holding off with 8.6 after all the issues.

they put a newspaper plugin with this update to solve that issue.

Hey Alastair,

It’s actually a really great theme (I’ve had it for four years now) and worth sticking through this update mess they’ve got.

They’re making some great changes, but it just got a little ahead of itself. They’ve said that they’re next update will fix all the problems we’ve all had the past few weeks with 8.7 and 8.7.1

they’ve been saying now to wait until the next update next week before updating.

That is just way to many steps to upgrade a theme, especially one that we’ve paid for. I’ve never had a problem with Newspaper updates before in over 4 years so I’ve been patient with this mess, but they really need to beta test the heck of the next one before I just update like I normally did.

Hey @rashburn

Sadly, I’ve gotten very generic responses from support via email and they keep blaming the buyers of this plugin. Hard to believe that after an update and so many customers have the same issue that the company would say it’s the paying customers fault.

They have done two updates since February 14, 2018 but they are not listed in the Changelog and I can’t get anyone to say what those changes actually were. Very frustrating for those of us that have been paying for support for over 4 years now and when we need it, it’s proving to be worthless.

as we have 33 writers around the world (literally) having them undo their PC protection seems to only be asking for problems for the website. wouldn’t it be best to have an update to deal with this issue since this latest update to Newspaper has sparked the problem in the first place?

I’m a little frustrated as a very long time user and buyer for your support service that with this update, I keep hearing that the problem seems to lie with your customers when the 8.7 update has caused the problem. Seems like a horrible way to do customer service.

You all have done two updates (as denoted in the last update section on the Newspaper) but they are not listed in the Change Log).

The latest update is marked for February 20, 2018 and I was wondering if you can let us know what the latest two updates included. I appreciate you all working on this too as it’s the first problematic update I’ve encountered since using your Newspaper them for several years now. It’s just after having our site being knocked out for 12 hours (and we have 33 writers working full-time for us) we a little nervous about going through the process again. Many other users are feeling the same way so you can understand why we’re not so ready to just try the update all over again.

Thank you.

@epickenyan I’m surprised at how the support team has been handling this as there have been multiple issues (including site speed) being caused by the update but support keeps telling paying customers to do the work. Seems they would go back to the update and make tweaks as this is the real cause of the problem.

I was using Visual Composer (WP Bakery) as it came with Newspaper but we created a page from TagDiv and will try during quiet time of weekend to try another update to see if that makes any change. We learned from last week to do full backup so if problem hits again, we’ve got it covered.

We’ve done all the steps you and others have mentioned to no avail so maybe creating fresh pages will do something, but at this point, anything is possible.

One would think that when the developers of a theme are shown that their update is slowing down users sites, they would work on coding of the update to fix this rather than tell the paying customers they need to make tweaks themselves.

The Newspaper support team is really handling this update TD Composer mess badly and doing more work to lose customers than keep them.

Sadly, the support team we’re paying for told me that there’s no issues at all with TD Composer or the upgrade and it’s all of our problem.

After using this theme for so many years and paying for support all that time, I was really frustrated that when you actually do need to use the support it blames you rather than the product.

thank you epickenyan for letting the PHP 7.2 problem be known. this is the first time in many years I’ve seen so many people have the exact same issue with this theme so I knew it had to be something with the update.

Support basically let me know it was my issue since most people weren’t having any issues with 8.7 but our site also runs PHP 7.2 and seeing it might the culprit at least gives some relieve on figuring this issue out.

I’m a little surprised that when you’re paying for support, they can be rather short with helping you out.

hey Kwacha,

I sent an e-mail to customer support at tagDiv so we’ll see if they’re able to fix this.

I’m having our hosting provider revert our site back to yesterday as I’ve tried going back to version 8.6 but the problem stayed. I’ve spent hours trying all the things everyone on here has mentioned but nothing has worked.

This is the first time in all the years I’ve had Newspaper that an issue cropped up so I’m sure they’re working on a fix. It seems like the new update is having trouble linking to our static homepage we created. All the other articles on our site look like they usually do, just the homepage issue only showing the menu bar on top remains.

Luckily this is the first time something this major has happened with Newspaper and I’ve had it for several years now. Hopefully, they’ll figure it out.

Mainly it seems that for those having issues with homepage not showing, it’s not seeming to connect to our static homepages. I even created a new page with same settings hoping that might trigger something, but same result which shows me that it’s just a coding glitch in 8.7. I’m having our hosting provider revert our site back to yesterday.

Of course the one time I didn’t back things up before doing an upgrade there was a glitch:)

I tried reverting back to 8.6 but that didn’t fix the problem so having our hosting service revert back to yesterday. Such fun since we’re a live news site!

It seems like the 8.7 version is no longer able to connect to the static homepage. I originally created our homepage with that WP Bakery plugin that came with Newspaper and that always worked great through 8.6.

I tried creating a new page with TagDiv and it gave the error message :
Errors happened during tdcIframeData.init() -> bindViewsModelsWrappers()!

And it won’t let me do anything to create a new page. Very odd as the rest of the site looks the way it should which leads me to wonder if there’s just a small glitch to connect static homepage.

Most of these errors are just small glitches that cause a big pain.

what’s weird is that it doesn’t seem like it’s able to connect our static page homepage with 8.7 no matter what tweaks you try. with this many issues, they’ve gotta be working on a solution as it’s pretty common now with this update.