User talk:Ben



Example of using pre over multiple lines

  1. Some bullet point
  2. Another bullet point
  3. Use this javascript code:
           var node = eventObj.Source;
    
    var newProbs = node.parentNode.selectNodes("some_concept_set");
    if (newProbs.length > 1) {
    deleteTableRow(eventObj);
    }
    else {
    var node = node.firstChild;
    while (node
    }
  4. Yet another bullet point


Testing the "@" image

botfinder1@ben.eflow.org

botfinder2Image:At-image.pngben.eflow.org


Testing the External Downloads mediawiki extension

OpenMRS 1.5.2

Feb 2nd 2010 - The latest stable release. Release notes
(OpenMRS 1.5.2 represents version 1.5.2.11935)
openmrs-1.5.2.jar1.29 MB
openmrs.war25.91 MB
OpenMRS_1.5.2.vmwarevm.7z143.23 MB
README692 bytes


Example Table

Optional Header Optional Header 2 Optional Header 3
Cell 1a Cell 2a Cell 3a
Cell 1b Cell 2b Cell 3b


Homepage widgets

Join community conversations via our forums, mailing lists, and online chats.

Rss-icon.gif Recent Posts:

» 17-Mar Implementer ML: Need help with the mdr-TB module
» 17-Mar Developer ML: svn error
» 17-Mar Developer ML: svn error
» 17-Mar Developer ML: svn error
» 17-Mar Implementer ML: Need help with the mdr-TB module

Get project updates through our blog aggregator or join a working group.

Rss-icon.gif Recent Blog Updates:

Suggest changes and view project timelines via our development site or learn how to contribute code!

Rss-icon.gif Recent Submissions:

10-Mar — News Blog: OpenMRS 1.6 RC is ready
Hi All, After a longer-than-expected delay, and a few bugfixes, the OpenMRS 1.6 Release Candidate is ready, and available on the prereleases page. Have at it! Assuming no bugs, this should become the official release by March 19th. -Darius
 
17-Feb — News Blog:
Hi All, Apologies, but there was a non-obvious-but-show-stopper bug in the Beta 2 from this morning. The offending code has been removed, and OpenMRS 1.6 Beta 3 is now ready for testing. You can get it here. Assuming no further major bugs, we should have the release candidate out in a week. We?re looking for one implementation (in addition to AMPATH, who has generously offered) to test out the release candidate in production, so we can be totally sure it?s stable. Let me know if you?re interested in that being you. -Darius
 
16-Feb — News Blog: OpenMRS 1.6 Beta 2 released
Hi All, OpenMRS 1.6 Beta 2 is now ready for testing. You can get it here. Assuming no major bugs, we should have the release candidate out in a week. We’re looking for one implementation (in addition to AMPATH, who has generously offered) to test out the release candidate in production, so we can be totally sure it’s stable. Let me know if you’re interested in that being you. -Darius
 
30-Jan — News Blog: OpenMRS 1.6 Beta Released
Hi All, Thanks to everyone who tested our alpha release of 1.6, we’re releasing 1.6 Beta. You can get it on the downloads page. We’ve made only two significant changes since the alpha: We’ve implemented “core modules” properly, meaning that we may now have modules that are required by core, and OpenMRS will not start up if they are not present. (The purpose is to make it easier for feature development to happen independently. Logic is the only one of these at the moment.) We had switched the role name from “System Developer” to “Administrator” but we’ve switched that back. It will change to Administrator again in the future, but not until we have added an integer primary key to the table so that we may correctly rename the role, instead of deleting and re-adding it. (Thanks Mark Goodrich for testing with the Patient Flags module and catching this.) You can see the additional trivial changes in the release notes. We still need to see some further testing of Beta release before we’re ready to move onto a release candidate. And I’m actually going on vacation for a week. So…go ahead and test away so that when I get back we’ll be all set to release. -Darius
 
16-Jan — News Blog: OpenMRS 1.6 Alpha Released
Hi OpenMRS Community, Our first alpha preview release of OpenMRS 1.6 is ready! First off, I’d like to thank the 35 developers who contributed code to this release: Agnor, arthurs, ayeung, ball, bmckown, bwolfe, cliff.mcintosh, dfuterman, djazayeri, dthomas, emendez, ewolodzko, hkwathome, jamesm, jmiranda, Keelhaul, Knoll_Frank, luzhuangwei, madanmohan, mkopinsky, mogoodrich, mseaton, msheley, n.nehete, nribeka, Pascal, r0bby, rarcos, rcrichton, samrajni, sunbiz, suneeth, tmdugan, upul, yatitandon You can read the release notes here or, if you’re impatient, you can go straight to the prerelease downloads page. Note that this is a PRE-release, intended for testing, and not for production deployment. The changes made in 1.6 are much less invasive than those we made in 1.5, so I expect there to be far fewer bugs, and I expect us to be able to get to beta, or even to a release candidate, within a couple weeks. But to do that we need your help. We need people to install 1.6 alpha, play around with it and look for bugs. There are three specific things I’d really like to ask for help testing: Everyone, even if you don’t have time for thorough testing, should try making a copy of their database, upgrading it by running this 1.6 alpha war, and reporting any failures People who use logic should test their code and make sure it still works now that most logic code has been pulled out into a module If you want to have Patients-who-are-Users then that is now possible. Please test it! Module owners should re-test their modules, because of a small number of unavoidable non-backwards-compatible changes. HTML Form Entry is broken, for instance. A week from today I would like to release an alpha-2 or a beta release, so do your testing sooner rather than later. Thanks, Darius
 

Things to test:

  • Try to log in with incorrect password
  • Try to duplicate form
  • Alerts:
    • Try to add Alert to self
    • Use Mark that Alert as Read link at top of page, refresh page to make sure its gone
    • Add another alert, use admin page to make alert disappear
  • Try creating a new patient with the short form (linked from the search screen)
  • Try creating a new patient with the long form (linked from the Admin screen-->Manage Patients)
  • Try creating a new user
    • Try creating a new patient off of that new user (make sure new patient_id == user_id)
  • Create user off of existing patient (make sure new user_id == patient_id)