This has just happened again. Even though the full path to the diskfile
attachment is in the record for the issue in the table, it tries to use the
path from the project setup. It looks like sometime in the past we must have
changed some of these locations or something and it is assuming the wrong path.
Why doesn't it use the full path to the file if its in the DB.
Maybe this is a basic question.... I always put the full path to the file in
the attachments field when creating projects (i.e.
/opt/mymantis/attachments/<myversionfolder>). Maybe I shouldn't be? Is it
supposed to be relative to mantis or something.
I am not really sure what is going wrong. I still think mantis code is
ignoring the full path to the file and using the projects attachment path to
try and find it.
ThxKM
From: KM <info...@yahoo.com>
To: mantis-help <mantisbt-help@lists.sourceforge.net>
Sent: Thursday, July 31, 2014 2:37 PM
Subject: Re: attachments/diskfile entry not updated when moving issues
OK. For now I was able to move all of my issues. I had to move the files to
the folder where the originating project attachments were expected to be. Then
I had to update the manits bug file table records so the 'diskfile' had no
path, only a filename, and so that the folder pointed to the originating
project's attachment folder (corresponding to where I moved the file).
Now moving the issue worked. I wonder how much this is going to keep
happening. I have thousands of issues in the DB so there is no way I can go
through all of these attachments and move them around... at least not easily.
We shall see how it goes. I recently (a few months ago) upgraded from 1.1.7
to 1.2.17. I hope I did not miss any steps. I don't think so, but this is not
the first issue that I have had.
Thank youKM
From: KM <info...@yahoo.com>
To: mantis-help <mantisbt-help@lists.sourceforge.net>
Sent: Thursday, July 31, 2014 12:25 PM
Subject: Re: attachments/diskfile entry not updated when moving issues
FYI - I noticed that now the moved entries are working for some updates -- I
see now that there is a diskfile and folder field in the table. for some
entries the full path to the file is in the diskfile field, e.g.
/opt/mantis/attachements/<file> instead of just <file>.
This is not the only issue though. even if I fix the field in the db to point
where the file actually is, it is still expecting it to be in the subfolder
where the attachements for the project are.
I am really not sure how it got this way.
I am having a hard time moving these last few issues.
Thank youKM
From: KM <info...@yahoo.com>
To: mantis-help <mantisbt-help@lists.sourceforge.net>
Sent: Thursday, July 31, 2014 12:15 PM
Subject: attachments/diskfile entry not updated when moving issues
I attempted to move a bunch of issues from one project to another. It failed
with the following:
Uploaded file could not be moved to the file storage directory. Directory
either does not exist or not writable to webserver.
Then below it shows more detail:SYSTEM WARNING:
'rename(/opt/mantis/attachments/proj40/4.2/269657e041cab6943f7623738c7c503b,/opt/mantis/attachments/proj43/269657e041cab6943f7623738c7c503b)
[function.rename]: No such file or directory' in
'/opt/mantisbt-1.2.17/core/file_api.php' line 1025
SYSTEM WARNING:
'copy(/opt/mantis/attachments/proj40/4.2/269657e041cab6943f7623738c7c503b)
[function.copy]: failed to open stream: No such file or directory' in
'/opt/mantisbt-1.2.17/core/file_api.php' line 1026
When moving my issue It is trying to copy the attachment
269657e041cab6943f7623738c7c503b from the "proj40/4.2" subdirectory of my
attachments folder to the attachments directory of my new project (the target
project for the move), "proj43".
Now theoretically this sounds good except that the file is not in a subfolder,
it is still in "attachments" directly. This issue was moved about 5 times to
different projects. The record in the DB (mantis file table) for this file
shows the correct location of the file directly in attachments. When you move
an issue it seems to be looking at the path set up for the current project and
not where the attachments actually are.
Or - maybe the attachments should have been moved before but were not ? I am
not sure.
Note that moving the file to where it expects it allows the issue to be moved
in most cases - BUT -- the location is not being changed in the mantis file
table.... so won't this happen again if we move the issue? I am thinking that
I need to just keep all of the attachments for my new project right at the top
level - and also going forward to avoid this issue.
Is anyone else having this problem and if show what did you do?
We are using mantis 1.2.17.
Thank youKM
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
mantisbt-help mailing list
mantisbt-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-help
