Comment 2 for bug 379968

I imagine this comes up if the section is not assigned to a term, but we need to handle this kind of error gracefully and explain the problem to the user -- ideally linking directly to the page they need to go to to solve the problem. Also, I have to get caught up to this point in the documentation...