Continuing the discussion from About ImageJ wiki upgrading:
Status update! The wiki is back!
- We completed the migration of the wiki to the latest version of MediaWiki on a newer, bigger, faster server.
- We performed a full security audit of all extensions, removing many obsolete and unused ones.
- We pushed the full source code of ImageJ’s customized MediaWiki installation including its custom extensions.
RESET YOUR PASSWORD!
The reason for the extended downtime is that there was evidence the machine running the wiki may have been compromised. We are waiting on forensic analysis to determine if that is really the case.
Hence, for security reasons, we have reset EVERYONE’s passwords. You will need to visit the Password Reset page to set a new password for your account. We strongly recommend that you do not reuse your old password. We do not know whether any passwords were compromised, but we are proceeding under the assumption that they were.
- The multiline LaTeX feature has finally been fixed, so pages like Integral Image Filters render correctly again. (Sorry that was broken for so long, @axtimwalde.)
- The Tabs extension is now working (see e.g. Eclipse). (For you, @hinerm!)
- All embedded YouTube videos now use the Widgets extension.
There are still some loose ends, which we will address in coming days:
- Fiji’s BugZilla issue tracker is still down. We will be retiring that service, but will archive all the old bugs for posterity next week.
- The top menu bar (About, News, Events, Source, Status, Help) is missing/nonfunctional.
- The old FLVPlayer extension was disabled, and so embedded FLV videos (e.g., Simple Neurite Tracer: Introductory Screencast) are not displayed properly. We are exploring the best way to restore/adapt this feature.
<source>tags do not set the overflow anymore, due to a change in syntax highlighting extension; see e.g. Eclipse#Running_and_debugging.
- The VisualEditor extension is still not working (it worked for a time on
fiji.sc, but never worked on
imagej.net—I was hoping to fix that, but there are still some technical hurdles to overcome relating to the parsoid service on our new server).
- The usage maps are currently broken in several different ways. It has been on our list to fix them for a long time now, but doing so is rather involved. We will keep working on it though!
- We still want to migrate the ImageJ user guide to the wiki (@tferr); we will explore doing that later this year, including the best way to support exporting it as a PDF.
Lastly: please LET US KNOW if you notice anything else not working as it should, and we will investigate!