User:Cmorse/Notebook/MediaWiki for Open Science/2009/02/02

From OpenWetWare
Jump to navigationJump to search
Report.pngMain project page
Resultset previous.pngPrevious entry      Next entryResultset next.png

I was using wordpress today and I noticed the message they show when an autosave version is different than the one on the current page. Here's a screenshot of it:

Cmorse notebook wordpress autosave.png

I really like how this looks, and I think it would be the best option for notifying the user that autosaved changes have been detected.SJK 23:17, 2 February 2009 (EST)
23:17, 2 February 2009 (EST)
I agree that that notification looks nice and is effective. Ironically, Anthony lost an edit today on his first day doing open notebook science in Osley's lab!
  • Added better autosave notification mentioned above
  • Added support for loading jquery library from google servers, with ability to disable it within LocalSettings.php


  • Various bug fixes for enabling/disabling extension
  • Switched to custom image for enabling/disabling extension (icon shows up in upper right hand corner, but only on edit pages).

Enabled: Cmorse notebook LiveSaver enabled.png Disabled: Cmorse notebook LiveSaver disabled.png

With these updates the plugin is probably ready for some real testing.

After using the wiki so much recently I can see how useful this extension could be; I have lost work a couple times in the past week for various reasons.SJK 02:10, 3 February 2009 (EST)
02:10, 3 February 2009 (EST)
Is it possible to easily demo it on the MW server you installed on our server? Is it the kind of thing that could easily be added to MW, but only enabled for a couple users (such as you, me, and Ant)? Given that both of you have lost information recently, I am even more interested in asking Bill about adding this very soon, so please let me know. Thanks for the speedy progress!

diff It is definitely possible to limit which users the extension is enabled for. It shouldn't take me more than 15-20min to add that.

Steve comment

Steve Koch 02:52, 3 February 2009 (EST): Not sure if you'll read this message soon: but the example on didn't seem to be working at 12:25 am? (I left a message on my talk page, which I'll replicate here): I just gave it a whirl using the "community portal" page of the wiki, and it didn't seem to be working (12:20 am). Here's what I did:

  1. clicked edit
  2. typed some stuff
  3. closed window
  4. revisited page
  5. clicked edit

It told me an old version was available, but it didn't have any of my information. Not sure if I didn't wait long enough? I don't know how your implementation goes, so wasn't sure what it was supposed to do. When I tried it the very first time you enabled it (last week?) I remember that something similar to the above procedure did work...

  • Cmorse 02:55, 3 February 2009 (EST): Oops, that was a typo in the code on my part. It should be working correctly now. If it doesn't you might need to delete the cookie that it created. But I wouldn't do that until we've exhausted allother options.
    • Steve Koch 03:04, 3 February 2009 (EST): I didn't try deleting the cookie, but now the extension doesn't do anything. Of note: the enable / disable icon on top right is not clickable anymore
      • Cmorse 03:12, 3 February 2009 (EST): If you were using IE, try it again. I had some debugging code still in there that only works with FF. But it should be working now.
      • Steve Koch 03:21, 3 February 2009 (EST): Actually I was using FF and the behavior is still the same (not enabled apparently, and the enable / disable button doesn't work (frozen with green checkmark). With IE7, it does work! And I like it! However, the enable / disable checkbox isn't visible. I'm not sure that enable / disable button is needed or desirable, even...I'm thinking it'd be OK since your message box is so unintrusive.
      • Cmorse 03:43, 3 February 2009 (EST): Ok, FF should be working correctly now. I forgot that FF fails when it hits the debugging code without the right extension installed. I will work on getting the enable/disable button to show up in IE7 if we decide to keep the button around.
      • Steve Koch 03:49, 3 February 2009 (EST): Awesome! Both of them worked for me now. I'm definitely interested in getting this enabled for you, me, Ant, and any other beta testers as soon as possible. If Bill agreed, do you think it'd be easy for him to selectively enable it? I'm going to probably go to bed now, and you probably are too (if you're not already sleep coding). So, let me know if I should email him, and what link I should point to. Or, actually, you probably would explain things better, so you should definitely feel free to email him yourself. Thanks again for this ... I'm very excited about it!
      • Cmorse 03:59, 3 February 2009 (EST): I will try to add the ability to enable/disable the plugin based on username. Right now I don't have public access setup for the svn repository (soon I will), but for now I can just email him a zip file of the extension. I think it would be better if you emailed him about it and CC'd me on the email since he already knows who you are. I am going to bed as well; maybe someday I will learn how to get work done in my sleep, but I am not there yet.
      • Steve Koch 04:03, 3 February 2009 (EST): OK, good night! When you read this, please let me know whether I can point him to a page, such as this test page, and he'll be able to try it out. I.e., can anyone in the world use that wiki (as long as we don't have too much traffic).
      • Cmorse 04:09, 3 February 2009 (EST): Yep, that page will work for anyone in the world. One thing he should be aware of is that it currently doesn't work on Chrome, Safari, or any webkit based browser. I'm currently waiting on a response from the mailing list to help me get those browsers working.
        • Cmorse 16:34, 3 February 2009 (EST): Just a quick note. Turns out that I was incorrect about it not working in webkit based browsers. I have been beta testing win 7, and I had to disable some functionality in chrome to get it running. Turns out that the functionality I disabled was required for portions of the extension to work correctly.