Thanks Vlad, I’ve sent an email as requested.
Thanks Calin. That would be perfect, except we use both percentage and points for different types of reviews, and I only want it for percentages.
No worries, I appreciate that this is all beyond the theme’s feature set, so I can leave it as it is now. I do hope that some of these solutions can be incorporated into future versions of Newspaper as it considerably improves the review capabilities.
Many thanks,
stuart
Thanks for your help @Calin, that’s working really nicely and looks really good.
One last question, and it may not be possible, but if I am using a percentage score for reviews, how can I display % after the score?
Currently it just shows the number (eg – 90), and I’d ideally like it to show 90%.
Many thanks,
stuart
We created a post template using TD composer. The Euro NCAP rating, Green NCAP rating and review sections all use a custom plugin we commissioned, which pull their data from a custom database.
That is our development site; this is where we have the aggregated reviews on our public site: https://www.thecarexpert.co.uk/new-car-ratings/
Hi decovca, thanks for your help.
I have added that code, and it now displays numbers from 0-5 instead of stars. See here: http://compareallvans.co.uk/reviews/
However, what I would like is for the original scoring system in the review to be used (we use either points out of 10 or a percentage) rather than converting it to a five-star rating (or a number out of 5, which is basically the same thing).
We score our own reviews out of 10 and we use a percentage score for aggregated reviews, and I would like the blocks to reflect the original format used instead of converting them to a format we don’t use.
Hi Calin,
That CSS looks fantastic, but it still leaves the scores in a star format rather than points or percentages. Please see here:
http://compareallvans.co.uk/reviews/
Is there a way to have this set so that it follows the scoring format used by the post? This would also be helpful across the theme’s post blocks and schema markup, so hopefully it’s something that can be included in a future update.
Many thanks for your time, as always.
stuart
Thanks @mercurial. I had the Facebook Pixel component of WP Rocket active, but deactivating that hasn’t fixed the problem.
Thanks @Calin. I sent an email late yesterday with the details, so I’d appreciate you guys having a look.
Hi Calin. Is there any additional information on resolving this information? I’ve been having the same issues since the last update – can’t even download a blank cloud template without getting the above error, let alone edit existing templates.
I have disabled pretty much every plugin to try and resolve this, but have had no luck so far.
Thanks,
stuart
Thanks Calin. I did see that thread yesterday and tried it on our sandbox site, but it doesn’t give the sort of results we’re looking for (score is still based on a total of 5, rather than a score out of 10 or a percentage, and doesn’t style very nicely).
I appreciate that this is beyond the capabilities of the theme’s review functions at present, so I’m happy to work with a plugin to try and achieve the desired result for our needs. Was just hoping that either someone from tagDiv or someone else on the forum knew what that particular site was doing to achieve its review scores.
Thanks,
stuart
Hi Catalin. That’s fine, was just hoping you knew of a quick way to add some custom CSS to achieve it without having to go to a developer.
Many thanks,
stuart
Hi Catalin. I regenerated the critical path CSS (in WP Rocket) and that seems to have solved that problem.
Many thanks,
stuart
Thanks Catalin. The advertiser has now supplied the ad units as .png files, so it’s now working.
What I’m now finding is that the site momentarily displays all four ad units (desktop, tablet landscape, tablet portrait and mobile) before the correct one is selected and the other three are hidden.
Any suggestions on how I can fix this?
Site is https://www.thecarexpert.co.uk and the ads in question are in the header ad unit.
Thanks Catalin. That worked for about half a second then caused a white screen of death. I also need to be able to insert different ad code for different screens (desktop/tablet/mobile).
I’ve bounced it back to the advertiser to see if they can provide banners as .jpg or .gif files.
Thanks.
stuart
Ah, many thanks Simion. I hadn’t realised that this site hadn’t been updated to the latest version (we have four sites running Newspaper and usually I make sure they are all updated as soon as a new version is released!).
Best wishes,
stuart
Hi Simion and team,
Sorry for the delay in replying on this; got overtaken by other jobs.
The shortcodes were entered using the TD Composer in text elements.
If I go into the regular backend WordPress page edit screen and replace the bbPress shortcode with regular plain text, the error message disappears and TD Composer works as normal.
If I add the shortcodes via the WordPress page edit screen, it will display correctly to visitors but it breaks the TD Composer when I want to use it to edit the page.
If I build a new page using TD Composer, I can add the shortcodes and save the page as normal, but if I exit the composer and then try to open it again, I get the red error message.
Hope that helps,
stuart
We get similar errors from time to time when building pages in tagDiv composer. Usually, but not always, it’s a shortcode from a plugin or something similar.
We’re currently seeing it a lot on pages with bbPress shortcodes, so probably worth checking that. Once we delete all the bbPress code from that section of the page (you have to look for it on ‘edit page’ rather than via the composer), it solves the problem.
Hope this helps, or at least helps to narrow down the source of the problem.
Many thanks Simion.
With regards to No.1, it may have something in how we set it originally for that image, since we copied the same layout across multiple sites. It’s an easy fix, but I left it as it was on that site to show what I meant.
Thanks for the tip on No. 2. That has fixed the problem perfectly, and everything is now aligned properly once again!
Cheers,
stuart
Thanks for your help Simion. Overall, we’re really happy with the theme and the work all you guys have done. The level of customisation we have been able to create right out of the box is brilliant, so it’s really just tweaking some details.
Cheers,
stuart
Yes, that seems to have done the trick across all of our existing content as well, so hopefully that will help reduce load times.
The problem with this is that we’ve had to disable our retina images, which is not ideal for viewers with retina screens. Is this something that can be fixed for a future update?
It would also be really helpful to be able to use smaller image sizes than 696px as well. As you can see on our site, all of our thumbnails are in a 2:1 or 3:2 format, so the 324x400px option doesn’t work for us at all. A lot of our thumbnail sizes are quite small, so it would be better to be able to have something like a 300x200px or 200x100px resolution as it would make the thumbnail file sizes much smaller.
Can you please pass this on to the dev team to add to their list of future feature requests?
Many thanks.
Hi Simion,
Thanks for your reply. I think we are getting somewhere.
The image width you mentioned of 1392px is double 696px, so presumably it’s pulling the retina version of the 696px thumbnails.
We use the Imagify image optimisation plugin, as owned/recommended by WP Rocket. It optimises for all thumbnail sizes used by the theme. I disabled the plugin then built a new page and created eight new posts to test, so it wouldn’t pull any old images. Link here, with one flex block to pull 696px images and one set for 324x400px images:
https://www.thecarexpert.co.uk/image-compression-testing/
Made no difference, was still pulling the 1392px and 648px (retina) images. Disabled all my other plugins apart from tagDiv ones and core plugins like bbPress, still no difference.
Went to the theme panel and deselected all the retina versions of the thumbnails, and presto! It now pulls the 696px and 324px images instead of the 1392px and 648px versions.
So it appears that the tagDiv theme panel settings are causing the flex block to pull the retina images rather than the originals, rather than a plugin.
Thanks Chris. And thanks for all the advice and tips you’ve provided here over the years, I’m always finding new tidbits of knowledge from your contributions.
Update on this: We seem to have found some success using a very old plugin from the WordPress repository:
http://kaloyan.info/blog/proekti/wordpress-proekti/wp-utf8-sanitize-plugin/
So far, so good. But I’m not sure if it’s the best long-term solution.
I have the same issue – assumed that there was a conflict somewhere. Can you please post the solution if you find one?
Oops, ignore me. The 9.0.1 update deactivated the tagDiv composer…
Hi Simion,
I updated to version 9.0 with no problems, however 9.0.1 has caused widespread errors with all pages and posts created on tagDiv composer (pages) and cloud templates (posts).
stuart
