This topic was marked solved by Arantor, on August 1st, 2013, 05:38 AM

live627

  • Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
  • Posts: 1,670
A confident man keeps quiet.whereas a frightened man keeps talking, hiding his fear.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: call_lang_hook: Missing debug info
« Reply #1, on October 8th, 2012, 05:11 AM »
Should it include the full paths or what, exactly?

Remember, the language hooks get a full path to play with, not just the plugin id and relative path.
Re: call_lang_hook: Missing debug info
« Reply #2, on November 1st, 2012, 05:46 PM »
Note that source files loaded from hooks are also not listed separately - but everything otherwise loaded will be caught by get_included_files() so they *will* be listed.
Re: call_lang_hook: Missing debug info
« Reply #3, on April 26th, 2013, 12:32 AM »
Since I rejigged language loading for plugins, I revisited this.

What I've done is made a backwards-incompatible change in plugin management. It should NOT affect anyone who makes plugins per se, unless you want to update. Anyone running an installation WILL NEED to disable all their current plugins before updating and re-enabling them afterwards so that what's in the DB is stored correctly. But this should be transparent to everyone.

Basically, the loaders in the hook callers should now actually use loadPluginSource and loadPluginLanguage, so debug information will be available. It also means caching is handled consistently for languages too ;)

I'll mark it solved once I commit, because it has changes in Load.php which will conflict with everything else >_<
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial