Turns out this statement breaks on the less recent mariadb/mysql versions. See here for details: OpenEMR 5.0.2 Patch
(as discussed there, luckily this doesn’t impact the patch except for not loading the covid codes; I am planning to post a fixed patch soon that does not have this issue)
Nope.
About says 5.0.2-1 and confirmed in version.php
‘’’$v_major = ‘5’;
$v_minor = ‘0’;
$v_patch = ‘2’;
$v_tag = ‘’; // minor revision number, should be empty for production releases
// A real patch identifier. This is incremented when we release a patch for a
// production release. Note the above $v_patch variable is a misnomer and actually
// stores release version information.
$v_realpatch = ‘1’;’’’
Ran “a2enmod rewrite” followed by; “systemctl restart apache2”
Re-Ran patch-2 still reports it ran Patch-1
Manage Module Problem symptoms changed to 403 Forbidden (no access) so which file needs it’s permissions updated?
I just did first time patch installation on Linux Mint. Very easy process, and everything looks good.
Just have a question, about files needs to be removed after installation.
Please let me know if the files marked in red needs to be removed, from OpenEMR directory.
Yep those file can go. all patches will include sql_patch.php. this is for security. also pretty sure if you are finish with all upgrades, it is safe to remove sql_upgrade.php. setup.php should already be empty if I remember correctly.
We are releasing a new security patch in a couple days so, beware.