Conflict with Loco Translate plugin

[actuallyakash]

Reproduction Steps

Loco Translate can't find the translation file when the user has selected the "custom" location.

• Use Loco Translate to localize LifterLMS.
• Choose a custom location
  https://share.getcloudapp.com/OAuoyPlm

Expected Behavior

Loco should be able to correctly localize LiterLMS picking the translation file from the selected custom location.

Actual Behavior

Loco Translate can't find the translation file when the user has selected the "custom" location.

Possible solution?
[from @dominiquemariano ]
When Loco Translate is installed, instead of looking at wp-content/languages/lifterlms/lifterlms-en_US.mo, we should look at wp-content/languages/loco/plugins/lifterlms-en_US.mo when the user selects a "custom" location

System Information

LifterLMS 7.1.4
WordPress 6.2
Loco Translate 2.6.4

This issue has been recreated:

• Locally
• On a staging site
• On a production website
• With only LifterLMS and a default theme

Related User Information

https://wordpress.org/support/topic/loco-translate-not-working-as-expected/#post-16704935

[eri-trabiccolo]

[from our slack conversation]
Loco Translate works with plugins and themes without the need for them to do anything special.
If it doesn't work for us it means that we might do something unusual. I would focus on understanding this, and if we can safely "revert" this behavior, only if we can't I would consider a possible compatibility layer for Loco Translate.