Hi,

The front-end login form uses the native WordPress functionality – https://developer.wordpress.org/reference/functions/wp_login_form/ – which you are correct, it will redirect them to the default WP login form. It’s not possible to alter how that works without creating a custom login form completely. I personally didn’t want to code a custom login functionality because it introduces security concerns.

Depending on your site, it may be best to instead customize the default WordPress login page and use that, see Theme Panel > Custom Login. This way you can at least add your own logo and tweak the colors so it better matches your site and you don’t need to add a 3rd party custom front-end login form plugin and introduce potential extra security risks to the site.

Now, if you do decide to use a custom front-end login form plugin that uses it’s own custom code, I would recommend disabling the native WordPress admin login page and making sure it redirects to your custom page so you don’t have 2 login pages.

- AJ

Understood, Thank you!

Got it, I will have a look and reply asap!

AJ, I believe I have found the solution. Unfortunately, I had to go and remove the .woff2 font file completely, then save the font without a file, then reupload the font. After completing this, the system now recognizes the self-hosted font.

Not sure why the fonts were no longer recognized, but if you have anyone else ask about this, we may have a workaround.

Hi,

I replied to your ticket a week ago and let you know of the issue. Did you not see my response? Here is a screenshot of my email: https://a.cl.ly/llulXDYZ

According to my system you did read my reply though, unless that’s a bug…

The problem was that your fonts were added as otf files and not woff2 files. I fixed your staging site so you could see them working correctly.

I also explained why the fonts were “no longer recognized”. Can you double check your spam folder and see if perhaps my email got spammed. I want to make sure you are receiving my replies from the support tickets.

- AJ

I really appreciate all the licenses and the kind words

Let me know if you have any suggestions for future improvements!

- AJ

Hi AJ, I feel a bit lost because I can’t see what is wrong – therefore I have created a private ticket and have given you temporary acces to the site hoping you can help me figure out what’s wong. I have named the ticket ‘Show hide shop categories issue’.

Hi again, I tried to rebuild the dynamic page and now it seems to work like before. I really don’t know what was wrong, but I’m glad it works now.

Very strange! Definitely sounds like a weird object caching issue where the WordPress term relationships may not have been working correctly or the page HTML was incorrectly cached by an optimization plugin.

Glad it’s working now!

- AJ

Hi,

If the old site had the license registered, you can simply log in here – https://my.totalwptheme.com/ – click on the License Manager at the top and then hit the trash icon next to any license you wish to un-register so that it can be registered on a different domain.

- AJ

Thank you! I managed to update the license now to my new domain.

Hi AJ,

Thank you for you the response. Please find the URL of where you can view the slider. https://www.camensarchitecturalgroup.com/ Please find the dropbox link which contains exported slider in zip format https://www.dropbox.com/scl/fi/yomnl1rt2curoqxwmpo87/home.zip?rlkey=u8vxi9btqzhw5i13z5v5rqcjd&st=du15myfq&dl=0

Thank you for your consideration but the requirement is like all the images want to loop again.

Thanks, Murugan

Hi Murugan,

I tested your slider locally and I didn’t have any issues. And there are so many images that it takes a very long time to sit here and wait for all of them to rotate to try and recreate the issue on the site.

But, you are doing a huge disservice to the site by having this slider. Every single slide has the same text so only the images are changing. This means there isn’t any real added value in sitting watching the slides rotate, it’s also not clear to the visitor that the images will even change.

Most visitors will come to the site and instantly scroll down (especially because you have a down arrow indicating that you should scroll). This means your site is going to be constantly loading massive images and rotating them slowing down the experience and more importantly on mobile using up a lot of your visitors data.

Not to mention that Slider revolution in of itself is a large plugin so you are slowing down the initial site loading time and page speed scores. Plus now you have to also keep that plugin installed and frequently updated.

