Media Library widget InsertHandler callbacks are called multiple times.

Jacobo Gallardo

January 09, 2020 11:23

Hi,

 

I have a page where I can create media library widget multiple times:

```

newWindow.cloudinary.openMediaLibrary(

        {

          cloud_name: this.props.cloudName ? this.props.cloudName : '',

          api_key: this.props.apiKey ? this.props.apiKey : '',

          inline_container: '.container'

        },

        {

          insertHandler: (data: any) => {

            console.log('Insert image handler has been called')

          }

        }

      )

```

 

this code is executed within a react component.

 

Everytime I call openMediaLibrary it seems it is registering the insertHandler callback somewhere but it is not cleared up when I open another media library, and I can see that the handler executions are accumulated over time as I create new media library widgets (this happens also when doing createMediaLibrary instead of openMediaLibrary).

 

I would expect to clear the callbacks everytime we create/open a new widget. Or a close() method to add to show() and hide() so we can make explicit that we want to start clean again. Or simply a clearInsertHandlers method in the options?

 

Any feedback will be welcomed, this is preventing us from using the plugin in production.

 

Thanks in advance.

0

• 

  Daniel Mendoza

  January 09, 2020 18:03

  @Jacobo

  Can you please open a support ticket at https://support.cloudinary.com/hc/en-us/requests/new so that we go over specific details for a reproducible test case. Feel free to address it directly to me.

  Thanks.

  0
• 

  Jacobo Gallardo

  January 10, 2020 09:52

  Opened, thanks very much.

  0
• 

  Nikolaos Nikolaou

  January 10, 2021 20:45 Edited

  Hello,
  
  We are experiencing exactly the same issues, Has there been a solution or a fix? We are using it in an EmberJS component.

  Thanks

   

  0
• 

  Stephen Doyle

  January 11, 2021 14:18

  Hi Nikolaos,

  Amine opened a request on your behalf about this also and I replied to that request a few minutes ago. We don't currently have an ETA for when we can make changes to address this, but I've updated our internal task tracking the issue with your details so we can let you know of updates directly
  Regards,

  Stephen

  0

Post is closed for comments.