I have just done a install of nForum
v1.5 onto a clean Umbraco v4.7.2 build and following this I get the below error
when I try to move items in my Media section from one folder to another:
Server Error in '/' Application.
No Document exists with Version
'0dcf2a64-0ab9-467f-b55d-ac894e46591c'
If you reload the nodes the move has
actually been successful, however the user seeing a YSOD is obviously not
ideal. The issue is defintely caused by the nForum install as I was
explicitly testing moving media items prior to the install (everything fine)
and then after the install (when I now see the errors above). In addition
if you try to delete media item you get a "No Document Exists
error..." in the bottom right corner, however again if you reload the
nodes the delete is successful.
Any ideas as to what in
the nForum build that would be causing this? As I said before this
is a clean build, so I haven't added any additional properties to the out of
the box media types (file, folder & image).
Here's what he said (from the email notifications I got at the time):
"Sorry for jumping in on the conversation, but we were having the exact same issue with the latest version of nForum (1.2 at the time of writing this). The reason is that a delete is really just a move to trash. nForum tries to process all document moves in case they relate to its document structure. In doing so, it assues every move is a document move... It's not difficult to persuade it to be a little less greedy; all you need to do is check the object type in the DocumentAfterMove method inside nForumEvents.cs:
I am now trying v1.6 on the umbraco 4.9.1 and am also getting this issue. Hopefully the package developers will be able to fix this and make a new dll available (probably for 1.5 and 1.6) so that we can use the package successfully.
Move/Delete Media Items Issue Following Install on Clean v4.7.2 Site
Hi All.
I have just done a install of nForum v1.5 onto a clean Umbraco v4.7.2 build and following this I get the below error when I try to move items in my Media section from one folder to another:
Server Error in '/' Application.
No Document exists with Version '0dcf2a64-0ab9-467f-b55d-ac894e46591c'
If you reload the nodes the move has actually been successful, however the user seeing a YSOD is obviously not ideal. The issue is defintely caused by the nForum install as I was explicitly testing moving media items prior to the install (everything fine) and then after the install (when I now see the errors above). In addition if you try to delete media item you get a "No Document Exists error..." in the bottom right corner, however again if you reload the nodes the delete is successful.
Any ideas as to what in the nForum build that would be causing this? As I said before this is a clean build, so I haven't added any additional properties to the out of the box media types (file, folder & image).
As always, thanks in advance.
Cheers,
Dave.
Hi Dave
Did you make any progress with this issue?
I had this problem with v1.2 and got a fix from Dav on a thread which now seems not to exist any more - http://our.umbraco.org/projects/website-utilities/nforum/bugs/18411-Error-on-DeleteMove-Media-obj-after-installed-nFoum?p=0#comment96720.
Here's what he said (from the email notifications I got at the time):
"Sorry for jumping in on the conversation, but we were having the exact same issue with the latest version of nForum (1.2 at the time of writing this). The reason is that a delete is really just a move to trash. nForum tries to process all document moves in case they relate to its document structure. In doing so, it assues every move is a document move... It's not difficult to persuade it to be a little less greedy; all you need to do is check the object type in the DocumentAfterMove method inside nForumEvents.cs:
static void DocumentAfterMove(object sender, MoveEventArgs e) {
#region Forum Topic Move Events
var sid = (CMSNode)sender;
if (sid.nodeObjectType != Document._objectType)
return;
var s = new Document(sid.Id);
/* rest of the method */
}
"
I am now trying v1.6 on the umbraco 4.9.1 and am also getting this issue. Hopefully the package developers will be able to fix this and make a new dll available (probably for 1.5 and 1.6) so that we can use the package successfully.
is working on a reply...