Just saw that v4.0.4 has been released. Has this bug been fixed in this release?
Hi,
Thank you for your prompt response! Unfortunately, no. I had to downgrade the plugin to 3.2.0 to get it to work. Maybe you can fix the issues in the next update of v4.