Search Results for 'block'

Hi,

Is that block cache new? Dont see it in settings.

Another small change in the text of the menus for vertical tablets.

I inserted the script of this type to prevent the menu at the bottom and the appropriate lines.. the model fails to shrink and align the menu

/* Sottomenu a piè di pagina – Tablet verticale (Newsmag) */ @media (larghezza minima: 768px) e (larghezza massima: 1024px) { .td-sub-footer-container .menu-item > a { dimensione del carattere: 10px; imbottitura: 0 5px; altezza della linea: 1.4; } }

FOR ADSENSE it seems difficult to solve.

Even entering this doesn’t work

/* FIX AdSense overflow – Sub Footer Newsmag */
.td-sub-footer-container,
.td-sub-footer-container .td-pb-row,
.td-sub-footer-container .td-pb-span4,
.td-sub-footer-container .td-pb-span8,
.td-sub-footer-container .widget {
max-width: 100%;
overflow: hidden;
}

.td-sub-footer-container ins,
.td-sub-footer-container ins.adsbygoogle {
display: block !important;
max-width: 100% !important;
width: auto !important;
}

• This reply was modified 6 months by SBC.

Hi Calin,

Thanks for the suggestions — we tested exactly as requested (logged in, no cache, and only tagDiv/theme plugins active) and the issue still reproduces reliably on our side on both desktop and mobile.

From comparing the DOM between an installation where the search works and our installations where it fails, the key difference is where the theme’s Accessibility module ends up placing/targeting #maincontent. The module (via tdAccessibility.js) assigns/normalises the #maincontent container based on what it detects in the page structure (e.g., presence/absence of a proper <main> element and the surrounding wrappers). On our affected sites, #maincontent resolves to a wrapper that also contains the header/search trigger, so when the search is opened the script attempts to apply aria-hidden/inert to #maincontent while focus is still on the search trigger. Chromium then blocks aria-hidden in that state (“descendant retained focus”), and the page ends up in an inconsistent/blocked interaction state.

This would also explain why the same setting appears to work on a generic installation: if #maincontent resolves to the actual content area (excluding the header), the search trigger is not a descendant of #maincontent, so the focus/aria-hidden conflict never happens.

Thank you.

Hi,

As per your instructions, I have used the flex block builder and selected the module that I have downloaded “APP Listings – 2 from App Find PRO Demo” and used it in my website aiopscommunity.com but the module doesn’t list the posts from the app listings. You can check the same under the heading “AiOps Apps / Tools” in the url that I have given “https://aiopscommunity.com&#8221;

I have a layout where I use Category Description to display custom text for categories, and it works correctly on category pages.

However, I have an issue with the top menu:
some menu items are normal pages, not categories. When I open those pages, an empty text block appears, as if they were categories, showing the default placeholder text (like “lorem ipsum”).

The problem is that:

If I delete the category description text on one page, it is deleted on all categories and pages.

If I add text using Text with Title or Inline Text in the template, that text appears on all categories, pages, and posts.

The Category Description seems to be shared globally across archives/pages when the same template is used.

I cannot set different texts for pages and categories without affecting posts or other pages.

What I want is:

Categories → show their own category description text

Pages in the top menu (not categories) → show different custom text or no category text

It seems the problem has been fixed by lowering the category text a bit; if it’s lowered just above the entries, it behaves correctly. Just in case that helps.

Thanks

Hi Calin,

Yes, that’s right, it would be nice to have an option to disable the opacity on hover setting. I have an instance where the buttons overhang a background of the same colour. It looks nice until someone hovers over a button.

Also, please note that imgur is now blocked in the UK, making your shared screenshots inaccessible to a wide number of users. Might I suggest another image sharing tool.

Why WordPress + Newspaper creates ~27 image sizes

Two things are happening at once:

1️⃣ WordPress core creates image sizes

By default WordPress generates:

thumbnail

medium

medium_large

large

plus retina variants (2x)

2️⃣ Newspaper theme (tagDiv) adds many custom sizes

Newspaper is optimized for:

blocks

sliders

modules

mobile / tablet / desktop

retina (2x)

So it registers 20+ custom image sizes, which is why every upload explodes into ~27 files.

👉 This is normal behavior for Newspaper — not a bug.

What image sizes does Newspaper REALLY use?

In practice, Newspaper mostly uses these core groups:

✅ Commonly used sizes

td_696x0 → main article featured image

td_1068x0 → full-width layouts

td_300x220 → small blocks

td_534x462 → medium blocks

td_80x60 → widgets / lists

Retina (2x) versions of the above

⚠️ Many other sizes are edge cases (rare modules, legacy layouts, demos).

Option 1 (Recommended): Reduce image sizes SAFELY ✅
Step A: Disable unused sizes via code

Add this to functions.php (or a custom plugin):

add_filter(‘intermediate_image_sizes_advanced’, function ($sizes) {
$allowed = [
‘thumbnail’,
‘medium’,
‘large’,
‘td_696x0’,
‘td_300x220’,
‘td_534x462’
];

foreach ($sizes as $key => $value) {
if (!in_array($key, $allowed)) {
unset($sizes[$key]);
}
}

return $sizes;
});

📌 This:

Keeps only important Newspaper sizes

Stops WordPress from generating the rest

Option 2: Disable Retina Images (Huge win 🚀)

Newspaper creates 2x images by default.

Turn them off:

Newspaper → Theme Panel → General Settings → Retina Display
➡️ Disable Retina Images

💡 This alone can cut image generation almost in half.

Option 3: Use a plugin (Easiest, no code)

Install Disable Media Sizes or Perfmatters.

Then:

Disable unused WordPress sizes

Leave Newspaper core sizes enabled

⚠️ Don’t blindly disable everything — Newspaper needs some sizes to avoid layout breaks.

Option 4: Regenerate after cleanup (IMPORTANT)

After changing sizes:

Install Regenerate Thumbnails

Regenerate

Delete old unused thumbnails (plugin or server cleanup)

❌ What NOT to do

Don’t disable all td_* sizes

Don’t edit Newspaper core files

Don’t rely only on CDN offloading (it hides the problem but doesn’t fix disk usage)

Best setup for Newspaper (my recommendation)

✅ Disable Retina
✅ Keep 6–8 essential sizes only
✅ Use Bunny / CDN for delivery
✅ Use WebP/AVIF

This keeps:

Layout intact

Disk usage low

CDN fast

Thanks for the clarification, Calin.

Suggestion still stands, would be great if the developers could add an option to display the message on flex blocks as well as loop blocks.

Hi Calin,

Just tried the flex block builder, which as you say does have the filtering options. Unfortunately, it still doesn’t let me display a ‘no results found’ message.

Thank you for the tip nonetheless.