Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter KC White

    (@kc-white)

    Oh, sorry I missed your other reply!

    Weird how those words got into the color settings. ?? Anyway, I’m happy to hear things worked out for you, too. ??

    Thread Starter KC White

    (@kc-white)

    Update:

    WooCommerce support explained briefly that woocommerce-base.less file, Line 2, outputs the primary nav UI styles entered in the General WooCommerce settings tab (“Enable WooCommerce CSS” must be checked to see/modify the styles).

    I had no idea you could even change the hex values in those boxes, but apparently the word, “Kristen” (my client’s name) made its way into the primary box vs a valid hex value (as illustrated by my support guy, Andrew, in the example here — https://d.pr/i/7cLG).

    WooCommerce support recommended installing a fresh copy of the woocommerce-bass.less file. I didn’t even have WooCommerce working on my site, so I downloaded v2.0.13 and uploaded the zip file via the WP dashboard.

    By reverting to a fresh copy of a previous version, I was finally able to reinstall WooCommerce. The next step was to reactivate the Genesis Connect for WooCommerce plugin. I immediately saw the prompt to update WC to 2.0.14, so I clicked the update link as usual, and this time, everything works just fine and WC is now up-to-date.

    Hope this helps the next person when troubleshooting a failed update.

    Thread Starter KC White

    (@kc-white)

    Ok, so it’s not just me. Sorry to hear you’re having the same issue. ??

    I bought a couple WC extensions to use as part of my project, so I was able to access their support desk and send in a support ticket.

    I got a reply this morning, but all they’ve done is request the file that’s causing the error (woocommerce-base.less).

    Anyway, once I find a solution, I will come back and reply. Please feel free to post here with a gentle reminder if I forget. ??

Viewing 3 replies - 1 through 3 (of 3 total)