03/06/2007 11:48 PM |
|
ok so heres the question. we are running DNN 4.4.0 and DMX 3.04.08. whenever someone uploads a file and/or creates a folder, when they check Private, no one, not even the admin or host login can see it.
any ideas on this? and how a super user can not even see these files. i remember reading that the admins and the user that labeled it as private could see the files.
|
|
|
|
Peter DonkerVeteran Member Posts:4536
03/08/2007 8:34 PM |
|
Please read this:
.... cut
|
|
|
|
03/08/2007 10:52 PM |
|
thank you for the response peter. but i have a feeling this was not the response you meant to give.
|
|
|
|
Peter DonkerVeteran Member Posts:4536
03/09/2007 10:31 AM |
|
Josh, I can't reproduce the error you report. I'm using 04.04.01. I can only guess it is something external and am wondering why you're still on 04.04.00. That's why I pointed you to that. The DNN minor releases are 'bugfix' releases that should be 'safe' to implement without breaking 3rd party modules. The Core team takes caution not to change anything in the API when making a minor version update. I think it's good practice to try to keep up to date with those releases. When something malfunctions, it's the first thing to look at. Peter
|
|
|
|
Peter DonkerVeteran Member Posts:4536
|
03/13/2007 9:06 PM |
|
ok, today we upgraded our portal to 4.4.1. we did uninstall the dmx module first the reinstalled after the upgrade to the new dnn version. we are still having the same problem.
i will attempt to explain my position better. i had one browser(ie7) open and logged in as the host user. another browser (firefox) logged in a josh, me a regular user. i uploaded a test folder and then added files to it. as the host i can see everything fine.
as josh, i made another folder and uploaded files into it. i made this one private. as the host i could not see inside the folder. it gives me this error:
"A critical error has occurred. You don't appear to have permission to see this item. Please check your login status."
all other content dissapears from the the page except the links on the top of the page. the powers that be have told me they like everything else so much about this module that we are going to keep plugging away at it. but, man am i stumped on this one. i do have a .net developer on staff, so now matter how convoluted it may be for the fix, we are willing to try it.
thanks everyone.
|
|
|
|
Peter DonkerVeteran Member Posts:4536
03/14/2007 11:20 PM |
|
Josh, Sounds like something is wrong with the authentication (lot's of stuff is happening after all when you log in and off). I can't reproduce it here (given that having 2 browsers open with different accounts is a highly unlikely usage scenario). I can't debug an error I can't reproduce as you can understand. Let me know if you run into issues regarding 'private' settings in a regular scenario (i.e. using a single browser and logging in as one user at a time). Peter
|
|
|
|
03/15/2007 2:16 PM |
|
other testers in our company are just using one browser and logging in and logging out. call me lazy, lol, i was using my dual screens with 2 browsers to speed up the process of testing. yes, not a likely scenario but man is it easy when i make a change in one and F5 the other one to see changes. :)
but, all other testers are getting the same errors. i am the only one using 2 browsers to test. so it is consistent with everything else.
i understand the mystical error i am getting is hard to fix when i appear to be the only one. my .net developer is poking around at it. what concerns me is its stumping both of us. i will have him look into the authentication side of things though and let everyone know what we figure out.
|
|
|
|
Peter DonkerVeteran Member Posts:4536
03/15/2007 10:57 PM |
|
Josh, I've been able to reproduce this and I'll fix it a.s.a.p. A fix will be put in 03.04.09. Sorry about the fuss. Peter
|
|
|
|
12/17/2007 11:50 PM |
|
ok, we have been revisiting this. we still have not upgraded to the 03.04.09 yet and would like to, as we are still seeing the same errors. we are on DNN 04.05.05 now. is that going to make a difference. and what about 04.07.00? we are working on a portal with that version and may be getting DMX for that one as well.
|
|
|
|
Peter DonkerVeteran Member Posts:4536
12/18/2007 7:51 PM |
|
Josh, You should be fine with both versions. DMX 3 is currently compiled against 04.05.03 if I remember correctly so anything up from there should be good to go. Peter
|
|
|
|
01/03/2008 10:15 PM |
|
well we got the latest build for 3.x. and yes that fixed this problem. yay!
another question. is it possible to allow other people to see those private items without just making the user an admin? we could really use this for internal usage only. we have many people that need to access private items but we would like to not let them have access to any of the admin controls for DNN. basically a user that has admin rights for this module but not for the any other portion of the site.
i know we could just turn off the apply 'permission by admin only' checkbox. as this portal is meant for the world to use we feel that too many people would make mistakes. we are attempting to use this in place of our current very hands on ftp policies. we are trying to be as hands off as possible after the setup of this module.
hopefully that makes sense enough to be able to answer the question.
|
|
|
|
Peter DonkerVeteran Member Posts:4536
01/08/2008 7:39 PM |
|
Hi Josh,
DMX 3 does not have 'user-based-permissions' like DMX 4 and it never will. The 'IsPrivate' setting was introduced as a way to mimic this, but all it really does is just flag a document, nothing more. It is not a 'forward bound solution'. If you really need to further tune your permissions (the answer to your request above is No, by the way) I suggest you look at DMX 4. It is much more fine-grained in permissions.
Peter
|
|
|
|