Re: [MediaWiki-l] Messages not available client-side

2017-11-11 Thread Stephan Gambke
Bleagh. I was sure I had the messages defined together with the module that was using them. Turns out I had them defined with the module holding the styles instead. ​Thanks for the heads-up, Legoktm ​Cheers Stephan > Original Message >Subject: Re: [MediaWiki-l] Me

Re: [MediaWiki-l] Messages not available client-side

2017-11-06 Thread chad amsel
Note: I made no comments to this organization. Nor did i authorize the use of my name in an publications if any sort. Please confirm receipt of my complaint, that this is an accidental error on behalf of your organization, that you have deleted related comments and unsubscribed my email address

Re: [MediaWiki-l] Messages not available client-side

2017-11-06 Thread Kunal Mehta
On 11/04/2017 07:00 AM, Stephan Gambke wrote: > Is there a module I need to/should/could wait for? I thought RL was making > sure that basic modules like mw and jquery were available before > loading/running other stuff? You just need to wait for the module that depends upon those messages to

[MediaWiki-l] Messages not available client-side

2017-11-04 Thread Stephan Gambke
I'm sometimes getting the message code instead of the message text in JS using mw.message(...).text(). The messages in question are declared in the RL module declaration. This happens when doing a normal reload (F5), not when doing a full reload (Ctrl+F5), so I guess reloading the module from