Extending discussion and work from here, @ivange94 came up with a Documentation on this issue, however I think this should be updated and improved cause am seeing alot of implementations being blocked by this simple issue. I suppose workarounds should be done to automate the installation process without hitting this tragedy. If documentations are put in place, I think links to the resource are relevant on such pages, download, Installing OpenMRS . I’m just coming up with an idea members, Any thoughts? cc: @ivange94 , @darius , @dkayiwa … etc
@samuel34 I agree that this current situation has been confusing for people, and it should be priority to fix it. (And thank you for taking the initiative to propose this as a community priority, following up on our conversation on the other thread!)
@dkayiwa did we end up creating tickets based on that design forum?
We had discussed this in the context of the OpenMRS Platform releases, but I wonder if one problem is that some people run into this because they just build and run openmrs-core. (In which case our proposed fix isn’t going to address their situation.)
Also, @samuel34, can you suggest what parts of the current process are especially confusing to new users? (For example I just noticed that the wiki page about installing a UI module incorrectly stated that the Reference Application didn’t support Platform 2.x. I changed the wiki page, but the instructions that I quickly wrote just now are too brief.)
According to my analysis and research, most of the implementations encounter this error when installing OpenMRS through building core or just using a “.war” file and deploying it to tomcat. This is because platform has no UI modules installed at the start. I propose on the start page of platform (The page where database tables are created and updated), there should be included a widget of adding the Legacy ui module.
@dkayiwa I didn’t know there tickets on this, if so do you mind pointing them out?