As with all prior releases, there is a bit of work to do. If your interested in helping, check out above link to get an idea of things you can help with.
For those wishing to help with the release. Here are the critical issues that need to be completed before the release: Issues · openemr/openemr · GitHub
And then here is the complete list of issues that would prefer to have completed before the release: 5.0.2 Milestone · GitHub
What version of PHP should we use to try out 5.0.2 ? From what I’ve seen so far, the install/setup routine doesn’t complete correctly with any version of PHP from 7.0-7.3
I just started playing with it Friday, going through it again today so far I’ve noticed the the gacl/setup.php file is missing, as is most of the content of the /vendor sub-directory.
I’ll do a fresh git checkout and start over from scratch, maybe I didn’t get everything the 1st time around.
If anybody else is playing with this, be forewarned that it flat out won’t build on Ubuntu 16 LTS, you’ll need Ubuntu 18 (a.k.a “Bionic Beaver”) in order for composer and the other dependencies to work.
Looks like maybe something went wrong when I cloned the master last week, or something got fixed over the weekend. I checked out a fresh copy from GitHub and started over, it at least builds correctly and the setup routine works. The UI is still a cluster, but this is a start.
I kept running into dependency errors with obsolete package versions trying to run the composer install on Ubuntu 16.04 LTS, even after I made sure all the PHP packages there were up to date, so I just quit wasting time with it and did the distro update to 18. Interesting that it works in some environments and not others. Thanks everyone!
@brady.miller It looks like you meant to say 7.1.1 instead of 5.1.1. Right? The line you reference in the Checker checks against 7.1.1. PHP themselves doesn’t support any version before 7.1.
We probably should just strongly encourage PHP7.2+ and Ubuntu 18.04. This combo seems to install very well. I believe Ubuntu 16.04 LAMP install PHP7.0 by default but not 100% sure.
Greetings all,
I’m a developer with more than 15 years of experience using php and javascript.
From the opened issues to complete the 5.0.2 milestone is there anything I can tackle to help?
Thanks for offering to help. Fixing this critical issue would be awesome: Page Refresh: Athentication error · Issue #2530 · openemr/openemr · GitHub
(ideal solution here is “throw up a warning if a user tries to do a page refresh from browser (via window.onbeforeunload) to prevent user from doing a browser refresh and losing their work”)
There was a bit of a delay in release to allow optimization of the sessions/cookies (still a bit of road testing to do) and upgrading of docker environments (alpine 3.10 was just released couple weeks ago) to use PHP 7.3 which allows a cool cookie (samesite) feature that provides protection against csrf vulnerabilities. This environment is now live on this dev demo (https://www.open-emr.org/wiki/index.php/Development_Demo#Demo_.28Alpine_3.10_-_uses_php_7.3.29), so please test and try to break it
(this is also the environment of the flex docker, so developers can develop/test in it)