Closed (fixed)
Project:
Localization update
Version:
7.x-2.2
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
12 Nov 2017 at 05:26 UTC
Updated:
14 Feb 2018 at 21:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
sutharsan commentedThe error you are getting in not the root problem. I suspect that you have a malformed translation file.
The error you get is cause by a bug that will be solved with the attached patch. Once that is resolved you will get information in the log about the file and line number were the error is found during import.
Comment #3
sutharsan commentedComment #5
delacosta456 commentedhi
thanks i will check and get back to you
Comment #6
sutharsan commentedAdditional patch to make sure the line number is always correct.
Comment #8
delacosta456 commentedBack to you @Sutharsan
Well Just after the fisrt patch (because i am just seeing the second patch now while writing to you) , there were no more error and most of update where successfully done...
-- Most because some ftp// server where not reachable , for some they were no available translation ..(that looks to be normal)
-- however i am still getting some little warning (below cattached files) ... but suppose they me be related to the above non-reachableserver/ non-avilable file
Thanks for the second patch that i will also apply and see what will happen
Comment #9
sutharsan commentedMy approach is usually to start with the first error, fix it and usually the following errors disapprear. The first one is "Missing or malformed header" on the workbench_access-7.x-1.5.fr.po Check the content of this file, compare is with other .po files. Delete the file, download it manually from localize.drupal.org or download it via the interface.
Comment #10
AritoMelo commentedHi @Sutharsan and @delacosta456 for simplicity and also to avoid some mistakes by trying to use only one of two patches I suggest this new patch that is the result of both together.
Tested on version 7.x-2.2!
Comment #11
sutharsan commentedHave you tried the latest dev? The code is as you suggest it to be changed.
Comment #12
AritoMelo commentedI have tested it on the latest stable version, not on dev!
Till the next version the projects that only update to last stable version can use it.
Comment #13
sutharsan commentedI don't understand what you are asking me.
Closing the issue as there is nothing more I can do.