It (with or without demo data) doesn’t work on Mac Chrome – I log in as physician and it doesn’t take me to anything …
good catch @Ralf_Lukner , it doesn’t look like there are any valid users other than admin
the site with demo data has them so maybe when the above demo resets overnight the users will be restored
looks like that’s all it took to break it
Hi,
I just checked this and I was able to login with physician:physician on the site with demo data.
Is this still not working for you. If so, what browser are you using?
looks like there’s a problem with mac os mozilla and chrome for the physician login at https://www.open-emr.org/wiki/index.php/Development_Demo#Demo_.28Alpine_3.10_-_uses_php_7.3.29
and when you login as admin it doesn’t show other users
Strange. When you login as admin to the demo with data, do you see this:
btw, this is demo link of that screenshot:
https://six.openemr.io/a/openemr/interface/main/tabs/main.php?token_main=9jQ6u2WMcveYprw2vTxkvrKfcacXHevmDlPOxBwP
Hi @stephenwaite and @Ralf_Lukner ,
I brought in a fix 2 days ago for session/cookie (a comma in the session id was causing problems, which should now be fixed, and guessing was causing issues with your browsers). Please retest and tell me that the issue has gone away
-brady
Hi,
I just branched rel-502 in github repository, and we are about 2 weeks from the 5.0.2 release.
There are now 5.0.2 development specific demos and packages (packages are built daily) along with install/upgrade instructions. Please test these all.
The OpenEMR 5.0.2 development demos are here (4 environments each with a demo with and without demo data):
https://www.open-emr.org/wiki/index.php/Development_5.0.2_Demo
The OpenEMR 5.0.2 development package builds (and install/upgrade instruction sets) can be found here:
https://www.open-emr.org/wiki/index.php/OpenEMR_Downloads#Daily_snapshots
You can follow the progress of the release process here (and feel free to help out with anything):
https://www.open-emr.org/wiki/index.php/QA/Release_Process#Version_5.0.2
-brady
no change
still no users listing under admin login and physician login says invalid username/password
with ubuntu firefox https://six.openemr.io/openemr/interface/login/login.php?site=default admin login shows only admin user
also happening at https://eight.openemr.io/openemr/interface/login/login.php?site=default, so it’s the master branch that has a problem loading the users
Hi,
Chest pain…
How about these 2 demos in https://www.open-emr.org/wiki/index.php/Development_5.0.2_Demo :
https://six.openemr.io/c/openemr/index.php
https://seven.openemr.io/f/openemr/index.php
(ensure you have that ‘c’ or that ‘f’ in the path)
I tried the ‘six’ and it seems to be working well on a quick check.
–RBL
Hi,
Freezing the 5.0.2 branch (except for bug fixes). Please test, test, and then test some more.
The OpenEMR 5.0.2 development demos are here (4 environments each with a demo with and without demo data):
https://www.open-emr.org/wiki/index.php/Development_5.0.2_Demo
The OpenEMR 5.0.2 development package builds (and install/upgrade instruction sets) can be found here:
https://www.open-emr.org/wiki/index.php/OpenEMR_Downloads#Daily_snapshots
There is also a dev 5.0.2 docker that will upgrade automatically if proper conditions are met (https://hub.docker.com/r/openemr/openemr/):
"
Automatic upgrading of OpenEMR is supported when upgrade from 5.0.1 to 5.0.2+ (note this is not supported in the flex* series). In your docker-compose.yml file, you can basically change the 5.0.1 to 5.0.2 image and then do a docker-compose up. This will only work if you have set a shared volume for the /var/www/localhost/htdocs/openemr/sites directory (it will not work if either you didn’t set a shared volume or you set the shared volume to be the entire /var/www/localhost/htdocs/openemr directory). Before you do this, recommend backing everything up.
"
-brady
last lap
Congratulations to Brad et al as it always takes a significant effort to make a release!
- ViSolve
Will there be a way to upgrade from AWS 5.0.1(7) to AWS 5.0.2?
–Ralf
hi @Ralf_Lukner ,
The dockers have a neat upgrade mechanism if certain criteria are met. Is there a docker-compose.yml in the AWS install? (I am guessing there is, which allows commands like docker-compose stop
etc.). If so, can you paste what it looks like here.
thanks,
-brady
Where would I look for the docker-compose.yml?
Also, would it be safer to create a new EC2 instance and then migrate the data over to the new instance somehow?
Something like Error Upgrade 5.0.1 to 5.0.2 could be a time-consuming problem for me if I’m doing the upgrade on the production instance.
–Ralf