This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Our next available supporter will start replying to tickets in about 0.95 hours from now. Thank you for your understanding.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 5 replies, has 2 voices.
Last updated by Christian Cox 7 years, 7 months ago.
Assisted by: Christian Cox.
Hi, I definitely recommend using a child theme if you are making any changes in theme files, like functions.php or style.css, single.php, etc. If you make modifications to any of the theme files in the Toolset Starter Theme, those will be overwritten if we release a new version of the theme in the future and someone chooses to update. If you create your own child theme, your modifications will not be overwritten by future theme updates.
The flash of styles I see while your site is loading seems to be related to several different plugins loading stylesheets after page load. For instance, please see the DOM screenshot attached. Each of these link tags represents a stylesheet that needs to be loaded after the page begins to render. If you delete stylesheets vc-mm-css and vc-mm-skins-css (I assume these are from VC Mega Menu), your Mega Menu looks broken. If you delete the wp_ddl_layout_fe_css-css stylesheet as well (from Toolset), you can see how your menu looks while the site is loading.
If the flicker is troublesome for you, there are a few options. You could consider adding some CSS in the document <head> that hides your menu content by setting it to opacity:0. This means that as the page begins to load, your menu will be hidden. Then in one of the CSS files that gets loaded later, you can override that with opacity:1. Alternatively, you could consider moving all the CSS that styles the top part of the screen into a style definition in the head of the document so it is loaded as soon as the HTML is downloaded. Do either of those approaches seem feasible for you?
