Fuzzy or blury text element on a page

[referee]

Hi Team,

I wonder why all my Cell 3 text elements inside Event Grid may look fuzzy or pixelated compared to all other text elements in the archive template? I checked the properties and couldn’t find any difference in the settings. I even tried to copy and paste styles for the containers and elements themselves. There are no shaddows or anything that could lead to that. Any ideas?

[christian]

Hey John,

Update your Cell 3’s Y Start to auto.

[referee]

Thanks, @christian, for replying quickly. The issue disappears, but all conditional blocks that should be hidden appear in that section than.

But I have just realised that it is due to the Looper structure I have. The thing is that Cell 3 serves as both the Looper Provider and the Looper Consumer for all Ages taxonomy.

Inside I have a block which is Looper Provider for ACF {{dc:acf:post_field field="event_weights"}}.

Then on the next level I have nested blcoks for each sport disipline Loopers {{dc:acf:post_field field="event_weights_sport"}} and {{dc:acf:post_field field="event_weights_fight"}} as well as {{dc:acf:post_field field="event_weights_beach"}}.

Finally, inside those blocks, I have ACF weight fields that are conditionally related to each age term selected for the events. There are different sets of those for selected Ages and Disciplines. I could not find a better way to implement that.

Basically, higher level Looper Providers don’t output anything. On the page I show related lower level ACF values only and Taxonomy is only used to loop through all ACF weight groups of the event. If I switch off Looper Consumers for higher levels of that structure, the issue disappears. So if it looks like Looper Provider (Taxonomy) > Looper Provider (ACF Repeater) > Looper Provider and Consumer (ACF nested Repeater) text looks fine.

That happened due to this discussion of Looper structure with Rue. That is why I added Looper Consumers for higher levels of the structure which actually caused the issue with fuzzy text. But the problem with that ticket was that I shouldn’t use a nested looper for the documents at all. I needed a single meta read “does this post have at least one document” instead. I removed the Looper Provider and Looper Consumer for the Doc Button entirely, and set another condition instead.

Sometimes the layout becomes rather complex where one thing is dependent on another. But I try to open separate tickets for each topic as you guys always ask. This is definitely more productive but sometimes they are kind of linked in some specific aspects. I hope I have solved them all now with respect to that archive layout. But I will need to run more tests to be sure.

Sorry for taking your time reading this explanation. Thanks again for your help to all of you guys from Themeco Support. That is a great help to get a clue what is really going on!

[prakash_s]

Hello John,

Thank you for the detailed explanation, and I’m glad you were able to get everything working.

Thanks