I have a looping error showing up in my logs whenever a page is loaded. It's not interfering with the functioning of either the manager or the live site, but it is causing my dev site error log to bloat quite a bit. The error shows up approximately 100 times in the error log for every page load. As you can imagine, once the site goes live and there are thousands of page loads a day, this will be a major issue. The error reads as follows:
[2012-12-21 08:46:15] (DEBUG @ /siteurl/index.php) Language string not found: ""
I can only guess that this has something to do with the Lexicon, but all settings there are as they should be. Thoughts?
-
MODX Staff
- 12,272 Posts
What version are you running and what Add-ons do you have installed?
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Ryan - running 2.2.5-pl with the following addons (all are up to date):
- Archivist
- Articles
- Big Brother
- Breadcrumbs
- CodeMirror
- FormIt
- Gallery
- getPage
- getResources
- GoogleSiteMap
- If
- LocalWeather
- mxCalendar
- phpThumbOf
- Quip
- Simplesearch
- taglister
- TinyMCE
- UltimateParent
- Wayfinder
Do you have debug turned on for MODX or for any of the add-ons?
IMO, it's much more likely to be in an add-on rather than MODX.
If you can create a localhost install of the site and have an editor that will do multi-file searches, you can search the codebase for "Language string not found". That should reveal the culprit.
As an alternative, you can disable plugins one at a time until it goes away, and if that doesn't work, disable snippets one at a time (especially ones in templates or chunks called in templates) by putting a space between the opening brackets until it goes away.
Bobray - most of the addons are installed using default settings so I'm unsure about whether any of them have Debug turned on - but it's not on for the MODX install. Gonna have to check on that.
Installing the site on a localhost would be pretty extensive work, so I may just go through and disable one by one as you suggested and see what happens. Will update after I've done this - in the meantime, any further thoughts would be awesome!
-
☆ A M B ☆
- 3,141 Posts
It looks like the log_level system setting is set to debug instead of error. While it can be convenient to look into issues using debug mode, it logs too much stuff to be particularly useful
-
☆ A M B ☆
- 24,524 Posts
That can come from core/model/modx/modlexicon.class.php when in debug mode, line 385
$this->modx->log(xPDO::LOG_LEVEL_DEBUG,'Language string not found: "'.$key.'"');
@MarkH - unfortunately, this isn't the case. The log_level System setting is set to 1 (which is error, I believe). Wish you'd been right, as that would have been an easy fix.
@Sottwell - Would the line of code you cited cause any issues if the MODX install is not in fact in debug mode?
-
☆ A M B ☆
- 24,524 Posts
It shouldn't show up at all if it's not in debug mode.
It's almost certain that some extra is changing the debug setting. Could you have turned in on yourself in a snippet or plugin property to diagnose a problem with an extra?
