Parse Error When Updating to/Installing WooCommerce 2.0.14

Resolved KC White
(@kc-white)

10 years, 7 months ago

I’m using WP 3.6 in addition to Genesis version 2.0.1 on a client site.

We were doing just fine with WooCommerce until updating to WC version 2.0.14 (we were previously using whatever version came before).

After the update, I got the following error message the next time I tried logging into the WP admin…

Could not compile woocommerce.less: parse error: failed at @primary: #Kristen; /home2/kristen/public_html/fun/wp-content/plugins/woocommerce/assets/css/woocommerce-base.less on line 2

I deactivated the entire plugin folder via FTP by temporarily renaming it so I could regain access to the WP dashboard.

Then I reactivated plugins one by one and everything works just fine, except when I try to activate WooCommerce. I get the same parse error message (but since the plugin is not active, I can still log in to WP admin, thankfully).

I’ve tried deleting the entire WooCommerce plugin file and manually uploading a fresh copy of version 2.0.14, but the error remains when trying to activate the WooCommerce plugin.

Not sure if it’s also worth mentioning, but I was using the Genesis Connect plugin for WooCommerce before the failed update. As I understand it, WooCommerce should be activated first, so I have not reactivated Genesis Connect yet.

Can someone provide some insight? I’d truly appreciate it.

http://wordpress.org/plugins/woocommerce/

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

kims126
(@kims126)

10 years, 7 months ago

I have this same issue. I’m also using the Genesis Connect plugin (v. 0.9.5) as well. Going back to version 2.0.13 for now until resolved.

Thread Starter KC White
(@kc-white)

10 years, 7 months ago

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. 🙂

Thread Starter KC White
(@kc-white)

10 years, 7 months ago

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 — http://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.

kims126
(@kims126)

10 years, 7 months ago

Thanks for posting KC! I reverted back to 2.0.13 but before doing that, I had tried to reuploaded the woocommerce-base.less file and it didn’t fix things. Perhaps I need to do things in the order you mentioned above. I’ll give it try myself.

kims126
(@kims126)

10 years, 7 months ago

well, I updated to 2.0.14 again and still received the error. I tried reuploading the woocommerce-base.less file again and overwriting the old one. I still get the parse error.

KC – did you deactivate the Genesis Connect plugin before updating Woocommerce? I had reverted back to 2.0.13 and saw the “update” prompt so I clicked update and I still get the error. Trying to figure out what I’m doing wrong?

My error points to line 11:
parse error: failed at @contentbg: #transparent;

kims126
(@kims126)

10 years, 7 months ago

AHA! I figured out the issue. In my case the word “#transparent” was in one of the color settings fields. I changed it to #fff and saved. Then I updated the plugin and all is good!

Thread Starter KC White
(@kc-white)

10 years, 7 months ago

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. 🙂

gmkatopodis
(@gmkatopodis)

10 years, 5 months ago

I have followed all of these threads regarding this error..but I still can’t get anything to fix the woo-commerce plugin. The error I am getting is below.

Could not compile woocommerce.less: expected color value: failed at .vertical_gradient( lighten( @secondary, 2 ), @secondary ); /home4/mollyalo/public_html/wp-content/plugins/woocommerce/assets/css/woocommerce.less on line 29

Any suggestions???

Andrej Pavlovic
(@andrejpavlovic)

10 years ago

I just ran into the same issue upgrading to version 2.1.6.

Enabling/disabling of plugin or reverting to an older version will not fix this issue since the issue is with an invalid value in the database.

For those looking for a fix, you can run the following SQL statement directly on the database:

UPDATE wp_options SET option_value = 'a:5:{s:7:"primary";s:7:"#ad74a2";s:9:"secondary";s:7:"#f7f6f7";s:9:"highlight";s:7:"#85ad74";s:10:"content_bg";s:7:"#ffffff";s:7:"subtext";s:7:"#777777";}' WHERE option_name = 'woocommerce_frontend_css_colors'

This will reset the css color values which are used by the less file.

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

The topic ‘Parse Error When Updating to/Installing WooCommerce 2.0.14’ is closed to new replies.

Tags