rachid93

After some investigations, it seems the problem was not related to the plugin itself but rather some customization we did on our end that I missed.

Closing this thread as it is resolved.