Adrian

Just to understand, does this layers functionality do anything by itself in Indico for someone who's not using your UN plugin? I think it would be interesting to see if...

> Let me clarify this with my colleagues internally and I'll be back. And update on this?

Sounds good, I'm changing the PR to draft for the time being.

I'd separate it into `get_registration_documents`. Also make sure to not include files which aren't `is_published` (those may even be tests a manager did, so I'd treat them just like manager-only...

At least for *users* we support predefined affiliations in the backend, there's just no UI nor a general-purpose plugin that populates the table backing it. But it sounds a lot...

I think the problem when not populating the built-in affiliations table is that you will only have a string in the end, w/o any attached metadata... So you lose quite...

Oh wait, this is for registrations. Yeah, custom field in a plugin should work. I think making it a plugin is nice, and then we could see it it looks...

You have one level too much of nesting. Here's an example I used for testing when I developed the plugin field type functionality: ```js registerPluginObject(PLUGIN_NAME, 'regformCustomFields', { name: 'ext__color', title:...

Did you rebuild the assets? I just tested my code and it still works... Anyway, you may want to add some `console.log()` debug code or set a debugger breakpoint in...

I would start by having a look at what `getPluginObjects('regformCustomFields')` returns