My watchdog is filled with messages about locale.module parsing javascript files. This message is printed so many times that it makes the watchdog a pretty useless tool for analysing problems with the site as there may only be 3 or 4 valid watchdog message in a page full of these messages from locale. The problem was recently reported on the forum here http://drupal.org/node/402268 and I brought it up in IRC and was advised to open a bug report.
Is this really intended behaviour? Or is this just a stray watchdog call that was forgotten to be removed? If it really is a genuine message, then there needs to be a way to turn down the logging level so that the watchdog can become useful to anyone who cares about things other than local.module pasing javascript files.
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | 409676_locale_watchdog_unnecessary.patch | 1.68 KB | greggles |
| #7 | locale-watchdog.patch | 595 bytes | mrfelton |
| #5 | parsed_javascript.png | 45.58 KB | ShannonK |
| #5 | parsed_javascript2.png | 19.17 KB | ShannonK |
Comments
Comment #1
kruser commentedI'm getting these notices too for every javascript file...
Parsed JavaScript file sites/all/modules/memcache/memcache_admin/memcache.js.Any idea how to get rid of them?
Comment #2
mrfelton commentedyeah, comment out the line in local.module - line 508. Yes, It's a core hack, but there's no other way as far as I know.
Comment #3
kruser commentedGood to know. Thanks!
Comment #4
pvhee commentedStill no solution for this problem?
Comment #5
ShannonK commentedI'm getting a bunch of these messages too. What do they mean? Is this an error?
Comment #6
malukalu commentedsubscribing
Comment #7
mrfelton commentedHere is a patch that removes the annoying message. Can we get this commited into core? The watchdog is next to useless when it's full of these messages.
Comment #8
lias commentedSubscribing to track fix.
Comment #9
geek-merlinsubscribing
Comment #10
gregglesThis seems reasonable to me as well. I found this issue from a thread that claimed that Google Analytics caused this to be parsed on every page, but the site where I have this problem doesn't use Google Analytics. Perhaps there are other modules that cause it to happen more often than necessary, but I'm not sure watchdogging all the time is the solution.
Comment #11
abqaria commentedsubscribe
Comment #12
mlncn commentedUnless someone can explain why we care when a JS file is parsed, or more likely why locale shouldn't be parsing JavaScript files in the first place, can we call this patch ready to go? We've tested it.
benjamin, agaric
Comment #13
dave reidYeah, this message is unnecessary. Let's fix in D7 first.
Comment #14
Ela commentedsubscribe
Comment #15
HTF commentedsubscribe
Comment #16
gregglesOk, same thing for D7.
Comment #17
dave reidYay!
Comment #18
dries commentedCommitted to CVS HEAD. Moving to D6.
Comment #19
gregglesNow the patch from #7 should be good - http://drupal.org/node/409676#comment-2082670
Comment #20
Sten-dupe commentedSorry i am confused is the patch for D6 on #7 ? it says its failed and has not been retested. Or is it greggles post on #16 confused as he put D7
Can someone clarify for me,
Thx
Comment #21
gregglesThe patch in #7 applies to Drupal 6. The failure message is about testing it on Drupal 7, where we expect it to fail.
Comment #22
gábor hojtsyTheoretically, this should not happen often, but only when caches are cleared. I'd advise you look at why are your caches cleared this often.
Committed this patch to Drupal 6 too.