#25 install panels

sites/all/modules/contrib/panels/CHANGELOG.txt

@@ -0,0 +1,39 @@
+CHANGELOG for Panels 3.0 for Drupal 7
+Panels 7.x-3.0-dev
+==================
+#1025716: Panels fields broken in last update.
+#1056464 by EclipseGc: Fix broken delete statement in mini panel delete.
+#954324 by EclipseGc: Fix broken delete statement in mini panel uninstall.
+#1008120: "classes" not passing through to rounded shadow pane stylizer style, preventing style from working.
+
+Panels 7.x-3.0-alpha2 (10-Jan-2011)
+=====================
+
+#920266 by dereine: Typo in cache.inc caused wsods in rare circumstances.
+#879482 by mvc: Ensure Panels and CTools module files are loaded during update. Apparently could cause WSOD if not.
+#917614 by jskulski: IPE broken in IE.
+#906520: Improve CSS for rounded shadow boxes on IE7.
+#932632 by mikeytown2: Fix notice in .install file.
+#927840: Add clear-block to dashboard HTML to ensure themes do not do weird things to it.
+#869766: Fix occasional problem with flexible layout pushing the entire layout to the left in certain fixed-width only configurations.
+#949310: E_STRICT violation on declaration of render_pane() method of display renderers.
+#940002: Custom style modal was broken.
+#953484: Panes were not properly using classes array.
+#941532: panel nodes had some serious problems do to hook_node_*.
+#954324: Mini panels failed during uninstall.
+#827628: "Add content" dialog could lose content with the same title as other content.
+Fix the naked style to support content that needs to be rendered.
+#958072: Fix panels_node_node_access to not throw warnings on menu access tests.
+#965286: Panel node update was trying to use db_insert() instead of db_update().
+#964334: Panels breaks views' row styles with the panels fields style.
+#941802: Fix radio layout butotn.
+#980696 by das-peter: Update calls to drupal_set_html_head() to D7.
+#961662 by Nick Lewis: Account for pager info in simple caching.
+#980870 by das-peter: CSS handling during caching broken.
+#970076: Remove old hook_update functions.
+#978768 by linclark: Fix notice with panel fields.
+#977296: Regions with _ such as with two column bricks would not save content.
+#987902: Fix flexible layout splitter resize brokenness.
+#967734 by das-peter and intoxination: Upgrade node_get_types() in wizard.
+#1020824: Finish fixing node template page wizard.
+Fix landing page wizard.

sites/all/modules/contrib/panels/KNOWN_ISSUES.txt

@@ -0,0 +1,91 @@
+
+Known Issue http://drupal.org/node/191771
+  'Node' panes can have two titles or have two title areas.
+  Cause: 
+    Content that comes into a pane is already formatted, and this happens
+    in theme('node'). theme('node') assumes it will be printing a title
+    most of the time. However, Panels wants the titles of panes to be
+    consistent, so it removes the title from the node to prevent your
+    node.tpl.php from printing it. The result is often an empty h2 which
+    has odd effects.
+  Solution:
+    Add an if statement to your node.tpl.php to prevent printing that h2
+    if $node->title is empty.
+
+Known Issue http://drupal.org/node/186454
+  Internet Explorer is really bad about making the rightmost panel
+  fall beneath the others.
+  Cause:
+    Internet explorer calculates margins and padding differntly from
+    everyone else, and this makes it entirely too easy for widths
+    to add up to greater than the amount of allotted space, despite
+    using percentage widths.
+  Solution:
+    There are two solutions to this problem:
+    1) In your theme, try to eliminate padding from the the <div>
+       that directly contains your content; you can do this by
+       adding an empty <div> inside it that surrounds the content
+       and very specifically is set to margin: 0 and padding: 0
+
+    2) if that doesn't work, override the widths of the panel-panel
+       divs and reduce them by 1 or 2%; usually this will give IE
+       enough space to quit pushing things around.
+
+Known Issue http://drupal.org/node/154351
+  TinyMCE, FCKEditor and other wysiwyg editors really blow up on Panels
+  content editing.
+  Cause:
+    The modal dialogs that Panels uses are very particular about javascript
+    and these editors are too much for them. Also, these editors get
+    cranky about complicated forms with several text areas.
+  Solution:
+    Disable these editors on all of your panels admin pages. The important
+    URLs are admin/panels/* and panels/ajax/*. More details instructions
+    may follow if someone familiar with these systems submits a patch at
+    the above drupal.org URL.
+
+Known Issue http://drupal.org/node/180650
+  The rounded corners style shows up as just a small graphic rather than
+  a full box around the panels as it shoujld.
+  Cause:
+    The rounded corners CSS relies on the ID for the panel, but the ID is
+    optional.
+  Solution:
+    Make sure your panel has an ID of some sort. With mini panels there is
+    no easy workaround as mini panels currently do not have IDs of their
+    own.
+
+Known Issue http://drupal.org/node/165745
+  You see a message similar to this:
+  Table 'drupal.panels_info' doesn't exist query: SELECT * FROM panels_info 
+  WHERE path = 'front_page_new' in...
+
+  The important piece of information is 'panels_info'.
+  Cause:
+    The Meta Tags module (also known as nodewords.module) directly reads the
+    the panels tables and modifies its forms to add the tags. Unfortunately
+    for this module, Panels has changed *greatly* in the leap from 1.0 to
+    2.0 and the tables aren't the same. However, the nodewords module doesn't
+    yet know this. Look in the nodewords issue queue for panels patches and
+    you should find something.
+
+Known Issue http://drupal.org/node/153399
+  The drag and drop content UI doesn't seem to work at all under Safari.
+
+  Cause:
+    Safari 2 has some serious problems with the javascript code.
+  Solution:
+    Upgrade to Safari 3 if possible. If not, use an an alternative browser
+    such as Firefox or Opera.
+
+Known Issue http://drupal.org/node/207859
+  When using the secure pages module, the Panels administrative UI gives 
+  unhelpful "An error occurred" popups when trying to add or edit content.
+
+  Cause:
+    The secure pages module tries to move the entire administrative section
+    of the site to HTTPS, but Panels' AJAX calls are using a path that
+    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.