Hi, helpful people,
Searched and could find no reference to this. I just added a text box and while the default color for text is black, it stubbornly appears green. I can choose other colors, but the 'default black' box gives green now and I cannot get it to change back. And a nearby text box (code object) now also shows green, though I did not do anything to it and it was black previously. I have temporarily 'fixed' this by tinting the text in the offending box a deep blue. I tried deleting and starting fresh, but same thing happens. Selecting a custom text color and adding it...gives green, not black.
Any ideas on what is happening and how to repair it? Or will this wear off as St. Patrick's day gets further away?
Thank you.

Can you post an example?

Try taking the sunglasses off

If it's not the sunnies, do you see the colors the same in both the workpage and preview views? I gather you are selecting a color that looks black in the text editor font color selector -- but when you view it on the workpage with some actual text, it then looks green?

Might be worth re-booting your computer too -- if you haven't already. Ssometimes that can fix strange problems like this...

I'm a rose-tinted glasses gal myself. but, yes, it appears green in both cases even after re-booting. The color chart #'s are correct for black as well. I've wrestled the one text box down to a deep indigo, but the other (the 'last-updated') is still green--take a peek here if you would: Paradise Gardens Rare Plant Nursery
-the other affected text box is the one with the plant collections in it.

This happened once before last fall and only disappeared when I dumped the page and started fresh. I don't want to do that here!
Thank you--

The "last updated..." text is a code object. The code you have placed in it appears to have code that makes the text green. i.e. <FONT color="#004000" ... >

There is no closing </FONT> after the </script> tag for that line which would explain why other parts are turning green.


The 'blooming...' text appears to be blue because blue was selected. Try to 'select all' text from the text editor's Edit menu and then choose a color.

The weird thing is that the code object was black originally and I did nothing to it. It changed with the other box.

It turned green when the other object did--I've changed that one to blue (because I can't currently make it black)--when I try for black I get green.

When I try any new text item, I can't make any text black; any color except black works, but black is green.

If I highlight text in any other text box and try for black, it turns green and I can't change that back, either. So it feels like the color-choosing box has a problem. In the edit-text box, all looks well, but in preview or in actual view, there's the green.
?????

That's the thing about adding your own code, if the code is not good, or you make a typo, you can get all kinds of seemingly magical behavior.

Because the code object has an opening <FONT> tag but not a closing </FONT> tag, all text after that code that is not given an explicit color (i.e. that is not left black) will use the color defined in the unclosed <FONT> tag. (i.e. #004000 or dark green)

So... first close the FONT tag:
put </FONT> in the code object on the line just after </script>


Then change the color number in the code object from color="#004000" to color="#000000" to make it black.

Thanks for the tip, Harpo, closing the font tag fixed the color leakage. As to how the 0000000 got changed to 004000, I have no idea but it's behaving nicely now. And thanks to you I discovered that there are color charts 'out there' where I can see what the 00's mean.
Aaahhh.

Indeed. I figured that out already--but still am mystified how a blob of code that had been fine for 9 months suddenly went bad. I hadn't done anything to it except drag it across the page. Can code be that touchy? (Will moving it again possibly change its color again?)
Where are the code objects fire-tongs?
Thanks. . .

The performance of code with a missing closing tag will vary depending on where it is on your page.

Possibly the closing tag was always missing. The code was in an OK position before, but after you moved it, it was in a non-OK position. Just a theory