Search Results for 'cache'

[Hannah]

Hannah

#221073

Hi Smith,
After clicking the open in new tab checkbox are you clearing your cache?

Hannah

[therapyforlatinx]

therapyforlatinx

#221027

I also cleared the cache, and updated the theme. It’s still not working.

[Hannah]

Hannah

#221018

Hey,
What version of page builder do you have running? And also what version of the theme? Have you tried clearing your cache?

Hannah

[Kevin]

Kevin

#220950

Hmmm, that doesn’t sound right. The option to clear your cache should be present in your admin topbar by default if that plugin is active.

If you’d like, you can post a login in a private reply and I can take a look for you.

-Kevin

[Ekaterina]

Ekaterina

#220949

Thank you Kevin,
I have WP Super Cache installed, unfortunately there is no signed for ‘clear cache’ neither on the top of menu or settings.
You are right, the content within elementor saving in the admin but not showing on the front end.

[Ekaterina]

Ekaterina

#220947

thank you, the link is https://helianthusclinic.com/about/acupuncture/
Could you please remind how to clear the site’s cache.

[Kevin]

Kevin

#220946

Hello,

did you clear your site’s cache after making the changes? Can you post a link please?

-Kevin

[Hannah]

Hannah

#220757

Hi Smith,
You should be able to go into your post edit pages and open the Discussion tab to deselect Allow Comments. Does this not work for you? Make sure you are clearing your cache.

Hannah

[Ohis]

Ohis

#220721

Am not using a cache plugin yet.
I only do that when my site is in production.

[Kevin]

Kevin

#220720

Are you running a cache on your site? If so, did you clear it after adding the CSS?

-Kevin

[Kevin]

Kevin

#220587

I’m seeing the images show now. Make sure to clear your cache if you have one on your site at the moment.

-Kevin

[Ben Ritner]

Ben Ritner

#220515

I turned off the handling of JS (it’s more of test). What likely really means is you likely were not clearing the minify cache after you activated a plugin or updated a plugin or theme. You may not want to enabled Fast Velocity Minify unless you truly know how to use it and that it’s critical that with any update to the js on your site that plugin gets cleared.

Ben

[Hannah]

Hannah

#220481

I believe this is due to your caching plugin. Are you tied to WP Super Cache? It is not one that we typically recommend. We love WP Rocket, or for a free option, we like cache enabler (https://wordpress.org/plugins/cache-enabler/).

Hannah

[paul]

paul

#220433

When I log in on desktop and delete the home page cache the mobile version is then visible on the mobile. Then when I log out again the mobile version is visible on the desktop. Really odd.

[Ben Ritner]

Ben Ritner

#220406

Ok, Here is what I saw:

when I first went to your site it was broken, I thought you must have already updated the theme but then I found the older theme there. I looked at what was broken using the dev tools in chrome and looked through the console errors. I found several JS errors on your site. All related to javascript functions that couldn’t run when they were supposed to. I was curious and so I looked at your non-staging site and I also see those same errors: https://www.refreshskintherapy.com/ the page doesn’t load when I view it in chrome.

That got me looking at your plugins and there I found two plugins that do the same things and should never both be used on one site. Autoptimize and Fast velocity minify. Looking in both plugins setting there were several settings that I would not advise using especially with all the things you have running on your pages (popup, cookie consent for some examples). I turned off the deferring JS settings, in particular, deferring JQuery and the settings to cache admin pages (that creates really crazy minify files because while logged in lots of plugins (jetpack) and even WordPress load scripts that should only be run on the admin).

I deactivated Autoptimize since you don’t need it, it wasn’t helping anything because you have Fast velocity minify. So just working with the Fast velocity minify settings I got things to work consistently while leaving the parent theme active, I updated and cleared the minify and confirmed that with the cleared cached and minify settings correct things worked.

I then reactivated your child theme and hit some new errors where again your home page wouldn’t load.

I found this in your child theme functions file:

// Defer Javascripts
// Defer jQuery Parsing using the HTML5 defer property
if (!(is_admin() )) {
    function defer_parsing_of_js ( $url ) {
        if ( FALSE === strpos( $url, '.js' ) ) return $url;
        if ( strpos( $url, 'jquery.js' ) ) return $url;
        // return "$url' defer ";
        return "$url' defer onload='";
    }
    add_filter( 'clean_url', 'defer_parsing_of_js', 11, 1 );
}

I remove it, I strongly suggest you leave it out. You already have a plugin to manage all this and manage deferring scripts adding a function only created confusion and conflicts.

I also deactivated this plugin: Remove Query Strings From Static Resources (that also is a duplicate conflict creating thing because you already have a plugin that controls this Fast velocity minify).

So now things are looking better but still won’t load because of errors and one was coming from a script added by this plugin: WooCommerce – Gift Cards

I looked and it hasn’t been updated in 6 months, not great reviews either. I suggest looking for a replacement.

For now though and since I doubted the author would get back to you quick I went in and manually fixed the plugin to work.

Last but not least your child theme is overriding the base.php file. Which is not something I suggest, in terms of adding scripts into your site we have a tool for that in your theme options > header and footer scripts. The base you had created was out of date and the last part of why when you updated everything was breaking. I’ve fixed that and moved your scripts into the theme options. I suggest remoing base.php from your child theme.

So now your site is updated, the theme is to 4.9.4 and I’ve massively cleaned up what is running and kept all the speed improvements you were going for.

You still have two errors on your site, they don’t prevent the page from loading but I don’t like to ignore errors.

Both errors have to do with your script you are adding in the header to load this file: https://az416426.vo.msecnd.net/scripts/JavaScript/JavaScriptSDK/ajax/ajax.ts In that file there is an error. It’s possible this is because of your staging site but I don’t know why you are adding that or what it’s doing for you so I figured I would just alert you to this. To see it simply right click, click inspect and look at the console tab. You will see an ajax error and the source is the link I posted which is coming from the scripts you are adding (previously through the child theme now through the theme options > header scripts).

The next is this error:1 POST https://dc.services.visualstudio.com/v2/track 400 (Invalid instrumentation key)

Again I don’t know why you are adding so I can’t guess as to why the errors and how to fix but you should know that there are errors in the console.

I really hope this is clear and is helpful. I understand it’s a lot if you wish for me to update your live site with all these changes I would be happy to.

Ben

[Kevin]

Kevin

#220324

I don’t see the CSS in your custom CSS box. Did you clear your cache after adding it?

-Kevin

[Kevin]

Kevin

#220304

If you are compressing your images and following the steps outlined in this post:
https://www.kadencewp.com/need-for-speed/

Then caching will have less of an effect on that page.

If you are using two different sliders, one for mobile and one for desktop, then you can’t run a cache on your home page. Otherwise only one slider will be loaded.

-Kevin

[Peggy]

Peggy

#220280

This reply has been marked as private.

[Juan]

Juan

#220186

This reply has been marked as private.

[Hannah]

Hannah

#220170

Hey,
Did you clear your cache after making these changes? If you want to send login info I would be happy to take a look. You can set as a private reply.

Hannah