BOOM! RC1: Unable to parse color from string

bymarkvig · August 31, 2019, 2:42am

Hi

After upgrade ti RC1 the site is not showing right in edit any more.

cs.js?ver=3.6.0-RC1-5c3c0df:74 Unable to resolve color: global-color:4c696e6b Error: Unable to parse color from string: global-color:4c696e6b
at new l (cs-vendor.js?ver=3.6.0-RC1-5c3c0df:6967)
at l (cs-vendor.js?ver=3.6.0-RC1-5c3c0df:6961)
at n (cs.js?ver=3.6.0-RC1-5c3c0df:74)
at r.lookupSingleColor (cs.js?ver=3.6.0-RC1-5c3c0df:77)
at cs.js?ver=3.6.0-RC1-5c3c0df:74
at Array.map ()
at r.lookupColor (cs.js?ver=3.6.0-RC1-5c3c0df:74)
at Object.color (cs.js?ver=3.6.0-RC1-5c3c0df:4794)
at cs.js?ver=3.6.0-RC1-5c3c0df:4795
at RegExp.[Symbol.replace] ()

I tried on two different sites … same issue.
Web cache and browser cache is cleared.

Cheers!

Georgich · August 31, 2019, 7:59am

All colors deleted from Color Manager. And cannot be saved. After saving and refreshing page they just gone. On the page all text colors becomes transparent.

JvP · August 31, 2019, 8:15am

Yup, all colors are gone from the Color Manager after updating to RC1.

JvP · August 31, 2019, 8:24am

Guys, it could be a browser cache issue, I cleared mine and the colors were back.

Misho · August 31, 2019, 8:33am

@JvP, in the backend too?

I have cleared all caches. Colors are visible on the front end, but all previously set Global colors are gone. Also some of them are not seen in the backend.

The way new global colors are being added has been changed. And it seems that this messed up old colors unfortunately.

JvP · August 31, 2019, 8:37am

Looks like I spoke too soon. They are gone again. Ignore my earlier comment. It’s broken

Misho · August 31, 2019, 8:41am

Shame. It will probably stay like that until Tuesday.

I am going to recreate a color with new names and assign them on the Landing Page I am building. That way, if the old one get restored in RC2, I will delete them as duplicates.

Since the colors are visible on the front-end, they can be be inspected. No need to go back to Beta 7.

Georgich · August 31, 2019, 9:10am

Just click ‘Save’ and they will dissapear from front-end (done it)… )) 700+ errors in console )

Georgich · August 31, 2019, 9:19am

Clicking ‘Save’ in font manager will kill them all on front end at all pages ))

Misho · August 31, 2019, 10:42am

Hmm, strange. Mine were gone, I have recreated them, saved, and now everything is good (Pro). There was no console errors after the update, and there are none now.

EDIT: I have jumped too early too. Although recreated and saved, all Global colors are gone again. All elements that are using them are transparent in the backend. They appear as normal on the front-end.

Georgich · August 31, 2019, 10:43am

Now i’m using CSS/Customize to colorize everything back )

Georgich · August 31, 2019, 10:44am

Check console errors in CS editor, not on frontend.

Misho · August 31, 2019, 10:57am

@Georgich yup. There they are. I thought I have checked the backend first time. It seems I haven’t.

EDIT: It is not just about the Global colors. I have just lost a Headline’s color, and whatever I do, it stays transparent.

scotbaston · August 31, 2019, 11:34am

Adding my name to the list… I had not created any colours on this project.

I went into the colour manager from Theme Options, set up news colours, saved them then set defaults for buttons etc. All worked fine until I went back into the colour manager and all the colours had gone… saved the ‘blank’ colours and voila loads of console errors.

I hope it is a simple fix come Tuesday

Georgich · August 31, 2019, 5:39pm

I got many headlines. Some of them colorizing only with ‘!important’, same for backgrounds.

RubberDuckers · September 1, 2019, 3:38pm

Just noticed this too on RC1 - loaded the site, colours were showing on front end but not in the editor, either in the colour picker or the actual elements themselves.
Re added the colours and set the page up again, disappeared.

sam_futr · September 3, 2019, 12:29am

@alexander - Can we get a brief update on this issue and resolution timing? Should we revert back to pre-RC1 in the meantime if we’re building out actual sites in Dev using Beta?

Cheers,
Sam

alexander · September 3, 2019, 5:45pm

Hi everyone. Working towards an RC2 to correct this by EOD.

alexander · September 3, 2019, 6:46pm

Quick update: Got this working. Was a race condition in some ember code I’ve been trying to relegate and eventually dismantle. The colors were getting sent into the application from the DB, but the color service wasn’t intentionally waiting for them to be made available and just assumed it was an empty array.

My apologies, if you clicked “save colors” after this bug was present your global colors will be overwritten with an empty set, or whatever new colors you created. The console warning means that an element is trying to use a color that no longer exists. It will use transparent instead.

To recover a color so you don’t have to go to every element again and fix it, you can open your developer tools and paste this into the console:

window.cornerstoneApp.lookup('service:store').createRecord('color-manager/selection', {
  id: 'c4f83002-736a-45c6-85f3-0b01c7457892',
  title: 'Recovered Color',
  value: 'rgb(0,0,0)'
})

Just update the ID to match the ID output in the console warning. Try this after we push RC2 later today.

alexander · September 3, 2019, 10:34pm

Update: RC2 is now available.