Follow-up for #1804702-82: Display interface translation status (See also comment #76.)
Also follow-up for #1804688-101: Download and import interface translations (See also comment #119-123)
[was there another issue Gabor opened related? list it.]
Problem/Motivation
Some people get an error, some do not.
Proposed resolution
No proposed resolution yet. More investigation needed.
Remaining tasks
- Investigate more.
- Document steps to reproduce that work for everyone or describe the conditions in which the error happens and when it does not (like permissions, or directory group owner).
User interface changes
(new or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text)
API changes
(API changes/additions that would affect module, install profile, and theme developers, including examples of before/after code if appropriate)
Comments
Comment #1
yesct commentedComment #2
yesct commentedProviding a lot of detail here as we try and track down why I have this problem but Sutharsan does not.
Lets get a few more people to try it also.
I have a mac with MAMP 2.0.5, PHP Version 5.3.6
Eliminating as many variables as possible by doing it totally from scratch.
0. from scratch
git clone --recursive --branch 8.x http://git.drupal.org/project/drupal.gitThat should be equivalent to (making sure to get rid of config files left over from a previous install)
git checkout 8.x
git pull --rebase
git reset --hard
sudo rm -r sites
git checkout sites
1. check files directory
ls -l sites/defaultshows just the default settings.php file. no files directory.
2. install
drush -y si --account-pass=admin --db-url="mysql://root:root@localhost/d8-patch" --site-name=8.xThat should be equivalent to installing in the ui.
3. check files directory
ls -l sites/defaultis different, including
drwxr-xr-x 5 ctheys staff 170 Dec 8 14:24:41 2012 files/
ls sites/default/filesshows no translation directory (as expected)
4. the files configuration page before enable locale
5. enable locale module
(I did it in the ui under Extend)
6. the files configuration page after enable locale
[edit: fix copy paste error, said "before"]

7. watchdog
The file entry at the top, after installed locale is unrelated about cannot remove a twig file.
"The file /Users/ctheys/foo/d8-patch/sites/default/files/php/twig was not deleted because it does not exist."
8. check files directory
ls sites/default/files(wow) translations directory is there.
ls -ld sites/default/files/translationsdrwxrwxr-x 3 ctheys staff 102 Dec 8 14:35:18 2012 sites/default/files/translations/
meh. ok. getting tamper.
9. get tamper from the sandbox so can simulate automatic downloading from l.d.o
I believe this downloads to a temporary directory, and then after import, copies the .po files to the translations directory that is set in the file settings (sites/default/files/translations/)
From http://drupal.org/sandbox/sutharsan/1833370
copy the git command
change directory first
cd modulesgit clone http://git.drupal.org/sandbox/sutharsan/1833370.git locale_tamper10. enable locale_tamper under Extend
11. add german
admin/config/regional/language/add
progress bar
says 5 of 35 better formats, etc.
Then get error. with a message that the import worked.
watchdog has messages like
file "File temporary://devel-7.x-1.3.de.po could not be copied because the destination directory translations:// is not configured correctly."
and then locale "Translations imported: 1567 added, 57 updated, 0 removed."
12. try saving the file settings page
admin/config/media/file-system
13. add dutch language
do not get the error.

thoughts
I thought maybe the .htaccess was changed when I hit save on the file settings form.
but:
.htaccess has the same time stamp. the same permissions are on the translations directory (.)
So... I dont know.
I checked the watchdog. And there is no entry between the message the German translations were imported and the adding of Dutch. (no log message as a result of just saving the files settings form.)
Comment #3
yesct commentedgoogle search for
"could not be copied because the destination directory" site:drupal.org
shows issues like
#1588056: The specified file temporary://filet8OKMQ could not be copied, because the destination directory is not properly configured
maybe the message about cannot delete twig because it does not exist is related after all. perhaps getting that error because the system had tried to copy a twig file but it didn't work and I'm just seeing the error from when it tried to delete something it expected to be there.
I could try clearing caches... maybe right after enabling locale?
Comment #4
csc4 commentedI had this problem and for me the issue was that Locale install (7.31) didn't create the directory sites/all/translations defined at admin/config/regional/language/update
Don't know why, don't know why it wasn't an issue on the Status report page but creating that directory fixed it for me...
Comment #6
joshmccormack commentedIn addition to making sure you have a translations directory created and set, make sure to look at admin/reports/status and see that you have tmp and private configured. Without those, translation updates won't download.
Comment #19
smustgrave commentedThank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #21
smustgrave commentedBelieve this is still valid. From the reading actually reads as a potential bug.
Comment #22
gogowitsch commentedI ran into this exact problem with Drupal 11.3.11. I tried, without success, the steps mentioned above, especially:
/admin/config/media/file-systemA solution was to run
drush locale:updateto import the available translation updates, instead of the web-based translation update at/admin/reports/translations.For me, this happend with the shared hoster All-Inkl.