juliadte

Hi there,

we had the same issue since we updated the plugin to version 1.16.
With the help of this thread we fixed the 403 error by editing the core file.

@duracelltomi Will this problem be solved by the next update so that we don’t have to edit the core file after each update? Before the update we never had any problems.

Thanks in advance