You are also using the slider on pages like this – https://www.camensarchitecturalgroup.com/about-our-residential-architects/ – to display a single image at the top, which loads a white space and than the image fades-in. This causes 2 issues:

1. The original issue where loading the slider plugin slows down the site. 2. The site doesn’t load as nicely, because it shows a white space then the image loads it.

You can easily re-create these full width backgrounds without any slider using the page builder.

I would highly recommend updating the site so it doesn’t need to use Slider Revolution at all and for the homepage, if you really want to have some background images rotating, Total has an option you can use for this via the Section or Row elements under the “Slider” tab: https://a.cl.ly/NQuXlBp8 – but I would recommend keeping the number of images to a minimum (again most users won’t just sit there and watch the images transition).

Last, I notice on pages like the https://www.camensarchitecturalgroup.com/testimonials/ – you have manually added a menu and the slider at the top. For a quick transition, you can create a dynamic template – https://totalwptheme.com/docs/dynamic-templates/ – and assign it to those pages. This way you can control the design globally for all these pages in the future. Here is a quick video example: https://a.cl.ly/7Kur6nZv – this video also shows how you could display a gallery for the top full width image if you wanted to by using the Post Gallery.

Switching to this setup will make it easier to maintain/edit those pages in the future and you will benefit from a faster and better optimized setup. Plus, then you can disable Slider Revolution and delete it and never have to worry about updating it: https://totalwptheme.com/docs/disable-bundled-plugin/

I also recently wrote an article about why you should avoid sliders on your site if interested: https://totalwptheme.com/docs/why-not-use-sliders/

- AJ

ps: I forgot in my video creating the dynamic template to include the “Post Content” element – you will of course need to add this after the menu so it can display the content you’ve added on the page.

Hi,

This is Aj the theme author.

Personally, I would recommend using a horizontal scroll bar instead of a carousel, you can do this with the Flex Container. Or if the client doesn’t want all the Icon Boxes showing up in a grid, it may be best to add a “view all” button then put them all on their own page.

There are many reasons to avoid carousels: https://totalwptheme.com/docs/why-you-shouldnt-be-using-carousels-on-your-website/ – and you may want to advice your client against it.

In terms of a specific plugin, there are some extensions you can use – depending if you are using Elementor or WPBakery on your site. But again, I wouldn’t recommend it.

For WPBakery this is the only plugin I know about – https://codecanyon.net/item/carousel-anything-addon-wpbakery-page-builder-formerly-visual-composer/22549707

And for Elementor, there is a carousel element included in the Pro version of the plugin – https://elementor.com/help/carousel-widget/

I know you mentioned not wanting to use a custom Post Type, but honestly it’s a good solution and then you don’t need any add-ons.

• Create a new custom post type – https://totalwptheme.com/docs/adding-custom-post-types/
• Add custom fields to define the data – https://totalwptheme.com/docs/how-to-add-custom-fields/
• Create a custom card – https://totalwptheme.com/docs/custom-card-builder/ to display them via the Post Cards element (set to Display > Carousel)

It may sound complicated, but it’s actually very simple and by using a custom post type you provide your client with a much easier way to manage the items then having to edit the page itself.

Alternatively, if you have access to ACF Pro you instead of a custom post type you could create a custom Theme Options page with a repeater field for the data. Then use the theme’s ACF Repeater template function to create the output – https://totalwptheme.com/docs/how-to-create-acf-repeater-field-template/ – you can display the data using the Post Cards element with Query Type > Custom Field

- AJ

Great thanks for this i will take a look at the options.

Hi,

I’m doing good thank you! I took a much needed holiday weekend

This error generally occurs when a 3rd party plugin is incorrectly modifying the WordPress classic editor. You can try disabling plugins 1 by 1 to see which could be causing the issue. I did test locally on the latest version of WooCommerce and I didn’t see any errors so it seems to be coming from somewhere else.

