RiverCityWordGuy

It turned out to be specific to the theme. I could add nav links using the site editor (like any block) and have them show up in the preview, but nav links would only be visible on the live site if they were added using the “+” button in the preview.

Discovered through trial and error.

Thanks for the effort on this. In the interim, I went back to the page and found that *all* custom colors had been removed from the objects where I had assigned them. (The custom palette still existed, but not the object asssignments.)

As a test, I swapped browsers to Safari and everything worked fine. So, I’m going to put this down to an incompatibility with the original browser (Edge) instead of a theme issue.

Thanks again!

• This reply was modified 2 years, 6 months ago by RiverCityWordGuy.

Thanks for the response/questions. Here are my answers:

WordPress version (e.g. 6.0.2 is latest)
I am using 6.0.2

Is Gutenberg plugin active? (if yes, what version)
No

Other active plugins?
WP Maintenance Mode & Coming Soon
Yoast Duplicate Post

What are the objects that you assigned the custom colors?
Groups and Columns

Are the objects core blocks or blocks from a third-party plugin?
Core

How are the colors assigned? (e.g. text color or background, or some other block plugin’s own color option?)
Colors are assigned to background in a Column that contains text blocks, image block and button block
Colors are assigned to background in a Group that contains columns, text blocks and button block

FWIW, I reduced my custom palette to four colors – in case that was a limitation. There are nine colors in the original theme plus four custom = 13 colors, total.

What you describe is the use case I had in mind: The entire blog is CC license by default and I would like to have the footer appear throughout the site (including home page). The option you mention would be a welcome addition.

Of course, there probably needs to be some way to suppress or modify the widget if it appears with blog posts in this scenario — but that goes without saying.

Thanks for the update. It’s still an issue for me, even after moving to a different version of my theme.