If you set the background image the theme should switch to a “boxed” version.

I don’t understand. Are you saying that 768×512 is generated by the theme and can be removed by a third-party plugin (mentioned in that topic), or that it is not generated by the theme?

Because, as I said, it’s not listed in the Theme Panel and as there are no other plugins running and WP default thumbnails disabled I don’t know what’s creating it.

Sorry for bringing the topic back from the dead, but I just ran into this problem again.

Very specifically: How can I tell the Slide module (not Revslider) to use the original size image and not the predefined 1068×580 thumbnail?

Can this be done with API or should I edit line 39 of td_module_slide.php?

What to put there instead of

$this->get_image('td_1068x580', true);

?

Could be something else, but tonight I solved several problems that started happening after TD Composer update by increasing server resources. Try raising max_input_vars and WP_MEMORY_LIMIT and see if that helps. Worked for me.

Open your homepage in admin and look for a panel called “Page Template Settings”.

Maybe not related to your issue but tonight I solved a major headache with TD Composer update and various weird stuff that started happening. It turned out that server resources that were enough before are not enough anymore. Probably not much of a difference, but still. I cranked up max_input_vars and WP_MEMORY_LIMIT and that did it.

Do you have Unique Articles enabled? Then it wouldn’t show again because it’s already shown in a previous block.

As it normally happens I figured it out minutes after posting here… but here goes for those that may stumble the same way.

It seems that server resources that were fine for earlier version of TD Composer are not enough for the new one. My minimal configuration (as it is a test site) has had no problems until now.

If you update TD Composer and it starts acting up, give it a little more room to breathe if you can. Specifically, I’ve increased max_input_vars and WP memory limit. Don’t know which one fixed it.

Sorry for troubling you guys.

I understand.

While we’re at it, is there a way to force a single module/block to use a different thumbnail? I mean, there is a size that I only need in a single block on a single page. It seems vastly unnecessary to have all images practically duplicated just because of that single block. I would rather overwrite it, even if I had to mess with the theme’s source code.

Wait a minute. So if we turn the thumbnail off in Theme Panel and also turn off the option to display “placeholder” images, the blocks will load full-size images as thumbnails?

From the docs:

“There are 3 ways a block can show content:

On a full width row, on a 2/3 row, and on a 1/3 row.”

Sorry – have you modified the width of the block? Block 14 normally isn’t that wide and the thumbnail width looks normal for its default width. You would need to “stretch” the featured image with CSS as well or force the block to use different size thumbnails, but you’d have to mess with the theme for that.

Block 14 uses 356×220 thumbnails.

That’s a good one. The theme should not create another thumbnail if the original image is already of sufficient size. I’ve ran into the same problem with Slider – even though I upload the image as 1068xSomething, the theme still creates another one.

Any solution, tagDiv? Perhaps we could bypass the thumbnail for that one module somehow?

This would happen if the images were too small. Check their size. The blocks don’t stretch them.

Make sure you have a 2/3 – 1/3 layout on the row and don’t forget to add the extra class. Add it to the row, not the element itself.

Thank you Simion!

I have added it to header.php file.

But I’m wondering would it work if I add it to the “Analytics” field in Theme Panel?

If I remember correctly, TD Speed Booster won’t activate due to incompatibility with AdRotate. That’s why I said it’s “unsupported”.

But yes, if anyone has managed to get those two (AdRotate & Super Cache) to play nicely I’d love to hear it.

I don’t know about your installation, but on mine it seems that WPBakery Page Builder (formerly Visual Composer) started hogging more server resources than in the previous version. It worked okay and now, after the update, its queries are sometimes insane. I probably won’t look deeper into it as I’ll eventually ditch it for TD Composer as recommended.

When editing, before you hit the “update” button, reload the post (frontend) in another tab and note the view count. Then enter that number in “post_views_count” custom field and it will be saved.

That should prevent the number from dropping.

But there is a custom field “post_views_count”. Sometimes, intermittently, it’s as if this field does not update properly when the post is updated – as if it resets to some previous value. A “hack” would be to note the views count before updating post and then entering the value into this field.

It’s not a life-or-death thing, of course, just a nuisance.

I have the same issue sometimes and that’s not the cause. I also have WP Super Cache installed and ajax-enabled counter.

In my case, post views count rarely goes back to zero, but it definitely does drop when the post is updated some time later.

The problem is particularly obvious when I keep the post open in admin after publishing it. If I leave and then come back to edit it, less views will drop. Maybe that’s a hint.

Thanks. This is just a rough first try, a patch until something more elegant comes along.

I’ll keep messing with it.

OK, I have managed to come up with something. I noticed that the AdSense script set “display: none” for itself, so I figured that the problem might be with AdSense after all.

Then I modified the responsive unit’s code by specifying expandable width and min-height, per instructions described here: https://support.google.com/adsense/answer/6307124

And it worked!

I’ll keep looking into this to see if it works everywhere and in all situations, but it’s a decent first step for now.

NOTE: I used the following settings for the header ad:

style="display:block;min-width:320px;max-width:768px;width:100%;min-height:90px"

You’ll of course probably want to modify the numbers for your needs. Fiddle around with it.

Non-AdSense ads are displayed properly. When no ad is shown, AdRotate tries to display the AdSense responsive unit, but fails every time. It’s the same for any other ad location on the site. Fixed-size AdSense works fine. Responsive AdSense units work only if they’re not in groups.

I have tried placing separate AdSense units for desktop and mobile in the same group, but that doesn’t work either. I believe there’s something in the code that blocks them from rendering even though they are properly loaded in the source, but can’t figure out what it is.