Now, if you want a super quick fix you can go to the Theme Panel, sort by Editor and disable the Editor Shortcodes feature. This is an older feature which is not really needed for most people. What it does is add the following to the Editor: https://a.cl.ly/04uZEoyW – so if you aren’t actively using this feature then you should disable it anyway to slim things down.

- AJ

Hi,

This is AJ the theme author.

I’ve patched the version of the plugin that get’s installed with the theme so if you delete and re-install the plugin it will install the latest version. If you are worried about deleting the plugin you can instead edit the file at themes/Total/inc/admin/recommended-plugins.php and change the plugin version on line 89 to 6.7.37 like this: https://a.cl.ly/Kou6AGx9 – this will trigger the update notice under Appearance > Plugins so you can update as you would normally.

Now, the security vulnerability can only be exploited by users that have a contributor or higher role on the site. These user roles can already do a lot of bad stuff to your site, so it’s not of very high concern. Any users on your site that have these high privileges should already be well trusted. This is why I didn’t push out a theme update just to alert users of the updated plugin. If there is ever a critical security vulnerability I will release an immediate theme update.

One thing to mention also, is that sliders are not recommended for modern sites for various reasons (SEO, accessibility, usability, conversion rates, page speed scores…etc). I would highly recommend deleting any slider plugin and using static content whenever possible. If you do decide to optimize your site you can also disable any notifications for the plugin via the theme panel – https://totalwptheme.com/docs/disable-bundled-plugin/

- AJ

The screenshot: https://imgur.com/YkcSxyq

It’s ok, it was LightSpeed extension problem (CSS)

NVM. I found it.

Thanks for responding hope you had a good holiday as well. I’m using the header builder. On the off canvas menu setting the Expanded setting in the sub menu is set to off however all items are still expanded in the drop down despite having this setting off.

Hi,

Oh yes, in the Off-Canvas menu, the Mega Menus display using headings for each section like this: https://a.cl.ly/ApudXmNX – and if you turn off the Headings then it will display all items in a single list since there is no way to create “sections” as you need the headings for this.

There currently isn’t any way to display the items as “toggles” for the Mega menu in the Off-Canvs element, but I think this would be a good option to have. Let me look into it, it should technically be very easy as all it would essentially do is disable the Mega Menu functionality – so perhaps a simple on/off switch for Mega Menus should work as that will treat the mega menus like every other menu and create toggles.

I can let you know when the update is ready (I will work on it today) so that you can update the Total Theme Core plugin and make use of the new option right away without waiting for an official theme update.

- AJ

Oh ok, I forgot that this element by default does not add “toggles” for sub-dropdowns. Regardless if it’s a mega menu or not – I was fixed on the mega menu aspect.

The Off Canvas Menu uses the modern details element for the toggles (no need for JS) and having threaded details is bad practice and creates accessibility concerns:

Here’s why:

Screen readers: Each <details> element creates a disclosure widget. Nesting them adds cognitive load because users must track multiple “expanded/collapsed” states in sequence.

Keyboard navigation: Users tabbing through may find it cumbersome to reach deeply buried content, especially if summaries aren’t descriptive enough.

Usability: People with cognitive impairments (or even just on mobile) may lose context when opening multiple levels of nested disclosures.

-

I could update the element to add an option that will make it possible, but I wouldn’t want to encourage it as users may be creating accessibility issues unknowingly.

If you want the mega menus to be toggle-able, what I would recommend is creating a seperate menu for mobile where the mega menus are actually added as parent items, this way they are “moved” up a tier and so their sub-items will be hidden behind the toggle affect.

- AJ

Hi,

I’m releasing the 6.4.1 fix shortly. If you don’t have local Google Fonts enabled then some other plugin on your site is parsing the whole site content on save which triggers the error. Basically the code in the theme loads only on the front-end as it shouldn’t be needed in the admin, but some plugins will render the full page on save to do some things and it can trigger the error as it’s trying to load content intended only on the frontend but on the backend.

Sorry for the troubles, you should see the update popup hopefully within the hour!

