Viewing 15 replies - 16 through 30 (of 39 total)
  • 3 levels of caching, what are they please?
    And yes, I can understand this is driving you nuts!

    OMG its gone!!!
    What did the trick???

    Thread Starter TechDepot

    (@techdepot)

    Hi Annie,

    Rolled back to 2.1.8 and deactivated customizer, Everything looks fine from my side. Can you please confirm?

    Thanks

    Thread Starter TechDepot

    (@techdepot)

    Autoptimize, W3 Cache, Site Ground SG Cacher (Host specific)

    Thread Starter TechDepot

    (@techdepot)

    Ok, will now activate Customizer and see.

    Fingers crossed, still looking good here!

    Thread Starter TechDepot

    (@techdepot)

    Ok… I can now say it officially… It is the upgrade..

    Well, its back now….

    What did you do latest? Activate Customizer I quess?
    If so this one is causing the issue even with storefront 2.1.8!

    Thread Starter TechDepot

    (@techdepot)

    No, Customizer is not activating… dunno why.

    What I did is upgrading back to 2.2.3

    Will fall back to 2.1.8 once more to confirm.

    Thread Starter TechDepot

    (@techdepot)

    Ok… I rolled back to 2.1.8 and all is ok now

    I confirm it is the latest Storefront Upgrade… Has a bug.

    Thread Starter TechDepot

    (@techdepot)

    Actually. I think it started by 2.2.0

    Hi,

    Hmmm, this does not have to mean its an actual bug in Storefront. I have about 40 sites and shops running on Storefront and they do not have issues even with the latest version 2.2.3.

    If I understand correctly, the woocommerce customizer ( third party plugin ) is now deactivated and can no longer get activated eather?

    Was the woocommerce customizer ( third party plugin ) activated when you had the 2.2.3 back too? Or are these issues only if that plugin is ative?

    It can still be some conflict with some other plugin..
    Best advice always test new updates in a staging site, not live. If things go south in staging, you can first fix that before messing up the live shop!

    Annie

    Thread Starter TechDepot

    (@techdepot)

    Hi Annie,

    The customizer is deactivated even if I want to activate. It states the Plugin Activated, but it is not. Rolling back to 2.1.8 no error. Upgrade to 2.2.X error.

    Best regards

    So even if on 2.1.8 the ( and you have no errors ) the third party customizer is not really activated, yet it says it is?

    That does not sound healty one way or another.
    Contacting their support might help solve this.

    Annie

    Thread Starter TechDepot

    (@techdepot)

    Hi Annie,

    I deleted the customizer plugin and tried to re-install and had same problem, so I deleted it and removed the folder, re-installed, all ok now.

    Rolled back to 2.1.8 now.

Viewing 15 replies - 16 through 30 (of 39 total)
  • The topic ‘BUG? – Home page buttons show script in Chrome’ is closed to new replies.