[SOLVED] [checkoutpaypal] error installing language pack
jens_k
Joined: 2007-01-28
Posts: 244 |
Posted: Wed, 2009-04-15 11:08 |
Hi Alec, All others work fine ;-) Cheers, |
|
jens_k
Joined: 2007-01-28
Posts: 244 |
Posted: Wed, 2009-04-15 11:08 |
Hi Alec, All others work fine ;-) Cheers, |
|
Posts: 4342
I've emailed the developers with this:
SUMMARY:
I need help with determining how the language .package files are
created. I think they are being created with incorrect contents for a module
and I don't have access to the code to find out why.
DETAIL:
When installing a new language via the language manager I and the community
get this error:
Error (ERROR_PLATFORM_FAILURE) :
'/var/www/tktp.com/public_html/gallery2/modules/checkoutpaypal/po/de.mo'
doesn't exist.
in modules/core/classes/GalleryRepositoryUtilities.class at line 554
(GalleryCoreApi::error)
etc.
Looking in g2data/cache/repository/community/modules I see that the failing
language pack is checkoutpaypal-lang-de-1606-1630.package which contains
expand_0213d4cecd($outputDir,
'locale/de/LC_MESSAGES/modules_checkoutpaypal.mo', '3hIElQAAAAA....
Notice the path given locale/de/LC_MESSAGES...
For another module (checkout) where the de language appears to install
correctly, the equivalent line from the language pack in the repository
cache is
expand_9737afe8df($outputDir, 'po/de.mo', '3hIElQAAAAAoAQAAHAAAAF...
Notice the different path - po/...
Both these modules have the language files (.po and .mo) in the po directory
in the repository. Both have been scanned/pushed to the repository since the
language files were moved from the /locale/ structure, and the MANIFEST
files have been recreated.
When installing the de language pack, the .mo file is being created in a new
and wrong locale/ directory structure instead of into the po/ directory, and
I believe that causes the error above.
The problem is identical for other languages in this module including .es.
Specific questions:
1) Where is the code that creates the .package files? I suspect it is only
on the GMC server so I cannot examine it.
2) What is the difference in the module files that leads to different
locations for the instruction to unpack the .mo file?
I will let you know if I get an answer.
Posts: 244
Thanks for the info.
___________________________________
http://jekophoto.eu | http://jekophoto.de
Posts: 4342
I had a reply from one of the core team who pointed out that the packaging code is included with the distribution (point your browser at lib/tools/repository).
So I've made a minor change to the Admin template, recompiled all .mo and .po files and reuploaded to the repository.
I've downloaded the code from SVN, done a local build of the packages, and verified that the de language package (revision 1822, for reference) contains the correct directory for creating the .mo file.
The next repository push (when the GMC server will rebuild language packages for this module) is in about 4 hours, so we'll have to see if it's correct at that point.
Posts: 4342
OK, I think this problem is fixed - would anyone like to check and see if they agree?
Posts: 244
Checked all 3 plugins - All works fine now.
___________________________________
http://jekophoto.eu | http://jekophoto.de
Posts: 4342
hurrah! Thanks for testing!
Posts: 244
It was a pleasure ;-)
___________________________________
http://jekophoto.eu | http://jekophoto.de