Hi,

This is AJ the theme author.

• Carousel: There isn’t any known issues with the carousel module, it is working when I test myself: https://cl.ly/4a079d

Can you make sure to clear all site cache and browser cache? The carousel has updated javascript so it’s possible there is a caching issue preventing it from working.

Also, if you did modify the carousel via a child theme via the file at vcex_templates/vcex_portfolio_carousel.php it needs to be updated accordingly to work with the updated scripts.

• Regarding the Icon box hover color, I was able to recreate this bug. Thank you for letting me know. I will be adding a fix for the upcoming 4.9.2 update. Thanks so much for letting me know!

- AJ

ps: The issue with the icon box hover could be breaking the carousel, if they are added on the same page.

If you wanted a quick FTP fix here is the fixed file for the icon box: https://cl.ly/fb06be – you can replace via FTP under plugins/total-theme-core/inc/wpbakery/templates.

I am pretty sure the hover issue was actually breaking the carousel due to the error it was generating. This will be fixed also in the Total update i’ll release today along with the updated Total theme Core v 1.0.3

Thanks for reporting the issue!

- AJ

Hi AJ. Thanks for all your help! Sounds like you’re all over this issue. I have cleared my caches now which didn’t help.

I haven’t modified the Carousel via a child theme. I just left the Carousel on the homepage as per the Theme default.

Yes the Icon Box and Carousel are both on the same as per the default homepage in the Total Theme. The only thing that was changes from the default really were the colours and the hover background colour.

- Perhaps I should just wait for your Core Theme update today instead of playing with the FTP?

- Also this is a total novice question but how do I update WP Bakery Page Builder which came with the theme to 6.0.3? (currently on 6.0.2) It says auto updates unavailable but not sure how to update it.

Thanks! Rusty

Hi Rusty,

I’m pushing out Total 4.9.2 right now which will have the Total theme Core update to 1.0.3 and WPBakery update to 6.0.3.

Now, Total has functions to prevent any notices for WPBakery updates in the backend which prevents requests to their API to keep your site faster. If you are seeing notices to update the plugin there are only 2 reasons for this:

• You have “Theme Mode” disabled (unchecked) in the Theme Panel: https://cl.ly/5b96e5
• You are using a Multisite with the plugin active on the primary install or network active (the theme can only remove themes when the theme is active and you can’t have the theme running on a multisite the same way a plugin can so it can cause the WPBakery notices to show up still).

- AJ

Hi AJ, Great news! Look forward to the update. - Re the WP Bakery updates – “Theme Mode” is enabled in the theme panel – I have a “developer” site in the backend using this same Total theme I very occasionally play with. i know that is allowed and I had to switch my current site: energeticconsulting.com.au to be the primary website and the other “sandpit” site to secondary via my host. So perhaps that’s impacting this and what you mean my “multisite” Cheers, Russ

Hi Russ,

I released the theme update if you have any problems updating or any pending issues after updating please let me know!

- Aj

ps: What I meant about multisite is actually this – https://wordpress.org/support/article/create-a-network/ – which doesn’t seem like you are using. Also, feel free to have unlimited developer sites, it’s not an issue. You don’t have to activate the theme license on developer sites. For developer sites you can just install the Envato Market plugin to get updates instead of the built-in theme function which requires the license – https://www.wpexplorer.com/envato-market-plugin-guide/

Hi AJ, The theme update worked perfectly. Great job!

Thanks for the advice around the multisite and developer sites.

- Can I somehow duplicate my live licensed site into a developer site in the backend? So a cloning of sorts to create an identical site just for testing purposes in the backend?

- Also I want to purchase another theme license and then again clone/duplicate my current website and create a new website for myself for a different business. Can I do that somehow?

That would save heaps of time in site build time and working out all the glitches! Cheers, Russ

Hi Mike,

1. Which h1 headings are you referring to specifically? Are these added via the “Heading” module? If so, I remember adding a fix for the font-weight (because this is a custom “preset” for the heading module it shouldn’t be pulling the custom font weight from the Customizer or custom hover colors. This was actually a fix added a few versions ago.

2. I did make a couple small changes to the localScroll but I’ve tested locally and don’t have any issues with the placement. Can you please share the URL so I can check out the live site and see what’s going on?

Now I may need WP/FTP logins to troubleshoot the sticky header and localscroll function if I can’t see the issue just by looking at the live site.

It could just be a caching issue, have you tried clearing the cache?

The tricky part with the shrink header and local scroll is that local scroll position calculations need to happen before the scrolling takes place while the shrink header shrinks as you scroll down, so if your local scroll location is positioned at a location that is x distance from the header equal to the default header height it could cause a little offset issue. But this is very unlikely so I don’t think this is the case.

There could also be an issue simply when you are logged in because of the WordPress admin bar.

Either way, if I can take a look we should be able to fix that up.

Thank you for the renewal mike, it helps!

- AJ

Hi and thank you for your response.

1.) Regarding the Heading / H1 issue: Yes, these were added via the Heading Module and you must have made those changes after 4.8.5. Cool! This works for me.

2.) Regarding the Local Scroll / Header Shrink issue: I restored back to the previous version right after I noticed this issue so I will need to upgrade again first before we can troubleshoot. Also, I did clear both host and browser cache (don’t have a CDN) – I always do this after upgrading. I see you pushed out a new update since so maybe that will help??? I will respond here after I do that.

There is something else that you need to know regarding issue #2: Just after I upgraded from 4.8.5 to 4.9.1, and before I noticed the local scroll and header shrink issue, I uploaded and activated one of your Extensions to test it out (Total Logo Description) and I experimented with it just to see what it actually did. I decided to deactivate it and delete it because I noticed that it messed with the header shrink functionality (don’t remember if it messed with Local Scroll as well).

