Unknown macro [profile]

[MidnightExe]

Hey everyone,

Has anyone encountered an "Unknown macro: {profile}" error after disabling the Linchpin User Profile app?

We recently deactivated the Linchpin User Profile app within our Confluence instance, and we're now seeing this error. We wouldn't expect disabling the app to cause this specific macro error.

Any insights or solutions would be greatly appreciated!

Thanks in advance.

[Roma Bubyakin _Wombats Corp_ · Accepted solution]

There are 3 ways:

1. Enable app back (but if disabled, it was done for a reason)

2. Clean up data on the DB level (required careful testing)

3. Create a User Macro that will substitute the original with the exactly the same name (recommended)

[MidnightExe]

Hei @Roma Bubyakin _Wombats Corp_ 

is there an instruction on how to do that? 

Thanks!

[Roma Bubyakin _Wombats Corp_]

This is the starting point:

https://confluence.atlassian.com/doc/writing-user-macros-4485.html

Try to create simple hello-world macro w/o params and with the exactly the same macro name: "profile"

Save it and reload the page.

Expected result is to see a lot of "hello worlds" there.

Next steps could be

* Render nothing, which will just hide lost macro from users

* Mimic the original one, which will require introducing same user parameters as in original macro, and use their values.

[MidnightExe]

So, I created a "profile" macro with the title "Hello world" and yes now I can see a lot of "Hello worlds" there. 

*Changing the Render is not showing any changes to the People Directory. 
*Quick question. Is it possible to mimic the original one without enabling it? And if so, how am I supposed to do that.

Thanks in advance!

[Roma Bubyakin _Wombats Corp_]

You can just delete "Hello World" from the template and leave it empty.
As a result, you will see a lot of nothingness instead of errors.

The second option to mimic the original one is a bit harder.
You will need to take a look at the page storage format. There you will find an XML element of your macro, something like:

<ac:structured-macro ac:name="profile" ac:schema-version="1" data-layout="default" ac:local-id="079dce3c-082f-490b-8ce0-f1efc2813e81" ac:macro-id="f6b3971f46324e3d2fc103c7741f9f364725accecc8032f4bd69aa82a458f552">
  <ac:parameter ac:name="param1">value of the first parameter</ac:parameter>
  <ac:parameter ac:name="param2">321231</ac:parameter>
</ac:structured-macro>

In this example, you can see param1 and param2 their values define how the macro will look on the page.

The idea is to create in your macro parameters with the same names/types/etc.
It might be something like the following:

## @param param1:title=Param 1|type=string
## @param param2:title=Param 2|type=int

First value: $paramparam1<br>
Second value: $paramparam2

Having a profile macro, it might be type username
More details on using parameters here: User Macro Template Syntax 

After correctly getting values of all parameters, you will be able to recreate your macro in the same way it was previously or in your own way.

Regards, Roman

[MidnightExe]

FYI --> Basically we solved the problem by restarting Confluence. All of the Profiles are back as normal. For me, thats a really weird behaviour. 

@Roma Bubyakin _Wombats Corp_ Thannk you so much for your help in this case. 

[Roma Bubyakin _Wombats Corp_]

Happy to hear that!

Stay safe,

Roman

[Robert Krause]

You can enable the native profile macro of Confluence. Linchpin overrides the native macro, so it gets deactivated. However the setting are compatible and the native macro can be reenabled.

[MidnightExe]

Hei @Robert Krause can you tell me where to enable the native profile macro of Confluence?