Closed GoogleCodeExporter closed 8 years ago
From the log, it seems like this folder does not exist:
"/home/solext5/nbasw-atsnb.ca/securedata".
Original comment by samuli.j...@gmail.com
on 26 Mar 2014 at 11:47
I checked the server and the folder is there. IT also had the Test folder I
created in it along with a .png I uploaded.
Why do I still get "Request Failed" when I try to delete a user, change a
password or even delete a file? Is there a word around for this?
Original comment by ehdesig...@gmail.com
on 26 Mar 2014 at 8:19
Screenshot of the error I get.
Original comment by ehdesig...@gmail.com
on 26 Mar 2014 at 8:22
Attachments:
The screenshot does not really help at all, only error logs.
The log you gave seems to be for adding new folder, and does not have help
other cases (delete user, change password etc). Could be anything, usually this
kind of errors are due to this:
https://code.google.com/p/mollify/wiki/Troubleshooting#Some_operations,_like_ren
ame_or_editing_descriptions,_don't
You seem to have missed the actual error description from the log above (there
should be something like "Invalid folder definition, path does not exist"), but
the error stack trace is quite clear that the folder does not exist, or PHP
does not have rights to access it. Make sure you use absolute paths in folder
definitions, so that it does not point to wrong location.
Original comment by samuli.j...@gmail.com
on 26 Mar 2014 at 8:47
Figured it out. There was in issue with ModSec on the sever. Changed a rule and
I am good to go. Thanks!
Original comment by ehdesig...@gmail.com
on 28 Mar 2014 at 12:18
Great
Original comment by samuli.j...@gmail.com
on 29 Mar 2014 at 6:04
I am running on Windows Server 2012 R2, mysql. I have exactly the same error.
Not sure how to solve it. Can anyone help?
Original comment by sjth...@gmail.com
on 3 Dec 2014 at 4:21
#7 Same error? Do you mean "request failed" or "folder does not exist"?
The request failed is not an error itself, it is only a signal in the UI that
something happened but it does not yet tell what. So if this is it, then it's
probably not "same error", just dig out the error log and solve it from there.
This exact issue has been closed as there was only configuration error so
nothing to do in Mollify side.
Original comment by samuli.j...@gmail.com
on 3 Dec 2014 at 7:35
Original issue reported on code.google.com by
ehdesig...@gmail.com
on 26 Mar 2014 at 2:21