We already use Cloud Templates for a lot of our pages, but we also use normal Pages still, etc. I’ve read through this link (https://tagdiv.com/newspaper-theme-update-standard-pack-or-tagdiv-cloud-templates/), but is there some kind of step-by-step guide as to the things we need to do before we deactivate the Standard Pack? I think we are close to being able to do that, but I don’t want to do it too early.
Our site is: https://www.vitalthrills.com
Hello !
In order to deactivate the standard pack which will result in a greater page speed you will have to switch to PRO demos / layout but that will require design adjustments / re-design. And after switching to pro everything will be shortcoded so the amount of code available on the page will be dictated by that.
Unfortunately at the moment we are not able to provide a step by step tutorial.
I hope this was helpfull !
Thank you !
Okay, we will look into doing that.
We changed the site’s demo to Default PRO yesterday, updated the theme panel to make things look like they were, etc., and then briefly deactivated the Standard Pack to see what it would look like. Below, you can see some screenshots of the Home page, an article page, and category page.
https://www.vitalthrills.com/wp-content/uploads/2019/11/screenshot3.jpg
https://www.vitalthrills.com/wp-content/uploads/2019/11/screenshot1.jpg
https://www.vitalthrills.com/wp-content/uploads/2019/11/screenshot2.jpg
What would we need to do in order for things like the logo & header, the content block on the home page, and the sidebar on category pages to show normally?
Are there elements available in tagDiv Composer that should replace these? Does it work the same for the Pages and Cloud Templates sections?
Here is the live site with the Standard Pack activated: https://www.vitalthrills.com
Thanks for any advice you can give.
Hello !
If you want to properly convert to full pro demo you will have to disable the standard pack from begining and build your page based on a default pro demo.
When you deactivate the standard pack you will face the issue shown on picture 3. So you can disable that, and install defaul pro demo for example and after that start editing your theme.
Thank you !
I’m not sure I understand. It says here (https://tagdiv.com/newspaper-theme-update-standard-pack-or-tagdiv-cloud-templates/):
“To make the transition from 9.8 to Newspaper 10 with Cloud templates, you need to ensure you gradually and smoothly remove the dependencies. Please read this, don’t scan. Failing in removing dependencies prior to deactivating the Standard Pack will break your website.
If your website uses any of the templates present there, you must replace it with its equivalent from the tagDiv Cloud Library.
We’ve made it easy for you and recreated them. Every template from the theme panel already exists in the tagDiv Cloud Library. It should be easy to find the one that’s closer to your brand and import it on your website. Customize it using tagDiv Composer and assign it to replace the existing one.
You must find and replace templates until you’ve completed the process. Then simply deactivate the Standard Pack, and you are ready for speed and performance.”
Doesn’t that mean I can now go into the Home page in ‘Pages’ and my other pages in Cloud Templates and swap the current header, blocks etc with I guess ones from the Cloud Library? Like I said above, you guys really need a guide on how to do this properly. It’s a little confusing.
Hello !
Yes, but please note that in Newspaper 10 There have been added some new blocks and removed some. So you will have to reproduce the Blocks using the flex blocks, if you’re using normal blocks then you will still be facing an issue. You can test and deactivate the Standard pack and see what blocks are left in the composer, those are the ones that can be used next.
Thank you !
Thanks Vlad. We’ll look into only using the flex blocks.
We’ve updated the header and footer to both be Cloud-based, but we ran into a couple of things.
For the Header, everything seems to be working fine on Chrome and Firefox, but on Safari the sticky menu doesn’t show the “More” pulldown menu. Do we need a special custom code for that? It’s showing just fine in the normal menu on Safari before you start scrolling down.
For the Footer, there’s a white line at the very very bottom of the page. Is there a way to get rid of that?
Upon closer inspection, the “More” menu in the sticky menu on Safari only doesn’t load on the home page. It seems it loads on all other pages and posts.
Another question: Which section in the Style settings for the header would allow us to make the “More” menu items in the sticky menu look like the “More” items in the normal menu?
Okay, I think I fixed a lot of those issues (except for the white bar under the footer), but now I’m encountering another problem on Safari and Microsoft Edge that is not on Chrome and Safari. When you mouse over the sticky menu in a post (not on a normal page), the articles in the mega menu that show below are aligned to the right.
Hello !
We have inspected your website on safari and the sticky menu works fine, But the alignment issue if you check is on chrome too. You will have to re-check the plugins and also check for some unwanted css coding.
Thank you !
I fixed the sticky menu from appearing on the right by setting the sticky menu mega menu to “Relative to menu.” That seems like only a temporary fix as the normal menu is set to “Relative to screen” and is showing fine. Any thoughts on this?
I turned off the standard pack, but I’m still seeing issues with the menu and other things:
1. In all browsers, when you first load the page, the height of the main red menu is really high for a second, then it snaps back to the proper height. Is this normal?
2. In Safari, the sticky menu on the home page (https://www.vitalthrills.com) does not pull down the posts or the “More” submenu. That seems to work fine in other browsers.
3. In all the browsers on posts (example: https://www.vitalthrills.com/2019/11/15/frozen-2-cast-and-crew-on-the-sequel/), the sticky menu “More” submenu items text seem to be squished and not each on one line. They are on one line in the normal menu.
4. Also in Safari, on the home page (https://www.vitalthrills.com), the Ajax Categories in the “Latest Articles” section (Flex Block 1) do not work, but they work in all other browsers.
Please ignore #4, as I went ahead and switched out the Flex Block 1 to a Posts Loop, which doesn’t have Ajax.
Hello !
We have investigated your website on Safari and Chrome and everything seems to work out great. Please make sure you are clearing your cache after any change.
Thank you !
Clearing the browsers’ caches solved some of these issues. Still seeing #3, but it’s not that big of a deal I guess.
Thanks for taking a look.
Hello !
Just re-tested them, the issue still doesn’t seem to appear. Please provide a photo with the differences that you’re seeing so we can have an ideea of the issue, maybe we’re looking in the wrong direction.
Thank you !
This is how the “More” pulldown menu should look in the sticky menu.
https://www.vitalthrills.com/wp-content/uploads/2019/11/stickymenunormal.jpg
This is how it looks on Posts and Categories.
https://www.vitalthrills.com/wp-content/uploads/2019/11/stickymenucondensed.jpg
Hello !
That happens on Chrome and other browsers too but you can try this CSS code that should fix your issue:
.tdb_header_menu .tdb-menu>li:hover>ul, .tdb_header_menu .tdb-menu>li.tdb-hover>ul {
min-width: 20em;
}
I hope this was helpful !
Thank you !
Perfect, thank you. This fixed it.
