Why am I getting the error that message that I have macros in the header?

[Andy Webb]

Within about the last week all my pages have these error messages.

"The following macros are not currently supported in the header: style"

and similarly at the bottom 

"The following macros are not currently supported in the footer: style"

We didn't add any macros to either the header or footer so far as we know.

Tried this in both Chrome and Edge and get the same errors.

[Michael Berman]

I fixed this error by doing the following:

1. Click on "Space Tools" (under Overview and Pages in the main space left hand menu)

2. Click "Look and Feel" sub-section

3. Click "Header and Footer" tab

4. In the Header box, delete:

{style}
.page-metadata, #breadcrumb-section {display: none;}
#system-content-items {padding:0px !important;}
{style}

5. Refresh browser

Note: I had multiple spaces, and had to repeat the above for each space.

[Amanda Burma]

This solution works!

[Vimal Patel]

Thank you.  That worked.  I deleted my style macros.

[Marcel Wilson]

We started getting it and I think I know why, but the error is confusing.

We have some override CSS that we put at the site level footer (this is because atlassian took away all the color settings in the new layout).  When I remove the {style} from the site footer the error goes away, but so too does the CSS override.

The confusing thing is the error says the macro isn't supported but it still seems to be functionally working.

[Andy Webb]

Thank you.  That worked.  I deleted my style macros and the errors went away.

My macros were meant to hide features I didn't like.  In my case, Atlassian decided to get rid of the things I wanted to hide so it didn't matter.

[Andy Webb]

For those wishing to make changes Administrator rights are required.  xxxxxx.atlassian.net/wiki/admin/custompagecontent.action

[Marcel Wilson]

It is possible for those custom header and footers to exist at the space level as well. 

https://xxxx.atlassian.net/wiki/spaces/custompagecontent.action?key=YOURSPACEKEY

[Ambika Elangovan]

This works! My header had the below customization and Removing it resolved the macro style error.  

{style}
code {
padding: 1px 5px 1px 5px;
font-family: Consolas, Menlo, Monaco, Lucida Console, Liberation Mono, DejaVu Sans Mono, Bitstream Vera Sans Mono, Courier New, monospace, serif;
background-color: #eeeeee;
}
{style}

[James Gill]

Same, started sometime either yesterday or the day before.

[Josh Lambright]

I'm also seeing this.

[Ian Hulme]

I am seeing it as well. I have no idea how to get rid of it.