Using Open UI extension on document type field

Experience Manager (PaaS/OnPrem)
1

Hi guys, I am very glad that in v13.2.0 the open UI functionality has been extended on the document fields (https://documentation.bloomreach.com/library/concepts/open-ui/configure-a-document-field-extension.html). Hence now I am trying the steps as mentioned in the documentation and I found also https://github.com/bloomreach/ui-extensions/tree/master/samples/bynder
The only drawback is that after the steps I followed, as mentioned in the samples, I do not see a button on the openUI field in the document. Do I miss something?
Extra information: I am using archetype v 13.2.0. And the extensions files I’ve deployed in a separate apache web server (locally). When a connect to the index via the browser I can see the button.

regards
Ricco

2

Never mind guys…I solved it.
regards
Ricco

3

Hi ricco,

Which steps did you follow? I just tried the steps explained at https://github.com/bloomreach/ui-extensions/tree/master/samples/bynder and that works fine.

To get the example document field extension working, follow the steps at https://documentation.bloomreach.com/trails/open-ui/develop-a-custom-page-tool.html and use the HTML and JavaScript example in the code example at https://documentation.bloomreach.com/library/concepts/open-ui/develop-a-document-field-extension.html instead. The “custom page tool” example use a local webpack dev server to “host” the extension’s files locally. For production the extension can be hosted anywhere, preferably at a different origin than the CMS itself. In case of the Bynder extension the code is hosted using Github pages (https://bloomreach.github.io/ui-extensions/samples/bynder/). Just make sure the “frontend:url” property of the extension’s configuration points to wherever your hosting it.

hope that helps,

Mathijs

4

Hi Mathijs, thanks for your response. The problem was that I was using my local apache web server, which was not configured correctly. While using Chrome gave me odd errors in the browser’s console, while trying to open a dialog extension. Which did not help while trying to figure out what was going wrong. But swithing to using Firefox gave me better info, what was going wrong. And now it is working.
regards
Ricco