- AJ

The update with the fix is live!

WordPress caches theme update checks to prevent constantly pinging the server. So if your site had recently requested a theme update check and it returned false then it may not check again for 12hrs.

So, if you don’t see the update available in your WP admin and your license is active, you can go to the Theme Panel and click the “Force Check” button under the “Updates” widget on the right hand side.

Sorry again for the troubles, if you have any other issues or questions please let me know, I hope you had a nice weekend.

- AJ

Hi,

The term order is based on the default term order in WordPress. There are 3 ways you can can change the order if you want a custom sort:

1) Don’t display categories automatically, rather create a custom menu so you can add the categories manually in the order you want.

2) You can use a term re-ordering plugin: https://wordpress.org/plugins/taxonomy-terms-order/

3) If you just want a different order (non-custom) that uses native WordPress sorting you can add a little custom code to your child theme functions.php file or via a code snippet plugin by hooking into the “vcex_navbar_get_terms_args” filter. Example:

add_filter( 'vcex_navbar_get_terms_args', function( $args ) {
    $args['order'] = 'ASC';
    $args['orderby'] = 'count';
    return $args;
} );

Here is the WP codex which explains all the $args that can be passed: https://developer.wordpress.org/reference/classes/wp_term_query/__construct/

So the example snippet would change the order based on how many posts are assigned to the term and sort them in ascending order.

- AJ

It sounds like there may be a different plugin on your site that is rendering the full page content whenever you save the post.

I am pushing out the patched 6.4.1 update shortly so you should see the update popup within the hour, sorry for the troubles!

Basically, the error happens because in Total I optimize my code so it only runs when absolutely needed, the local scroll function is only needed on the live site, so if a plugin is triggering the code in the admin then it will cause the error. I’ve added an extra check so if the local scroll code is called when not needed it will exit early and not trigger any error.

Sorry for the troubles, I don’t use any plugins that renders the live site when saving the page on the backend so I didn’t have this issue during my tests prior to updating. But I will be sure to keep this in mind for future theme changes.

- AJ

The update with the fix is live!

WordPress caches theme update checks to prevent constantly pinging the server. So if your site had recently requested a theme update check and it returned false then it may not check again for 12hrs.

So, if you don’t see the update available in your WP admin and your license is active, you can go to the Theme Panel and click the “Force Check” button under the “Updates” widget on the right hand side.

Sorry again for the troubles, if you have any other issues or questions please let me know, I hope you had a nice weekend.

- AJ

All fixed, many many thanks!

Hi,

There are many reasons why switching could cause issues, but they would all be server-related and not on the theme’s side.

When you say “site layout” I’m assuming you mean the design which would imply that perhaps the CSS is not correctly loaded on the site. My first thought would be that perhaps the issue is related to user permissions so the theme’s CSS isn’t loading.

• Ensure the PHP-FPM process user (commonly www-data, nginx, or similar) has read access to your WordPress files, themes, and plugins. CSS, JS, and media files must be readable; otherwise, pages may load without styles.

• Make sure URL rewrites in .htaccess (Apache) are correctly translated for Nginx or your FastCGI setup. Incorrect paths can prevent CSS/JS from loading.

If you switch to PHP-FPM and notice layout issues, open your browser’s developer console. Any errors related to files not loading, such as CSS or JavaScript, will show there and can help identify the cause.

- AJ

Thank you AJ

Hi,

Hmm, I looked back a few versions and nothing has changed with this filter. Are you updating from a much older version?

At one point I did optimize the code to cache the Footer ID so the filter is only going to run once so I can see how it can cause issues if you are wanting to modify the filter after the wp hook (where you can use conditionals like is_post, is_term…etc).

Working on a fix for this, it’s a bit tricky to keep things optimized and also allow to modify the footer in the later hooks. But I’ll figure it out. I’m most likely going to release a Total 4.6.1 small patch shortly and I’ll include this fix.

