Hi, there.
We are using TagDiv Newspaper 12.4 template and, this morning, we found out that our homepage, category view and article view have been messed up. The css formatting wasn’t like it was supposed to be.
After looking deep into the problem, we found out that the website is not rendering anymore the mobile version of the Cloud Template we assigned it.
Can you, please help us? I can provide you more details in private.
Regards,
Ciprian
Hello Ciprian!
Actually, we have 3 options for mobile versions that you can use:
1. Responsive version: A responsive version of your website looks similar to the desktop version. TagDiv Composer is used to edit the page.Click on the mobile viewport: https://www.screencast.com/t/XDQJedlggSB. There, you can see your mobile version and edit or adjust the elements to look better.
2. Mobile pages: https://tagdiv.com/newspaper-10-3-7-update-brings-customizable-and-fast-mobile-pages
3. Mobile theme plugin: The Mobile Theme is a performance-optimized theme included in the main Newspaper theme that only loads on mobile devices. It comes with its own templates and designs for pages, posts, categories, etc., so your current templates from the desktop theme will get converted to the mobile theme layout. Please see https://forum.tagdiv.com/the-mobile-theme/ and https://forum.tagdiv.com/mobile-theme-introduction/ for more information.
A full explanation is here: https://www.youtube.com/watch?v=SpGkOnJeNZY
If you need to use the mobile version 1 or 2, then you need to disable the Mobile Theme plugin.
Thank you!
Hi, Bettina.
Thank you very much for your answer. We are using the second scenario/version. We have separate mobile versions for the layouts we are using and, since you introduced this feature, we used it with no problem.
Regarding the third situation, we are using the mobile theme plugin just for AMP pages.
Meanwhile, we had an issue regarding a cdn SSL certificate expiring and, after we managed to renew it, the problem with the layout rendering fixed by itself.
I am thinking that it was something related to this CDN/subdomain SSL certificate.
Thanks!
Ciprian
Hi observatorulprahovean,
We are glad that the problem has been resolved.
Indeed, we has a few similar reports and the problem were caused by CDN settings.
In case you have some questions or you’ll face problems, please let us know and we’ll try our best to help you!
Thank you!
