Note related to default display creation.

diff --git a/KNOWN_ISSUES.txt b/KNOWN_ISSUES.txt
index 1daab64..2cf3ec8 100644 (file)
--- a/KNOWN_ISSUES.txt
+++ b/KNOWN_ISSUES.txt
@@ -89,4 +89,21 @@ Known Issue http://drupal.org/node/207859
     secure pages doesn't know about. When trying to make non-secure ajax calls
     from a secure page, the browser denies the call.
   Solution:
-    The solution is to simply add panels/* to your Secure Pages configuration.
\ No newline at end of file
+    The solution is to simply add panels/* to your Secure Pages configuration.
+    
+Known Issue
+  When editing a secondary default panels display in panels_page for the first
+  time, the export/saving of the page from the root default can be irregular,
+  as can the spawning of a type-specific display from the secondary default.
+  
+  Cause:
+    Gremlins in panels_page's current display selection code.
+  Solution:
+    If you really, really need the functionality, then just force-save the root
+    default, the secondary default, and then the type-specific until you've got
+    three different ones. Once the different ones are instanciated, they'll stay
+    fully separate and work just fine. The developers don't plan to fix this
+    issue, at least on the 2.x branch, because the 2.x branch is being
+    deprecated for D6 onwards. 
+  Solution #2:
+    Figure it out and file a patch!
\ No newline at end of file