Search Results for 'td composer'

Hi Bettina,

You currently can reproduce the problem when opening these two different pages directly from the Google SERPs, at least I can with incognito mode:

– https://tinyurl.com/4u83xw2r
– https://tinyurl.com/mpmtevue

I have attached two new full page screenshots for you for these two pages:

https://1drv.ms/i/s!AlQHsqtJGzeatY9lkO8LPT26n-sodg?e=wLnhz8
https://1drv.ms/i/s!AlQHsqtJGzeatY9mSXcAdYX9FRN83A?e=zaUWMr

Here is the tagdiv composer view for our posts template:
https://1drv.ms/i/s!AlQHsqtJGzeatY9kLtq2PHDsn4wmrQ?e=KE6lXv

The issue seems to be somewhat related to how “Googlebot smartphone” renders the pages and then stored some data which is now being used when users click on the Google SERPs.

This means the issue appears only for some pages when users come from Google, as some cached version or parts of the code (that had been served on a previous crawl) is being applied

If the user then reloads the affected page the problem disappears. All visits/loads that are not coming from Google appear to render the pages correctly – including from Bing SERPs

My assumption as of now is that some dynamically served image (container/element) code to “Googlebot Smartphone” sometimes produces a flawed cache result – which then affects desktop users when they visit the site from Google SERPs.

In the meanwhile I did some tests with the previously reported page:

– Doing a minor change on the affected article
– Reducing the featured image dimensions and saving the page
– Re-indexing it again manually via Google Search Console.

This removed the problem. But this could be just a random success as in general not all pages are affected.

Further changes I have implemented in an effort to fix things:

I added this custom CSS code to my wordpress theme to force a limit for maximum image size rendering on mobile devices, to target Googlebot smartphone which seems to have some rendering issues with the code it gets:

@media (max-width: 767px) { .tdb_single_featured_image img { width: 100% !important; max-width: 696px !important; height: auto !important; } }

In WordPress you can edit posts with td-composer, or the default gutenberg editor, and if you have the classic editor pluging installed, you can still use the old classic editor from old wordpress (what we do here).

When you go to edit a post, there are little links below the post in the posts menu, to choose how to edit.
(I don’t work here.)

Hi Bettina,
thanks for your respond.
hope these 3 images will illustrate what is not working and help to find a solution or fix.
I expect to see something like in this example from tagDiv:
https://cloud.tagdiv.com/category/podcasts/

Instead I see this and don’t find a way to fix it.
Showing within Edit TD Composer the element subcategories:
https://freeimage.host/i/3H22YhB

here you can see that the category has subcategories and individual subcategory image:
https://freeimage.host/i/3H227IV

this screenshot is prove that a subcategory has its own image and is displayed a sub-category template correct:
https://freeimage.host/i/3H22RmQ
It is identical with what tagDiv example is showing:
https://cloud.tagdiv.com/category/podcasts/sub-category-podcast-1/page/2/

As the first screenshot shows all images are the same, but under each image is a different subcategory-name listed
The image is not representing any subcategory, but instead the main category.
When removing that image from the main category, no image is showing in the element subcategories.

• This reply was modified 1 year by AndrewT.
• This reply was modified 1 year by AndrewT.

For some reason td composer subcategries images are not working right.It only shows one image for all the sub categories listed. The image that is shown is the image of the main category.

In Admin > Newspaper > Theme panel > categories
Each category and subcategory has its own background image

In TagDiv Composer
For the main category I got the cloud template: Category Template 33 – Parent – Podcasts.

the Subcategories item (element) is part of the template.
It is working as it should, except for the image.
It shows all subcategories names and descriptions correct, but only the image of the main category is showing for all subcategories.

When the image of the main category is remove in Theme panel > categories
no image is showing.

How can this be fixed?

Hi Anamaria,

I already have the related section that you show in the screenshot on the website at the moment. These articles are matched based on tags/categories. However, this is not desirable because we use the tags and categories for multiple news items that have nothing to do with each other.

So I am actually looking for a way where I can link an article myself in a related articles section. Otherwise we have to create a tag for each topic and attach it to the flex block via TD Composer. I hope you understand me, it is difficult to explain.

Hi Anamaria,

Thanks for the reply. How can editors link articles here without going to the TD composer? Our editors only write and don’t know anything about technical stuff. I want them to be able to do everything from Gutenberg in the post editor.

• This reply was modified 1 year by marijn390.

Hi Bettina,

No, the images have never changed this. Again, the only difference here is the extra piece of code “,“TDMAXWIDTH”:786}”.

It’s the same template, so the row size in TagDiv Composer is the same for both articles. Can you tell me where that “,“TDMAXWIDTH”:786}” is being set from and why it is suddenly appearing?

Thanks!

What we actually do here is edit the views module file inside td-composer to match our existing custom field (in our case existing field for 10+ years is “views”). Have to remember to edit on each update, but it’s what we do.

Apologies, I don’t recall the exact file path.
Oh, sorry; this fix we do with newsmag, not newspaper; might be entirely different file location.

Heh. Well, we’re old, and using WordPress since 2004.
In our case we have couple of high traffic sites, one online since 2000 as a newwire service.

For the Tagdiv sites, we actually have WP-PostViews installed, but not active, as this generated a custom field “views” and then we hack the views file in td-composer to change the TD views field to “views”. We then use the TD counter, but turn off extraneous things like most popular, popular 7 days, random views, and views are OFF everywhere except the actual posts — not on any modules. (We want to use a custom field “views” so that the counter is evergreen and agnostic and not tied to theme.)

On the other site, we turn off TD views entirely, and use the WP-PostViews plugin and insert the template code at bottom of the main post template file we’re using for posts.

Each of those sites have 768M allocated.

Your mileage may vary. But turning off a lot of “tricky” things visitors don’t really care about will lower your “query load” and that also speeds up the whole site.

• This reply was modified 1 year by simchris.