{"action":"created","issue":{"url":"https://api.github.com/repos/openwebwork/webwork2/issues/666","labels_url":"https://api.github.com/repos/openwebwork/webwork2/issues/666/labels{/name}","comments_url":"https://api.github.com/repos/openwebwork/webwork2/issues/666/comments","events_url":"https://api.github.com/repos/openwebwork/webwork2/issues/666/events","html_url":"https://github.com/openwebwork/webwork2/pull/666","id":123180207,"number":666,"title":"Yet Still Even More Release 2.11 Bugfixes","user":{"login":"goehle","id":1774907,"avatar_url":"https://avatars.githubusercontent.com/u/1774907?v=3","gravatar_id":"","url":"https://api.github.com/users/goehle","html_url":"https://github.com/goehle","followers_url":"https://api.github.com/users/goehle/followers","following_url":"https://api.github.com/users/goehle/following{/other_user}","gists_url":"https://api.github.com/users/goehle/gists{/gist_id}","starred_url":"https://api.github.com/users/goehle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/goehle/subscriptions","organizations_url":"https://api.github.com/users/goehle/orgs","repos_url":"https://api.github.com/users/goehle/repos","events_url":"https://api.github.com/users/goehle/events{/privacy}","received_events_url":"https://api.github.com/users/goehle/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-12-20T20:02:50Z","updated_at":"2015-12-22T13:24:17Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/openwebwork/webwork2/pulls/666","html_url":"https://github.com/openwebwork/webwork2/pull/666","diff_url":"https://github.com/openwebwork/webwork2/pull/666.diff","patch_url":"https://github.com/openwebwork/webwork2/pull/666.patch"},"body":"-  No longer show progression message on subproblems which don't count towards the parent grade. \r\n  -  To test: Create a just in time set with restricted progression and have a problem with two child problems, one which counts for the parent grade and one which doesn't.  When viewing the problems you should get a \"you cannot proceed\" message on the problem page for only the one which counts for the parent grade. \r\n\r\n-  Fixed a bug where restricted progression didnt work properly. \r\n  -  To test:  Have problems 1, 1.1 and 1.2 with all three problems having a max attempts limit and *both* child problems must count toward the parent.  Run out the attempts on the parent problem and a subproblem, but get the other subproblem right while still having attempts remaining.  Before the patch you will not be able to proceed to the next problem and after you will. \r\n\r\n-  Changed how scores are displayed on Problem Set page for just in time sets.  Now status of all problems is shown, as well as adjusted status for top level problems and  a flag if child problems count to the parent grad.e \r\n  -  To test:  create a just in time set and look at the problem set page.   Check that columns all work. \r\n\r\n-  Cleaned up single set csvs in \"Scoring Tools\".  \r\n  -  To test:  after the patch you should see a due date and due time in single set scoring csvs.  Also, for jitar sets you should see the problem number, not some big integer.  \r\n\r\n-  Added some code to improve formatting of the Problem Set page when the window is smallish but not tablet sized (about 1000px wide).  For just in time sets the Problems table was getting obscured by the Set Info page.  I reduced the padding on that table.  This doesn't get rid of the clipping but it minimizes it.  \r\n  -  To test:  Create a just in time set and view the ProblemSet page and shrink your window.  You should see the table get compressed, then there will be about a small interval where the set info box clips over the table, then the window should go into \"phone mode\" and the Set Info box should drop below the table. \r\n\r\n-  Changed code so that User Settings is always shown, since it pretty much always has something the user can do.  \r\n\r\n- Small CSS Tweaks:  \r\n  -  Tweaked the masthead css so that it no longer overflows the container.  This should get rid of the bottom scrollbar that appears no matter how wide the window is.  Check that the login button renders nicely and there is no scrollbar. \r\n  -  On IE the vertical scrollbar actually covers up page content.  This is annoying in the library browser where the scrollbar can cover up the \"X\"'s and make them hard to use.  Added some css to inset the library browser icons a bit to avoid this.  Check to see that it renders nicely.  \r\n -  The \"skip to main content\" link now skips to the page title.  Before it skipped to before the breadcrumbs.  "},"comment":{"url":"https://api.github.com/repos/openwebwork/webwork2/issues/comments/166616510","html_url":"https://github.com/openwebwork/webwork2/pull/666#issuecomment-166616510","issue_url":"https://api.github.com/repos/openwebwork/webwork2/issues/666","id":166616510,"user":{"login":"mgage","id":1203580,"avatar_url":"https://avatars.githubusercontent.com/u/1203580?v=3","gravatar_id":"","url":"https://api.github.com/users/mgage","html_url":"https://github.com/mgage","followers_url":"https://api.github.com/users/mgage/followers","following_url":"https://api.github.com/users/mgage/following{/other_user}","gists_url":"https://api.github.com/users/mgage/gists{/gist_id}","starred_url":"https://api.github.com/users/mgage/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mgage/subscriptions","organizations_url":"https://api.github.com/users/mgage/orgs","repos_url":"https://api.github.com/users/mgage/repos","events_url":"https://api.github.com/users/mgage/events{/privacy}","received_events_url":"https://api.github.com/users/mgage/received_events","type":"User","site_admin":false},"created_at":"2015-12-22T13:24:17Z","updated_at":"2015-12-22T13:24:17Z","body":"I have an issue with showing the User settings all of the time. Set the permissions so that students can change email addresses and passwords (but guests can't) -- this is the default permission setting. With the new system guests can change email (and perhaps their password if they guess their current one).\r\n\r\nIf you are going to expose the User settings page then the individual entries on that page should be controlled by permission settings -- and preferably have some visual sign as to whether or not they can be changed."}}