Closed (fixed)
Project:
Coder
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 Feb 2008 at 13:58 UTC
Updated:
27 May 2008 at 15:41 UTC
Jump to comment: Most recent file
Comments
Comment #1
douggreen commentedGood idea, please test the attached patch. It looks for the presence of ./po without ./translations. If you run this on many modules with several directories that need to be moved, it will give you the error only once, and only mention that one directory. It would be better to show it foreach directory that needs to be moved, but I think that this is an edge case that probably doesn't deserve the extra half-dozen lines of code we'd need to do that.
Comment #2
nancydruI'll try to do this right away. I generally run it on only one module at a time, so the limitation is not a big deal.
Comment #3
nancydruPHP Parse error: parse error, unexpected ')' in C:\\www\\drupal-6\\sites\\all\\modules\\coder\\includes\\coder_6x.inc on line 509.
After I removed the extra ')' it worked fine and caught the change.
BTW, you're killing me - modules that are already converted keep getting more flags... ;-(
Comment #4
stella commentedI get the error:
Removing the extra ')' fixes it. I've re-attached a fixed version of the patch.
The patch does correctly identify that I have a 'po' directory instead of 'translations'. However, the warning is printed once for each file in the module directory, so it's printed for e.g. faq.install, faq.module and for each of my 8 theme tpl.php files. Maybe it should just alarm on the first one?
Cheers,
Stella
Comment #5
nancydruYes, I get the same thing - message on each file. However, once I corrected the directory problem, the message still appears on the .install file even though it disappeared on the .module file.
Comment #6
stella commentedThe same is not true for me. Once I fixed the directory name, no more warnings appeared.
Comment #7
nancydruI haven't committed yet; could that be it?
Comment #8
stella commentedI don't see how it could be, but I guess there's no harm trying. It's not there as a hidden directory, no?
Comment #9
Freso commented(Why was it set to "active" instead of "patch (foo)"?)
Comment #10
Freso commentedHere's a re-roll. I think, though, that it should probably only appear for either .module or .info. The current one makes it way cluttered, and it's not that critical an issue.
Comment #11
Freso commented@nancyw: I had the same problem (created a 'po' dir to trigger the warning, then made a 'translations' dir to remove it again... only it didn't), but clearing the cache solved the problem. So it looks like a cache issue.
Comment #12
nancydruIndeed. I've had multiple "opportunities" to clear the cache and now the flag is gone.
Comment #13
douggreen commented@Freso, You should only get this error once per module. What project did you use that displays the error for each .module and .install?
Comment #14
Freso commented@douggreen: snpower wrote – and I see the same behaviour. But if you really must know, I used Akismet with the patch from this issue applied. I created the "po" folder myself, to check the warning.
Comment #15
stella commentedThe attached patch should work without producing the warning for each file in the directory. It will only produce the warning for the .module file.
Doug - the check in the previous patches wasn't within the
if (substr($filename, -7) == '.module') {....}section and so was being applied to every file.Cheers,
Stella
Comment #16
stella commentedCommitted.
Comment #17
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.