This has definitely been an issue for several versions now though no one had reported it, so thanks!

If you want email me directly to wpexplorer [at] gmail dot com and I will provide you with the patch as soon as it’s ready!

- AJ

Actually the fix is very easy! If you want to patch it yourself you can…Simply edit Total/inc/footer/core.php and locate the get_template_id() function and change it from this:

public static function get_template_id(): int {
    if ( null === self::$template_id ) {
        self::$template_id = 0;
        if ( get_theme_mod( 'footer_builder_enable', true ) ) {
            $id = get_theme_mod( 'footer_builder_page_id' );
            $id = (int) apply_filters( 'wpex_footer_builder_page_id', $id );
            if ( $id && 'publish' === get_post_status( $id ) ) {
                self::$template_id = $id;
            }
        }
    }
    return self::$template_id;
}

To this:

public static function get_template_id(): int {
    if ( ! get_theme_mod( 'footer_builder_enable', true ) ) {
        return 0;
    }
    if ( null === self::$template_id ) {
        self::$template_id = 0;
        $id = get_theme_mod( 'footer_builder_page_id' );
        if ( $id && 'publish' === get_post_status( $id ) ) {
            self::$template_id = $id;
        }
    }
    return (int) apply_filters( 'wpex_footer_builder_page_id', self::$template_id );
}

Basically we are just moving the filter outside of the cached check, this way it can be changed on demand whenever the function is called, but it will only run the status check on the initially set custom footer defined in the admin panel – which makes sense…no need to run these checks on user defined ID’s.

- AJ

Great. thanks. I did find a way around it by using the Custom Actions area (inside footer) to use a generic dynamic template, then use a new function to swap that out based on the custom post type slug matches. But i’ll try this in an older site that is using our original method.

Hi,

None of the theme demos use the WP-Forms plugin, so I’m not sure what you are referring to. The theme has it’s own simple Contact Form Element though which I use in some demos: https://totalwptheme.com/elements/contact-form/

- AJ

That’s what I see the one on the left, who and where is this defined?

I’ve sent a test email, but I don’t see anything come through to me email address (which is the admin for the site) sorry if I’m missing the obvious?

Hi,

The Contact Form element is added on the page itself via WPBakery so you can edit the page to modify the design, but it’s a simple contact form so you can’t add/remove fields (anything more would be best done via a 3rd party plugin).

By default, the theme’s Contact Form will send the email to the admin email address (as you mentioned) but this email can be modified in the main Theme Panel – https://totalwptheme.com/docs/contact-form-recipient-address/

If the form shows a green notice on submission letting you know that the the email was sent, but you didn’t receive any, most likely it’s going to your spam folder or your domain’s DKIM, SPF and/or DMARC records are not setup correctly. Because the green notice would only display if the email was sent by WordPress, thus it means the issue is on the receiving end.

This plugin can be helpful for testing to make sure emails are being sent correctly by your server – https://wordpress.org/plugins/check-email/ – so if the emails are properly sent, but not received then you know the issue is with either the domain records or with your email provider.

- AJ

Nope, I actually had a notice on the upcoming changelog because I specifically updated the plugins live so if you want you can delete and re-install them.

But I just finished Total 6.4 so you should be able to update any moment now as soon as it’s accepted by ThemeForest I will send out the notice to your dashboard – https://totalwptheme.com/docs/changelog/6-4/

- AJ

Awesome, thank you AJ! Looks like a brilliant update as usual.

Hi,

I’ve already patched Templatera as well, but technically Total overrides the Templatera code and the code in the theme has had this patch for years.

Total 6.4 is ready and you should see the notice to update any moment now – https://totalwptheme.com/docs/changelog/6-4/ – so you can wait for the official update to update Templatera if you wish. Also, most customers choose to not install or even use Templatera as it’s not really needed – especially since the introduction of Dynamic Templates in Total a few years back.

- AJ