Forum Replies Created

Viewing 15 posts - 1 through 15 (of 15 total)
  • Avatar: Airtite
    Airtite
    Participant
    March 4, 2021 at 18:57

    I figured it out. The product short description somehow had an invisible Elementor section appended to it. That section contained a div with an id the same as the the swiper. Just redoing the short description fixed the problem.

    Avatar: Airtite
    Airtite
    Participant
    March 4, 2021 at 15:05

    Hello. Were you able to figure it out?

    Avatar: Airtite
    Airtite
    Participant
    March 4, 2021 at 09:32

    I disabled all nonessential plugins and cleared the cache. I can’t disable all plugins because this is a live site. The problem persists so I’ve added credentials to the private content area. Thanks.

    Please contact administrator
    for this information.
    Avatar: Airtite
    Airtite
    Participant
    February 12, 2021 at 09:56

    Sure. I’ve added the info in the private area. Thanks.

    Please contact administrator
    for this information.
    Avatar: Airtite
    Airtite
    Participant
    February 11, 2021 at 15:19

    I just duplicated the menu and assigned it to en_GB. Unfortunately nothing changed; the wrong menu is still showing up.

    Avatar: Airtite
    Airtite
    Participant
    February 11, 2021 at 15:11

    No, I haven’t done anything with multiple headers. Shouldn’t the just all default to the same header configuration?

    Avatar: Airtite
    Airtite
    Participant
    February 11, 2021 at 09:14

    Thanks for the link, but this doesn’t address my problem. My problem is very specific: the wrong menu content is showing up in the menu bar on the translated page.

    This one is right: https://airtitesmokers.com/product/airtite-smoker/
    This one is wrong: https://airtitesmokers.com/en-gb/product/airtite-smoker/

    Notice how the two header menus are different. In the second link, it’s actually the contents of the footer menu.

    Avatar: Airtite
    Airtite
    Participant
    January 20, 2021 at 12:08

    Hi. Did you get a chance to check it out yet?

    I’d think that this is unlikely to be a W3 Total Cache issue. The problem is the in-browser rendering time. The time to first byte is quite fast.

    Avatar: Airtite
    Airtite
    Participant
    January 19, 2021 at 08:59

    Sure. I’ve submitted the login details in the private content area.

    Please contact administrator
    for this information.
    Avatar: Airtite
    Airtite
    Participant
    January 13, 2021 at 19:58

    That fixed it. Any idea what caused this?

    Avatar: Airtite
    Airtite
    Participant
    January 13, 2021 at 19:48

    I ended up just using a native button with a link to /?add-to-cart={productid}. Seems to work fine.

    Avatar: Airtite
    Airtite
    Participant
    January 13, 2021 at 15:49

    Thanks for the offer, but I can work out the CSS to customize it.

    XStore seems to have options to customize about everything imaginable. Is there a specific reason you don’t have an option to customize the Add to Cart button?

    Avatar: Airtite
    Airtite
    Participant
    January 13, 2021 at 10:51

    Thanks for the link. I already fixed that yesterday. My site url was configured in WordPress to be http://, while I was accessing it with the SSL url starting with https://

    However, I’m now seeing an even stranger problem. I’m now getting a 404 when the font is downloaded becuse the url being fetched includes the fully qualified path of the font file. The path that is getting fetched is

    https://airtitesmokers.com/home/customer/www/johng115.sg-host.com/public_html/wp-content/fonts/lato/S6uyw4BMUTPHjx4wWCWtFCc.woff

    Notice the directory name in the path. It appears to only be happening for the font fiile. Any ideas how to fix this?

    Avatar: Airtite
    Airtite
    Participant
    January 12, 2021 at 19:55

    I uninstalled XStore and WPML. I then disabled and reenabled WooCommerce. After that I reinstalled XStore and WPML. It seems to work no. No clue what went wrong.

    Avatar: Airtite
    Airtite
    Participant
    January 12, 2021 at 17:18

    Yes, it’s still there. This starts to sound like a WPML bug then.

  • Viewing 15 results - 1 through 15 (of 15 total)
Viewing 15 posts - 1 through 15 (of 15 total)
We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.