[itslenny]

Since upgrading, files uploaded to a case using the Multplefileuploader control gives the below error when some else tries to download

pm32_accessdenied.png (9.67 KiB) Viewed 9223 times

If I start a another case, upload files, submit, open again at next task, I can download. Seems like the files are locked with permissions in some way which is different from how 3.1.* worked?

Permissions on CentOS for the respective file are as follows and appear correct.

-rw-rw-rw-. 1 apache apache 92922 Jun 23 05:00 638087518594cd8b34a9ca6037091251_1.jpg

So this appears to be a new permission within ProcessMaker?

[itslenny]

So, I found the code causing this problem.

/opt/processmaker/workflow/engine/methods/cases/cases_ShowDocument.php

Line 66

Code: Select all

if (defined('DISABLE_DOWNLOAD_DOCUMENTS_SESSION_VALIDATION') && DISABLE_DOWNLOAD_DOCUMENTS_SESSION_VALIDATION == 0) {

    if (!$oAppDocument->canDownloadInput($_SESSION['USER_LOGGED'], $_GET['a'], $docVersion)) {
        G::header('Location: /errors/error403.php');
        die();
    }
}

Seems the either DISABLE_DOWNLOAD_DOCUMENTS_SESSION_VALIDATION variable is not set appropriately, or the canDownloadInput function is returning the true, so I have simply commented out this block for the time being.

Would be good to know how and where these items can be changed.

[amosbatto]

So this appears to be a new permission within ProcessMaker?

Yes, it's a new setting in PM. You can disable it in the env.ini file. See: http://wiki.processmaker.com/3.1/faq#al ... t_download

[itslenny]

Thanks for the information. My issue is that this message appears for the current person assigned to the task, when they have a valid login session. Only the person who added the file seems to be able to download.

The functionality you linked to shouldn't apply in this instance.?

[amosbatto]

If you give the user Process Permissions to the Input Document or DynaForm where the file was uploaded, does that solve the problem?

[azalea45]

Hi All,

just a quick point that we discovered with the copy env.ini.
You need check the file permissions on the file after you have copied it, if necessary, change to match the directory.

[gbalbach]

So this appears to be a new permission within ProcessMaker?

Yes, it's a new setting in PM. You can disable it in the env.ini file. See: http://wiki.processmaker.com/3.1/faq#al ... t_download

And FYI we just went through this as well - that setting also fixes web entry errors when upgrading to 3.2 if you happen to have a v2.x process using a web entry form that happens to do queries against the PM tables, if the disable_download_documents_session_validation = 1 is not set/left blank or 0 then you can't query any tables since the web entry doesn't have a logged in / validated session.

From support, they suggest anyone going to v3.2 that has any legacy 2.x processes to set that disable setting in the env.ini file.

[gbalbach]

So this appears to be a new permission within ProcessMaker?

Yes, it's a new setting in PM. You can disable it in the env.ini file. See: http://wiki.processmaker.com/3.1/faq#al ... t_download

And FYI we just went through this as well - that setting also fixes web entry errors when upgrading to 3.2 if you happen to have a v2.x process using a web entry form that happens to do queries against the PM tables, if the disable_download_documents_session_validation = 1 is not set/left blank or 0 then you can't query any tables since the web entry doesn't have a logged in / validated session.

From support, they suggest anyone going to v3.2 that has any legacy 2.x processes to set that disable setting in the env.ini file.

Well never mind, that didn't fix the issue, support is still looking into it - if you have a valid/logged in session in another browser tab then it works but if you open a fresh browser that hasn't logged into PM yet, you can't query the PM user tables.

[gbalbach]

So this appears to be a new permission within ProcessMaker?

Yes, it's a new setting in PM. You can disable it in the env.ini file. See: http://wiki.processmaker.com/3.1/faq#al ... t_download

And FYI we just went through this as well - that setting also fixes web entry errors when upgrading to 3.2 if you happen to have a v2.x process using a web entry form that happens to do queries against the PM tables, if the disable_download_documents_session_validation = 1 is not set/left blank or 0 then you can't query any tables since the web entry doesn't have a logged in / validated session.

From support, they suggest anyone going to v3.2 that has any legacy 2.x processes to set that disable setting in the env.ini file.

Well never mind, that didn't fix the issue, support is still looking into it - if you have a valid/logged in session in another browser tab then it works but if you open a fresh browser that hasn't logged into PM yet, you can't query the PM user tables.

Hi folks, FYI I was just informed by support that this issue is fixed in the upcoming 3.2.1 version.