Search Results for 'mobile theme'

How do I create a mobile design that’s independent of the desktop browser design without using the default mobile theme?
Next, in the WordPress settings – reading – static pages – homepage, I set it to “home.” For the post page, should I leave it blank or use a mobile template?
Or, what should I use as the homepage in WordPress: the original page or the mobile template?

How to create a Mobile Design that is Independent from the Desktop Browser Design, without using the default mobile theme.

Ah, got it. Disabled and the pages are now showing.

Does that mean I cannot use the mobile theme, and have the pages working properly?

Hi,

Could you explain how I ‘select the tagDiv Mobile theme plugin’?

It is in my plugins, activated, but I cannot ‘select’ it.

I’ve deactivated and reactivated it, cleared full cache.

Thanks for the help.

I have created a mobile theme on my website, but not using a mobile theme plugin, can I use AMP?

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.

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

Hi Cailin.

a) Yes, Rev Slider is fully updated (6.7.40)
b) Yes, RS is at the beginning of the page. We tried to delete it and the layout is OK (posts are in the right place, obviously): we also tried to replace the previous RS layout with a new one, but the issue persists
c) we choose to delete the RS for now, the general layout was terrible
d) Yes, we disabled the tagDiv Mobile theme

Here some images:

https://postimg.cc/gallery/VcVBLMR

Thank you