The redcap_deployment does not have a good method for deploying REDCap's "non-versioned files" during an upgrade. One will get messages like this:
While there are reasons this warning could be a false-positive, there are plenty more reasons why it is a legitimate alert that should be addressed. On this particular host, these files were out of date:
./Instructions.txt
./redcap/ehr.php
./redcap/index.php
./redcap/redcap_connect.php
./redcap/cron.php
./redcap/surveys/index.php
./redcap/api/index.php
./redcap/api/help/index.php
Instructions.txt is not a problem, but every other file is.
One possible solution is to use the redcapX.Y.Z.zip files instead of the redcapX.Y.Z_upgrade.zip. With the recent change that excludes the database.php file found inside redcapX.Y.Z_upgrade.zip during upgrade (commit # 9db03a2) this might be a viable solution.
The redcap_deployment does not have a good method for deploying REDCap's "non-versioned files" during an upgrade. One will get messages like this:
While there are reasons this warning could be a false-positive, there are plenty more reasons why it is a legitimate alert that should be addressed. On this particular host, these files were out of date:
Instructions.txt is not a problem, but every other file is.
One possible solution is to use the
redcapX.Y.Z.zipfiles instead of theredcapX.Y.Z_upgrade.zip. With the recent change that excludes thedatabase.phpfile found insideredcapX.Y.Z_upgrade.zipduring upgrade (commit # 9db03a2) this might be a viable solution.