Does your error message state that Loco Translate is the cause? If so, please post the full text of the error.
Loco Translate is a file editor. It saves MO files, and those MO files are loaded and used by your plugin. It’s very unlikely indeed to crash your website simply by being enabled, and isn’t known to “clash” with other plugins in the way you imply. If there is a direct conflict that causes a fatal error then I need to see evidence of this in order to do anything about it. Your website suffering a fatal error while the plugin is enabled is not itself evidence of this.
Much more likely is this – Incorrect translation formatting in your custom language files CAN crash your website when those translations are rendered by your plugin. I’m not stating this is the cause, but it’s possible and very common. You will have to find descriptive messages in your error logs to establish what is actually happening.
It can also happen that translation values are used by your plugin in such a way that an unexpected value would cause a fatal error. There is no limit to the possibilities of this, but it’s less likely than above. Again – error logs are required to debug it.
This is part of the code, perhaps that can help you understand the problem, even though Loco is not mentioned by name:
/customers/3/c/4/dansksolcelleservice.dk/httpd.www/wp-content/plugins/woocommerce-subscriptions/vendor/woocommerce/subscriptions-core/includes/admin/class-wc-subscriptions-admin.php. Error Message: Uncaught ValueError: Unknown format specifier “m” in /customers/3/c/4/dansksolcelleservice.dk/httpd.www/wp-content/plugins/woocommerce-subscriptions/vendor/woocommerce/subscriptions-core/includes/admin/class-wc-subscriptions-admin.php:1813
Stack trace:
#0 /customers/3/c/4/dansksolcelleservice.dk/httpd.www/wp-content/plugins/woocommerce-subscriptions/vendor/woocommerce/subscriptions-core/includes/admin/class-wc-subscriptions-admin.php(1813): sprintf(‘Betalingsgatewa…’, ‘
As I hinted, this is indeed a badly formatted translation. See Unknown format specifier from my earlier link.
Your stack trace shows you the start of the translation (Betalingsgatewa….), so you should be able to find it and correct the formatting amongst your custom translations. Looking at your error message, it will contain something like %m or % m (which would be invalid). Without seeing the full translation I can’t be specific about how to correct it.