title: Can a UIViewController support more interface orientations than its parent in iOS 6?
body: <p>The changes to auto-rotation in iOS 6 seems to have made this incredibly difficult, or impossible. They seem to be pushing the philosophy that a child view controller should not have to override the auto-rotation behavior of its parent view controller. This makes it difficult to accomplish what I am trying to do:</p>
  
  <ul>
  <li>I have a view controller that must be displayed portrait.</li>
  <li>It pushes another view controller modally that is a simple image viewer, but I want this view controller to be able to rotate to any portrait or landscape orientation (for obvious reasons)</li>
  <li>When the child view controller is dismissed (regardless of its current orientation), the parent view controller should remain in portrait orientation</li>
  </ul>
  
  <blockquote>
    <h3>Relevant Apple Documentation from UIViewController class reference</h3>
    
    <p>In iOS 6, your app supports the interface orientations defined in your app’s Info.plist file. A view controller can override the supportedInterfaceOrientations method to limit the list of supported orientations. Generally, the system calls this method only on the root view controller of the window or a view controller presented to fill the entire screen; child view controllers use the portion of the window provided for them by their parent view controller and no longer participate in directly in decisions about what rotations are supported. The intersection of the app’s orientation mask and the view controller’s orientation mask is used to determine which orientations a view controller can be rotated into.</p>
  </blockquote>
  
  <p>I've thought about using transforms to simulate rotation in the child view controller, but honestly, I feel like there should be a better way, and would like to avoid that if <em>at all</em> possible.</p>
  
  <p>It seems that any in order for any child view controller to support an interface orientation, its parent view controller (presented modally or otherwise) must now also support that interface orientation.</p>
  
  <p>Am I missing something simple here? Is this as ridiculous as it seems?</p>