Works perfectly – thanks!

Hi Bogdan – thanks for this. Here is an example post: https://www.deeperblue.com/win-deepblu-goodies-celebrate-world-wildlife-conservation-day/

Cheers!

Sadly after a week of testing and trying to get it to work I just couldn’t get it to display properly. Theme sorting doesn’t work effectively with caching involved so i’m going to have to think of a different option.

Thanks,

Stephan

Also – we have tested by de-activating all plugins except TagDiv ones and the multi-purpose options don’t appear in the TD Composer.

Bogdan – thanks.

I can confirm there are no other settings changed apart from Limit Post Number. All other options are set to default.

This seems very intermittent to be honest, some hours it shows all 5, other times it shows only 4.

Thanks Bogdan – i’ll do this when I can as it’s a high traffic production site. I’ll update here when I have more info.

I’ll do some testing. Weirdly it only causes an issue if we create a new row. If we embed it in an existing row it works fine.

We have used WP Rocket on http://www.deeperblue.com for several years now with no issue.

Bogdan – did you guys ever agree on implementing this? Would be awesome to understand what is on the roadmap (and perhaps help provide input).

Many thanks,

Stephan Whelan
Founder
DeeperBlue.com

Bogdan – thanks for this.

Has the large image size width change over time in the theme? I’m convinced it used to be 700 pixels (and cover the width of the content area) in the past.

Is there any way of controlling the size of the thumbs?

Thanks!

Hi Catalin – yes you are right i’m talking about the size of images that can be added in the WYSIWYG editor. I’m only concerned about the width of images not the height (that i’d expect to be proportional).

At the moment you can see the LARGE image is set to 700px wide: http://take.ms/BUKHw

However when trying to add an image in the WYSIWYG editor it is set to 640… all LARGE images are set to 640 which is strange: http://take.ms/bJWsR

Andrei – I understand – the difficulty is the Mobiloud powers a mobile APP yet we still get a large amount of mobile traffic directly to the website so BOTH solutions need to work 🙂

I’ve asked the Mobiloud developers to take a look but it would be great if they could talk directly to you guys to try and understand where the issue is and how it could be fixed.

Thanks.

You can setup AMP easily with the official AMP plugin. Yoast has created a simple guide to follow:

https://yoast.com/setting-up-wordpress-for-amp-accelerated-mobile-pages/
https://yoast.com/wordpress-amp-part-ii/

It’s very simple to do and AMP url’s work with this theme easily.

Catalin – I understand and appreciate your position but equally Jetpack is the most popular wordpress plugin available so you should at least attempt to test and work with it. The reason we use the related content module is that the one that comes with Newspaper just isn’t up to scratch – it is a very basic version and we need some intelligence in displaying related content from our 5,000+ posts.

Something in 7.2 broke as it was working perfectly up till now.

I’m also not sure what you mean by “If you want to display more levels in our theme and you are not aware of the steps in this regard, please consider hiring a freelancer/developer to help you!” as this is a compatibility issue between your theme and Jetpack not a customization issue.

Thanks! We’ve tested each plugin separately and it is the Jetpack plugin causing the issue. Specifically it’s the Related Content bit of Jetpack that is causing the issue. We have de-activated that for now but what do you think causes this clash with Jetpack and how to we fix it?

Thanks,

Stephan

Sadly that’s not really a fix – just a temporary work-around. What you are essentially doing is by-passing all caching on those two CSS files and that will give a performance impact. Till the tagdiv team actually test and ensure that the theme works with WP Rocket this will only every be a workaround.

Bogdan – are there any plans to test WP Rocket – it is a major caching plugin and i’m sure used by many sites. I know you’ll say speak to the WP Rocket team and I will be but until we can confirm it starts working with WP Rocket we won’t be upgrading.

Is there any official way to make suggestions for features or plugins to be tested?

egypiana – the issue is likely with WP Rocket – suggest you raise a ticket with them as well as follow up with Tagdiv team.

Yoast did a good tutorial on AMP along with some of the key plugins helping you get started: https://yoast.com/setting-up-wordpress-for-amp-accelerated-mobile-pages/

Bryson – thanks for that. Question though if you stop heartbeat from working apart from the backend doesn’t it break the post and comment count functionality?

Interestingly after disabling “Show Post View Count” it disabled that on the backend admin interface as well. Is this functionality binary (i.e. it is either on or off?) – wouldn’t it make sense to continue to log number of post views in the backend even if you decide not to show it off on the frontend?

With 6.3.1 has the line number changed for this code fix?

Actually re-did the code and it works.

Still believe this should be in the core code though 🙂

BTW – just installed 6.3.1 and this isn’t fixed in the core code. When I apply the changes as described above it kills my footer – please advise changed code so we can fix this again and also suggest you fix this in the core code release as well?

Thanks,

Stephan

@Radu – thanks for the response and looking forward to seeing the documentation in due course.

As a point to note we’ve done quite a bit of testing on Rocket Loader the last few days and it’s pretty hard to get it to play well with a lot of different plugins, themes and other software (for example forum software such as Xenforo or vBulletin).