-
-
Notifications
You must be signed in to change notification settings - Fork 166
Ww3 feature/problem set details #598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ww3 feature/problem set details #598
Conversation
… same date/times as the regular problem set dates.
…tab was reloading all the user data on a render (like resizing the window).
… change the properties. Added the user data inside a scrolling table.
…oesn't actual go to that view.
…from CourseManager and ProblemSetManager to better separate code. Also moved AssignmentCalendar to a view for reuse.
…3-feature/problem-set-details Conflicts: webwork3/lib/Routes/Course.pm webwork3/public/js/apps/CourseManager/main-views/ProblemSetDetailView.js webwork3/public/js/apps/util.js
… MainView. This creates a new calendar called CourseCalendar, which has an AssignmentCalendar within it.
|
|
If problem instances have a unique id in the database which does not depend on which set they are in or their order of appearance in the set then it should be possible to delete a problem. You can do that in the current webwork if you do not reorder the problems. If you reorder the problems then problem 7 would refer to one problem before the deletion and to another problem after the deletion and reordering. This causes confusion if some students do the problem before the change and others do it afterword. Not having a separate unique id for each problem in a course was the biggest flaw in the current database scheme. |
|
So as a follow up
|
|
I'll test it when I can. My classes have started so my available time has gone down considerably. |
|
I understand. I'm ramping up right now. I wasn't sure if you were waiting from me. |
…e server resulting in many put calls on a simple date change on the calendar.
|
Did you change something about how things set up with ww3? I'm having trouble getting it running via the fcgi pathway. The issue seems to be that the WEBWORK_ROOT environment variable is getting lost somehow. |
|
I had to add the lines to WeBWorK3.pm before any of the WeBWorK includes in order to get the fcgi path to work. I dont know why it used to work or what has changed. |
|
I'm also getting this error again when I load up the page. Last time it was caused by there being nonstandard permission level stuff. I got this error by changing a user to the TA permission level using the ww2 classlist editor. |
|
After getting ww3 up and running:
One subtle issue is when you mark correct for all students it also sets student overrides for every problem parameter for that student. Its not the worst but it means that future global changes to things like weight will not be reflected in the problem. The issue may be getting a "mergedUserProblem" from the DB and then putting that into the database with "putUserProblem". You should really use "getUserProblem" because it will have null fields for things which are not overridden. The same is true for sets. Keep an eye out and make sure you aren't using "putUserSet" with a set object generated by "getMergedSet". |
|
I'm getting errors that look like when I visit the problem page. Those "proctor" users were added by WeBWorK3. I think its not adding a permission record (with permission set to proctor) |
…an issue if a user is a T.A. and deleted some console.log statements.
|
Getting these fixed, but a couple of questions/comments:
|
|
|
On the set headers, are you getting errors in the network console of the browser (or in the dancer log)? |
… values that differ from the global problem values.
|
about the gateway quiz. What did you do to recreate it? I just did the following:
|
|
You shouldn't need the proctor id in that case. Was adding permissions something that wasn't happening earlier and was fixed? |
|
I had the permission problem fixed a couple of weeks ago. Any idea why it's asking for the proctor_id? |
I did pull develop (with jitar) into ww3 so that may have caused issues. |
|
I just noticed those two errors in firefox about unreachable code. Those are in libraries, so I won't worry about those. I'll pull ww3 in again and do more testing to see if I can reproduce your errors. |
|
OK. For more specific things to test
|
…3-feature/problem-set-details
… care of some issues in deleting and reordering.
|
I'm still having trouble with the set headers, but this pull is too unwieldy. It fixes enough stuff and has enough improvements that I'm just going to merge it. |
I guess I forgot to put in this pull request. Overall this updates the Problem Set Details views with many bug fixes. This includes:
This clears up issue #286
A couple of questions about issue #472:
Thoughts?