Tonight I went through the RELEASE-NOTES-1.22 and did a little house
cleaning. In the process, I had some ideas for how we could make the
1.23 (and future releases) more usable more easily. I mention this on
this mailing list because I'd like to get feedback from actual users.
You can see my pro
Doh... should have read the infobox where it says 1.22+...
On Nov 7, 2013, at 12:26 PM, Chad wrote:
> On Thu, Nov 7, 2013 at 10:05 AM, Jim Hu wrote:
>
>> Thanks for the replies, Nik and Chad. Sounds like I should switch.
>>
>> Is 1.21.2 recent enough? I'm going to try this on a development s
On Thu, Nov 7, 2013 at 10:05 AM, Jim Hu wrote:
> Thanks for the replies, Nik and Chad. Sounds like I should switch.
>
> Is 1.21.2 recent enough? I'm going to try this on a development server.
>
>
The upcoming 1.22 release *should* suffice.
-Chad
___
Thanks for the replies, Nik and Chad. Sounds like I should switch.
Is 1.21.2 recent enough? I'm going to try this on a development server.
On Nov 7, 2013, at 10:50 AM, Nikolas Everett wrote:
> On Thu, Nov 7, 2013 at 11:37 AM, Jim Hu wrote:
>
>> Hi Nik,
>>
>> As I was reading the docs for M
On Thu, Nov 7, 2013 at 11:37 AM, Jim Hu wrote:
> Hi Nik,
>
> As I was reading the docs for MWSearch, I considered whether I should
> switch to CirrusSearch, so it may not be a difficult sell. I'd even
> volunteer to try to update the documentation if you're willing to help walk
> me through it.
On Thu, Nov 7, 2013 at 8:37 AM, Jim Hu wrote:
>
> My similarly uninformed reading about CirrusSearch is that it uses
> elasticsearch, which in turn uses Lucene. So if the problem is between the
> incrementalUpdater and Lucene, I might have similar issues with
> CirrusSearch. But if CirrusSearch
Hi Nik,
As I was reading the docs for MWSearch, I considered whether I should switch to
CirrusSearch, so it may not be a difficult sell. I'd even volunteer to try to
update the documentation if you're willing to help walk me through it.
But to show how clueless I am... I'm not sure how to chec
> On Thu, 07 Nov 2013 15:34:14 +0100, wrote:
>
>> To clarify, I am looking for a way to add something like this:
>>window.onbeforeunload = function() { return "You work will be lost."; };
>>to the page every time a user has the edit window open.
>
> MediaWiki 1.22, due to be released in a few week
On Thu, 07 Nov 2013 15:34:14 +0100, wrote:
To clarify, I am looking for a way to add something like this:
window.onbeforeunload = function() { return "You work will be lost."; };
to the page every time a user has the edit window open.
MediaWiki 1.22, due to be released in a few weeks, include
> What's the best way to disable the back button for users? I have a user
> who uses his back button a lot and we're finding that he accidentaly
> reverts his changes.
To clarify, I am looking for a way to add something like this:
window.onbeforeunload = function() { return "You work will be los
What's the best way to disable the back button for users? I have a user
who uses his back button a lot and we're finding that he accidentaly
reverts his changes.
Also, we're running into an issue with images being cached, most likely in
the browser, and editors have to refresh the page several ti
On Wed, Nov 6, 2013 at 7:04 PM, Jim Hu wrote:
> Our MWsearch stopped updating a while ago. I'm wondering if one of
> Apple's Java updates caused a problem.
>
I'm work on the system that will replaceMWsearch/LuceneSearch so I have to
try to sell it to you first:
https://www.mediawiki.org/wiki/Ex
12 matches
Mail list logo
