Mat

Hello @comopi ,

Thank you for using Hestia and apologies for the delayed reply!

Anchor buttons are usually used for the navigation on single-page websites so the user can experience a smooth scrolling effect from the top of the page to the clicked element section.

If you want to add anchors to your website, then please check our documentation here that shows exactly how it’s done.

Hello @comopi,

Thank you for your message and apologies for the delayed reply!

You can use CSS to achieve such a behavior even though we do not recommend this method usually.

You can start with the below CSS and then modify it as per your needs:

nav.navbar.navbar-default.navbar-fixed-top.navbar-color-on-scroll.hestia_left.navbar-not-transparent {
    height: 100px;
    background-color: red;
}

However, if you also want to change the elements within the navbar to adjust when scrolled, then you would also need to insert some JS to target each element and adjust it for the new dimensions.

Thank you for understanding and have an amazing day!

Hello @aivorasolutions ,

Thank you for your message and apologies for the delayed reply!

We have released a new version of the theme. Can you please update the theme and see if this version fixes the issue?

Thank you and we’ll await your response!

Hello @chamois_blanc ,

Thank you for your reply!

Optimole is a free plugin with a Quota indeed, as long as you don’t exceed that, you’re not being charged. However, if you exceed it, then you would need the PRO version.

Now coming back to the issue at hand, indeed we could improve this and I already informed our developers about it so they could implement it in future versions of the theme.

Thank you for pointing this out and have an amazing day!

Hello everyone ,

Thank you for providing the error!

Are you using the Contact component inside the header? If not, then can you please tell us what components you are using inside the header so we can try to reproduce the error?

Also, please provide the website URLs so we can further troubleshoot.

It is almost impossible to know what is causing these errors if we cannot see the websites themselves or have no other information other than an error message of a minified file.

Thank you for understanding and we’re looking forward to hearing from you!

Hello @idwikat ,

Thank you for confirming that the canonical issue was produced by a plugin conflict!

As for the H1 issue, from what I can see, the divs are different (mobile and desktop) thus I’m thinking you can hide the mobile one with CSS using the display:none command as a quick fix if you cannot find the cause.

I have tested this behavior on my testing instance and I couldn’t replicate it thus it must be some particular setting in your environment that produces this issue.

Thank you for understanding and have an amazing day!

Hello @sahadatuk21 ,

Thank you for your review!

We are sorry to see that you do not like our change but we do appreciate you taking the time to leave us a review with your feedback.

We are still offering the Starter Site Templates for Gutenberg for free but if you want access to the premium templates, then you’ll need the PRO version.

Also, you can still use Neve with Elementor as before, as the theme is fully compatible with that page builder, it’s just that we are not offering starter templates anymore with the Lite version of the theme.

Thank you and have an amazing day!

Hello @thetraininglady ,

Thank you for using Neve and for reaching out!

Can you please make sure to have the Vertical Setting for the Row Component of the Footer setup to the top? (screenshot)

Thank you and please let us know if that worked for you!

Hey @vteves2 ,

Thank you so much for your review! We really do appreciate that you find our plugin useful and your review helps a lot!

Have an amazing day!

Hello @saihttam104 ,

Thank you for using Neve and for reaching out!

It seems like the error is related to the menu-icon component but I cannot say for sure why that might be.

What I would advise is to backup your website first, then disable all plugins and see if you can update the theme without breaking the website (getting this error).

If that worked, then start enabling back plugins one by one and see at which point the website breaks. Once you identified the plugin that breaks the website you can replace it with another one or remove it if you don’t need those features.

If this didn’t work either, then can you please share the website URL with us so we can have a further look and see if we can identify the root cause?

Thank you and we’re looking forward to your reply!

Hello @aid45 ,

Thank you for using our plugin and for reaching out!

Yes, you can exclude pages from being under maintenance by using the Plugin General Settings.

What you need to to is go to the WP Dashboard > Settings > WP Maintainance Settings > Exclude Field > Enter the slug of the pages that you don’t want the plugin to work on > Save Settings. (screenshot)

In your particular case, you would need to exclude all pages except the one mentioned but it will work the same.

Thank you for understanding and have an amazing day!

Hello @sellmet ,

Thank you for using Neve and for reaching out!

When it comes to this particular scenario there isn’t much we can do on our end. What needs to be done is to have your variables updated to respect the new root declarations. You can try and roll back the theme to the version that was previously working then update the variables to the new spelling so your website is ready for the update and your users won’t have a bad experience during the transition.

We are sorry for this situation but whenever you are actively working on a piece of software, changes will be made in order to improve the product and we always recommend to our users not to modify the root files of the theme unless they know exactly what are the risks and benefits.

When a user decides to manipulate the original files and change them, they also have to take into consideration that along with updates of the product, their modifications might need updating too.

Thank you for understanding and hopefully, we are still cool!

Hello @wpkava ,

Thank you for using Visualizer and for reaching out!

Visualizer is not collecting any data about the user visiting the website thus it should be respecting the GDPR conditions. However, if you want to be completely safe that your website does not brake any rules, you can always instate a Privacy Policy pop-up that your users would need to accept before accessing the website.

You can use the Orbit Fox Plugin for that or any other Privacy Policy plugin to your liking.

As for your latter question, since you are using the free version, the call is made in the backend whenever the chart is created indeed.

Thank you for understanding and have an amazing day!

Hello there,

Thank you for your message and apologies for the delayed reply!

That option can only be modified if you modify the plugin files. I think you can access those options by going to Dashboard > Plugin File Editor > Open the Maintainance Plugin > Under Assets > JS > Scripts.JS file you should find the Contact Us form functions.

If you modify the setTimeout function there it should be working.(screenshot)

I have modified it to 6000 so it holds for 6 seconds, but you should input the value you need.

Also, please keep in mind that this change will automatically be overwritten when there will be a plugin update.

Thank you and please let us know if this worked for you!

Hello @cobra65 ,

Thank you for using Neve and apologies for the delayed reply!

We have noted this code and forwarded it to our developers for further analyzing. If the code proves to be a good implementation, then our team will make sure to include it in future versions.

Thank you for understanding and have an amazing day!