Project

General

Profile

Actions

Bug #1523

closed

Document:Dropbox student

Added by Ludwig Theunis over 13 years ago. Updated over 12 years ago.

Status:
Bug resolved
Priority:
Normal
Target version:
Start date:
17/06/2010
Due date:
% Done:

100%

Estimated time:
Complexity:
Normal

Description

When publishing in the document tool, the published document is not visible for the student himself.
The student does not have access to his published document in the course, he only sees the object in his repository..
It is also not possible to select the CourseGroup he/she is member off.

Actions #1

Updated by Ludwig Theunis over 13 years ago

Correction: The student does not see the published object when he selects other users/teachers. He can't publish to himself.
When selecting everybody, the published object is also visible for the publishing student.

Actions #2

Updated by Sven Vanpoucke over 13 years ago

  • Status changed from New to Needs testing
  • Assignee set to Sven Vanpoucke
  • % Done changed from 0 to 100
Actions #3

Updated by Ludwig Theunis over 13 years ago

  • % Done changed from 100 to 0

I've added a teacher and a student.
The teacher created a course and added the student to the course.

The student published a document in the dropbox. The student used Select Groups/users and selected the teacher not ('Everybody').
He still can't select himself: so the published document is not visible to the student in the course.
As expected the document is visible to the teacher.

The document is visible in the students repository but is not visible for the student in the dropbox of the course.

I've checked this in the beta and with the latest version, same result...

So it is not fixed... :-(

Actions #4

Updated by Anonymous almost 13 years ago

  • Target version changed from 2 to 21

I tested this again and now the teacher doesn't see the document as well.
The document does appear in the student's repository.
So it's definitely not fixed.
(tested in the latest version)

Actions #5

Updated by Stefaan Vanbillemont almost 13 years ago

  • Status changed from Needs testing to Assigned
Actions #6

Updated by Sven Vanpoucke over 12 years ago

  • Status changed from Assigned to Needs testing
  • % Done changed from 0 to 100

Added a published for me and published by me button on the stable

Actions #7

Updated by Stefaan Vanbillemont over 12 years ago

  • Project changed from Chamilo LCMS Connect to Courses
  • Category deleted (2)
Actions #8

Updated by Stefaan Vanbillemont over 12 years ago

  • Assignee changed from Sven Vanpoucke to Ludwig Theunis

Ludwig,

Can you retest this?

Actions #9

Updated by Ludwig Theunis over 12 years ago

  • % Done changed from 100 to 0

Functional this ok now. As a student publishes something he can find this, but...

But with this change the total documents tool is become a dropbox like tool. Meaning the objects published by a user are seperated from the objects published to the user.

If there was one thing anoying on the dropbox in the past then it was this. Is there no other posibility to have alle objects in the documents in one tree.
You have the publishedID and publishedFOR column to see which user published wath and for which users. Otherwise you could delete those two columns...

Also when you publish something from inside a course, why do you have to search the users, I understand you have this possibility in the repository. But when you do this from inside a course, you've allready limited the users from which you would want to select.

Actions #10

Updated by Stefaan Vanbillemont over 12 years ago

  • Target version changed from 21 to 2.1.0
Actions #11

Updated by Ludwig Theunis over 12 years ago

  • % Done changed from 0 to 100

I withdraw my previous remarks on the separation between 'publish for' and 'publish by'. The more I think about the more I can see the point of it...
Because the object in real isn't stored in the course but in the users repository it is indeed better to make the distinction between both.

Actions #12

Updated by Stefaan Vanbillemont over 12 years ago

  • Status changed from Needs testing to Bug resolved
Actions

Also available in: Atom PDF