Import fails without feedback, file translations being deleted on publishing
See original GitHub issueMy laravel.log
file registers this error each time I use the Import all or Import from the webUI. I get no feedback in the webUI from that error, it just does nothing.
[2017-05-24 18:19:49] staging.ERROR: ErrorException: file_exists(): open_basedir restriction in effect. File(/) is not within the allowed path(s): (/var/www/vhosts/mydomain.com/:/tmp/) in /var/www/vhosts/mydomain.com/d550.mydomain.com/vendor/vsch/laravel-translation-manager/src/Classes/PathTemplateResolver.php:328
So the existing translations in the files are not being imported, and when I publish the new translations the old ones are being deleted because they are not registered in the database.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Paragraphs translations aren't updated when imported with ...
Paragraphs translations aren't updated when imported with file import (with Auto accept finished translations enabled). Closed (fixed). Project:.
Read more >Common Errors with Exporting and Importing Translation Files
Troubleshoot issues you can encounter while exporting and importing files in Translation Workbench.
Read more >Failed to import return package because you created it yourself
I have Trados Studio 2015 and have hired translators to translate some of my books that originate from InDesign.
Read more >Export & Import Jobs for Offline Translation
The most common reasons for a failed string import are that tags used in the offline translation are not supported in Smartling for...
Read more >Import solutions - Power Apps | Microsoft Learn
The most common cause for an import to fail is that the solution did not contain some required components. When you download the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@gerardreches, new version released with a fix for this bug.
Solved in 2.4.22, thanks @vsch !