Thanks for reporting this, Ray,

I just tested this on master and it seems it has been fixed.

On saving a new course as CC, user is redirected to recently created course page and not home page.
Can you please try it on recent build and let us know if this is resolved for you.

Hi,

This is still broken. Moodle 2.4 (Build: 20121203)

Thanks Ray,

Not sure what is wrong. I can't reproduce this issue.
If I login as CC and save changes. It redirects me to newly created course page.

Have you tried this with fresh copy of Moodle? If not can you please try it.

http://screencast.com/t/se1fOr7k

Clean site.

User is a CC in Misc category.

User is thrown out at site level. Ideally they need to be directed to course page (or enrolled users as before).

Taking user to system level confusing.

Thanks Ray,

I can reproduce it now. It has different behaviour when user click on "Add/edit courses" when he/she is in a course.

1. Log in as CC
2. Select an existing course
3. Click Site administration -> Courses Add/edit courses"
4. Click "Add a new course"
5. After saving user is redirected to newly created course.

I realized that we are adding "returnto=category" when user click "Add a new course" after selecting a category. This was done intentionally in MDL-23144.

Adding Aparup to this as he added this code and might want to add his 2 cents here.

OK, I read the other issue.

It depends on your view of what a course creator wants to do:

1. Create a course and do something in it.
2. Create a course and be taken back to where they came from 9perhaps to create another course).

I'd favour 1 as this made sense and was the default in 1.9 and early 2.x.

Neither approach will be universally correct.

Whichever approach is adopted it needs to be consistent for both methods.

Hi! Ray,

I agree that it should show newly created course to user if user doesn't have capability to enrol users.
Current patch will take user to enrol page (if user has enrol capability), else will show newly created course.

IMO this is more consistent approach, no matter where user clicked "Add a course" (category or course).

Your patch looks good Raj, here are just a few things:

1. Looking at the current behaviour and MDL-23144, cancelling the form brings you back on the correct category page. The proposed patch changes this behaviour by bringing back the user to the main category page.
2. Could you add some testing instructions checking the 'Cancel' action?
3. Also some testing instructions with a role which can enrol users, who should be redirected to the enrol page.

Many thanks!
Fred

Thanks Fred.... I totally missed that...
Let me revisit this.

Thanks Fred,

I have done required changes, back for your review.

As we discussed it IRL, I think that removing the returnto entirely to redirect to the course page will make some people happy, but some other not. Also considering that there are 2 different behaviours regarding that you are in course/index ou course/category, I think the best option would be to add a button on the course edit page which would display "Save and return". Reading the returnto value we redirect the user, and assume they were on the main category page when this value is empty. This patch would not be backported, but I don't think this is a problem.

Thanks Fred, that makes sense.

Will wait for Ray's feedback, before changing the patch.

I was looking at this again, and it seems there is no nice solution which can make everyone happy.

Case1: New site with no course/category.
After creating a new course and clicking save changes, (IMO) user will expects to see the newly created course and not category paqe.

Case2: User is in course and click on Add/edit course (from site administration which is not expanded)
In this case also, user should see newly created course and not category with courses.

Case 3: User is in category and click add a new course (Case you provided)
In this case user should return to category list if he/she can't enrol user. This seems to be correct case for CC who is just creating empty courses and probably not good for CC who is creating new course and want to create some activity within.

IMO: This bug should not be fixed as there is no good solution which can satisfy everyone. As different people will have different expectation, any solution will cause regression and some unhappy users.
Also, Adding an extra button will be confusing for existing user base and will have no meaning when user is updating a course.

Ray Lawrence If you think otherwise then let us know, else I will close this as "Won't fix".

FYI: Patch is attached, so user will be navigated to newly created course page. Feel free to use it, if you need that behaviour.

Sorry, I don't agree.

This needs fixing as behaviour should be predictable and not vary without any clue to the underlying logic.

With the current state of functionality the behaviour should be to proceed for the course for the reason outlined by me on 11/Dec/12 5:35 PM.

The proposal for an extra button makes sense as it leaves the next step with the user rather than us trying to predict their needs.