Below is a short timeline of what I did as this might help:

1.) Upgraded from 4.8.5 to 4.9.1

2.) Upgraded plugins

3.) Cleared host and browser cache

4.) Looked around and everything seemed to be ok (not sure if header shrink / local scroll issues were happening yet)

5.) Uploaded and activated Total Logo Description plugin

6.) Looked around and noticed header shrink issue (not sure about local scroll issue at this point)

7.) Deactivated and deleted Total Logo Description plugin

8.) Cleared host and browser cache

9.) Looked around and noticed both header shrink / local scroll issues

10.) Did a whole host account restore to the day before I upgraded from 4.8.5 to 4.9.1 in step “1” above (I use SiteGround hosting)

11.) Cleared host and browser cache

12.) Looked around and local scroll and header shrink are both back to working as they should (even when I am signed in and the WordPress Admin bar is present)

13.) Upgraded from 4.8.5 to 4.9.1 again

14.) Upgraded plugins

15.) Cleared host and browser cache

16.) Looked around and local scroll and header shrink issues both returned

One last thing and I’m not sure if this has anything to do with it: I noticed that the Total Core plugin was still in my plugin directory even after I restored my hosting account to a time before I first installed it (in step 10 above) which I thought was weird.

I hope all that information above helps and I will do an upgrade to the newest theme version and let you know what happens.

Thanks again for your help,

Mike

Hi Mike,

I Hope you had a nice weekend. I haven’t heard back from you so I’m hoping everything went smooth.

Not you are correct, the extension to add a description under the logo will affect the shrink header and possibly local scroll since the local scroll has to calculate the end header height before the scrolling starts and this is done based on your logo shrink height (as defined in the Customizer) if you add a description under the logo the logo height changes and it can’t be calculated correctly. But if you use the standard sticky header (no shrink) it should work correctly or if you use CSS to hide the description under the logo when it becomes sticky.

Keep me posted on the local scroll issue, it is possible I made a small error in my theme and if I did I can log onto your site and fix it manually then add the fix in the next theme update. I would need to look at your site first though since every test I’ve tried locally I can’t break the scroll position – thanks!

- AJ

Hi Michel,

Yes, you could add some code to your child theme to insert the term names into the body tag, this is very easy. Do you know the name of the taxonomy? This way I can give you the code.

- AJ

By the way…I’m not sure what you meant by “a single doesn’t have its category in body tag like Total’s post types” – because Total doesn’t add the category into the body tag for it’s post types (portfolio, staff. testimonials). Sounds like maybe you already added some code to your child theme to do this?

- AJ

Thank you AJ.

I haven’t added code for body tags, and here’s the CPT info :

Post type : my_keywords

Taxonomy : keywords_family

And a sample post if it helps (with messy category style yet) : https://culture-officer.fr/my_keywords/14787

Michel

Hi Michel,

So you just want a classname like “keywords_family-term-1-ID” added to the body tag, correct?

- AJ

Yes AJ

Something like this should work (didn’t test since I didn’t want to take all the extra time to create a post type and add terms on a dummy site, but it looks correct to me):

add_filter( 'body_class', function( $classes ) {
    if ( is_singular( 'my_keywords' ) ) {
        $terms = get_terms( 'keywords_family', array(
            'hide_empty' => false,
        ) );
        if ( ! empty( $terms ) && ! is_wp_error( $terms ) ) {
            foreach ( $terms as $term ) {
                $classes[] = 'keywords_family-term-' . absint( $term->term_id );
            }
        }
    }
    return $classes;
} );

Reference:

• https://developer.wordpress.org/reference/functions/body_class/
• https://developer.wordpress.org/reference/functions/get_terms/

- AJ

Hi David,

This is AJ the theme author. Haven’t heard from you in a while, I hope all is good!

Did you get this email during the update or do you have the error on the live site? Basically the error is saying that a file is missing from the site so I can’t be loaded. This would happen if someone tried loading your site while it was performing updates and so the file was currently deleted.

If your site looks good now, you have nothing to worry about most likely it’s like I said, the error was triggered during the update when someone tried to view the site as files were being deleted/installed.

- AJ

Hi AJ,

OK, makes sense. We’ll proceed with the update on the live site and let you know if there are any issues.

Thanks! David

Hi AJ,

We now received the same error message email after we updated the live site to the new version of the theme, same thing that happened on the staging site. Other than that error message the site seems to be operating as expected.

Is there anything else you think we should do?

Thanks! David

Hi AJ,

I never heard back from you from my last message. Please let me know your thoughts about getting the message on the live site as well.

Thanks, David

Hi David,

Weird, I never got your reply! Sorry about that.

So basically if your site is working correctly there is nothing to worry about. What’s going on is that WordPress sends out an email now whenever an error is detected. It sounds like what happened was during the update process someone loaded your live site and triggered this email warning (when the site is being updated files are being deleted so if someone tries to access the live site at the same time it can trigger an error).

It’s kind of an annoying that WordPress does this but I do believe in their email it does say something along the lines of “please check your live site to verify there are no errors” – as long as your site is fine you can ignore the email. I could be wrong as I have yet to actually receive this type of email, but I remember reading this somewhere in the WP developer notes.

Definitely a bug in WordPress or maybe it’s intentional but can be confusing.

I’ve had a couple customers complain about this but it seems most don’t get the issue. I’m thinking this may have something to do with the Wordpress “maintenance mode” function which is supposed to trigger when a theme or plugin is being updated and depending on your server settings it’s possible it’s not being triggered on your site.

Does that make sense?

- AJ