Hello Marko,
@vmarko Thank you for your support and I am sure if we’ll rollback to 2.1.6 or 2.1.7 it will works fine, since the issue occurred after updating to the 2.1.8 version. And sorry but I am not sure what file system do we have, but everything is deployed via git after testing on a virtual staging server and we use SSH if we want to change any files or update any plugins. hopefully this will help you.
we did reinstall the older version 2.1.7 on staging and it looks fine there is no issues occurring.