So "Save and view course" and "Save and return to category" would work.

I agree this would be confusing for teachers editing course settings so it need to be shown the first time the settings page is accessed only.

Thanks Ray,

I will put this discussion on Dev Chat and try get more feedback.
I am not sure, if adding an extra button for edge-case (CC adding course from category), is a good way to go about it.

CC gets enroled in new course as teacher, so IMHO he/she should be redirected to new course.
I am not sure how many users create empty courses and are enroled as teacher.

Will wait for more feedback.

OK, just trying to be flexible on this...

"CC gets enroled in new course as teacher, so IMHO he/she should be redirected to new course. I am not sure how many users create empty courses and are enroled as teacher."

So you agree with me...

How I see it (constant behavior):

• Anybody with create course perms click on a "add course" link from page xxx_source_xxx (xxx being any page).
• The edit (new) course page is shown, with some bits filled (for example the category when coming from a given category and so on). Out from the scope of this issue.
• Pressing cancel ALWAYS return the user to xxx_source_xxx.
• Saving always does => course enrollments (if the user has perms to) => show course. Always. It never returns to xxx_source_xxx, front page nor any other page.

That's the usual behavior I've get when creating courses with Moodle. It should not depend of being CC/Admin/Whatever. The only point where a check is necessary is to decide if, after saving, the course enrollments page is shown or the user goes straight to the course page.

So, "graphically":

xxx_source_xxx ---> edit (new) course ---> save >---> enrollments ---> view course
     ^                       |                    (optional, perm-based)
     |                       |
     |-------< cancel <------|

Constant (independent of roles), predictable (in my mind) behavior.

IMO that would make happy everybody BUT those course creators creating hundred of courses in a row. But that's another issue, let's sort it out separately if needed (after all they are just 1/2-clicks away from creating a new course via admin or we can provide them extra "create cours" actions in navigation everywhere).

Just my opinion based in my expectations/experience, for sure better than going back to the site page or category page.

Hope it helps, ciao

Thanks Eloy... but it doesn't always go to course enrolments. See http://screencast.com/t/se1fOr7k This user is a CC.

"Saving always does => course enrollments (if the user has perms to) => show course. Always. It never returns to xxx_source_xxx, front page nor any other page."

Isn't that always the case with default config as Use who is CC is auto assigned as Teacher when course is created?

Looking at the graph there, it seems we should redirect user to view course after creating new course.
Hence, current patch is fine. Will push it for peer-review again, so get another opinion.

This looks good to me Raj, pushing forward. (FYI, I don't think you need $CFG->wwwroot in moodle_url)

Grrr copy/paste.
Thanks Fred, have update branches.

The main moodle.git repository has just been updated with latest weekly modifications. You may wish to rebase your PULL branches to simplify history and avoid any possible merge conflicts. This would also make integrator's life easier next week.

TIA and ciao

Added Marina as watcher.

Did any of you look where this crazy behaviour came from? Please always try and look at git blame to find out the history, because it often is useful in working out why we ended up like we did and preventing us doing the same thing again. When we didn't write the code ourselves this is often the best way to work out why we ended up here.

Apparently it came from MDL-23144. Raj, could you check that this is going to be reintroducing a problem identified by that bug..

Hello Dan,

This has been identified before and we are taking care of the original problem (reported in MDL-23144)
Now behaviour is:

1. On clicking cancel, user will be redirected to where he/she came from
2. On clicking Save, user will be redirected to enrol page (if he/she has capability) or view newly created course. (As shown in graph by Eloy https://tracker.moodle.org/browse/MDL-32526?focusedCommentId=197486&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-197486)

Thanks for clarifying (point it out to me) Raj.

Integrated to 24, 23 and master, thanks everyone - this was an interesting issue!

Works as expected, passing.

Thanks everyone for sticking with this issue. Looking forward to adding this logical navigation to the Moodle 2.4 manual...

Surely you will be happy to know that your code is now part of Moodle upstream. Thanks, thanks!

Closing as fixed, ciao