Global color returns wrong value

[miguras]

Hello. I noticed today that all my extensions return a wrong value when a global color is used. This happens only in some fields and can't figure it how to solve it. For example, i have an extension named elegantshop, that has multiple color settings, some of them returns the proper value if a global color is used, and others returns something like "gcid-fce83346-c5d2-4304-a9b3-755d1753d775" . looking in the code, i found this is the way divi stores the global colors, and then through some functions this id's are replaced with the proper value, but this not happens as it should. I also ran some basic tests in some other plugins made by others developers, to discard that not happens only to my complements, and it happens in all of them.
I appreciate any orientation on this.

Greetings!

[mrcbt]

was this ever fixed?

[jcdotnet]

Same here, it seems to be happening in all 3p extensions.

I just received a support ticket from a customer and I have found this:

background-color: gcid-b412ef92-e4a7-4cd0-b405-f6b2cc8cbc0d

The background color is working in the Divi Builder, but not in the front-end. They seem to be using a global color and I don't know right how to solve this or what to say them.

Any help on this? Thank you!

[artneo-io]

I'm running into this same problem as well, anyone managed to solve it?

[Update] I kept searching online and this post helped me out: https://support.divizoom.com/docs/how-to-use-the-global-color/

This issue was happening to me only in a certain part of the menu, so I solved it by accessing the Divi Builder and manually updating the color from that odd code to a new one.

[LRLMike]

I found this when searching for this issue, so thought I would post the solution here given that Elegant Themes official support told me that these gcid values were nothing to do with divi which returns hex codes or RGB values, and must be from a third party component.

Here is the code from a built in module showing how they read values from the color field:

        $background_color = $this->props['background_color'];
        if ( strpos( $background_color, 'gcid-' ) === 0 ) {
            $global_color_info = et_builder_get_global_color_info( $background_color );
            return esc_attr( $global_color_info['color'] );
        }
        return $background_color;

it is therefore a requirement for module authors to include something similar to the below:

		if ( strpos( $this->props['heading-colour'], 'gcid-' ) === 0 ) {
			$this->props['heading-colour'] = et_builder_get_global_color_info( $this->props['heading-colour'] )["color"];
		}

The official examples do not do this processing, and as far as I can find there is no documentation on this. Modules that do not properly handle this condition will apparently work most of the time but then for some reason which I have not determined will randomly not work on a new site set up with the same plugins. The fact that the built in modules do this check suggests this is normal behaviour that should be documented somewhere.

I have given a link to this thread to Elegant Themes support, so hopefully they will update their documentation to inform module authors how to handle these fields correctly.