phplinuxredcap

What is a non-versioned file?


I've got a php program, on my debian server. If set it up and changed the php version to 8.1. Now the server is giving me an error message:

Some non-versioned files are outdated - WARNING: One or more files that are not included in REDCap's version directory but reside in your web server's main REDCap directory were found outdated, and thus need to be replaced. Click the download button below to download a zip file that contains the files you need to replace.

I want to know what a non-versioned file is, so I can fix that problem.

After downloading that .zip file I took a look inside and I realized it was empty... I didnt change anything in the Servers main directory...

Thank you


Solution

  • In REDCap server administration, application files can be either versioned or non-versioned. Versioned files are those files that exist within a directory named for the version, i.e. redcap_v13.1.0. Non-versioned files are those that are outside this versioned file structure, in REDCap's base directory.

    Below is a sample directory structure (altered so this answer does not expose the file structure of a non-open application):

    .
    
    └──redcap
       ├── init.php
       ├── index.php
       ├── redcap_v13.1.0
       │   ├── tests.ini
       │   ├── unit.php
       │   └── api.bat
       ├── tmp
       │   └── index.php
       └── debug.php
    

    Files tests.ini, unit.php and api.bat are versioned, and everything else is non-versioned.

    Upgrades to the REDCap application mostly affect versioned files, but occasionally an upgrade will modify non-versioned files, which the application itself is incapable of directly modifying on the server. In these cases the application directs the administrator to download a zip file containing the modified non-versioned files and instructions on installing them.

    If this zip file was empty for you, then that might indicate an incomplete upgrade. Some admins in the community have recently advocated for publishing hashes alongside releases to allow admins to ensure that the release has been correctly downloaded.

    If this issue persists (though your comment suggests not), then I'd recommend taking this issue to the REDCap Admin Community, which you ought to have access to if you can access the code.