[4f375e3] | 1 | |
---|
| 2 | Known Issue http://drupal.org/node/191771 |
---|
| 3 | 'Node' panes can have two titles or have two title areas. |
---|
| 4 | Cause: |
---|
| 5 | Content that comes into a pane is already formatted, and this happens |
---|
| 6 | in theme('node'). theme('node') assumes it will be printing a title |
---|
| 7 | most of the time. However, Panels wants the titles of panes to be |
---|
| 8 | consistent, so it removes the title from the node to prevent your |
---|
| 9 | node.tpl.php from printing it. The result is often an empty h2 which |
---|
| 10 | has odd effects. |
---|
| 11 | Solution: |
---|
| 12 | Add an if statement to your node.tpl.php to prevent printing that h2 |
---|
| 13 | if $node->title is empty. |
---|
| 14 | |
---|
| 15 | Known Issue http://drupal.org/node/186454 |
---|
| 16 | Internet Explorer is really bad about making the rightmost panel |
---|
| 17 | fall beneath the others. |
---|
| 18 | Cause: |
---|
| 19 | Internet explorer calculates margins and padding differntly from |
---|
| 20 | everyone else, and this makes it entirely too easy for widths |
---|
| 21 | to add up to greater than the amount of allotted space, despite |
---|
| 22 | using percentage widths. |
---|
| 23 | Solution: |
---|
| 24 | There are two solutions to this problem: |
---|
| 25 | 1) In your theme, try to eliminate padding from the the <div> |
---|
| 26 | that directly contains your content; you can do this by |
---|
| 27 | adding an empty <div> inside it that surrounds the content |
---|
| 28 | and very specifically is set to margin: 0 and padding: 0 |
---|
| 29 | |
---|
| 30 | 2) if that doesn't work, override the widths of the panel-panel |
---|
| 31 | divs and reduce them by 1 or 2%; usually this will give IE |
---|
| 32 | enough space to quit pushing things around. |
---|
| 33 | |
---|
| 34 | Known Issue http://drupal.org/node/154351 |
---|
| 35 | TinyMCE, FCKEditor and other wysiwyg editors really blow up on Panels |
---|
| 36 | content editing. |
---|
| 37 | Cause: |
---|
| 38 | The modal dialogs that Panels uses are very particular about javascript |
---|
| 39 | and these editors are too much for them. Also, these editors get |
---|
| 40 | cranky about complicated forms with several text areas. |
---|
| 41 | Solution: |
---|
| 42 | Disable these editors on all of your panels admin pages. The important |
---|
| 43 | URLs are admin/panels/* and panels/ajax/*. More details instructions |
---|
| 44 | may follow if someone familiar with these systems submits a patch at |
---|
| 45 | the above drupal.org URL. |
---|
| 46 | |
---|
| 47 | Known Issue http://drupal.org/node/180650 |
---|
| 48 | The rounded corners style shows up as just a small graphic rather than |
---|
| 49 | a full box around the panels as it shoujld. |
---|
| 50 | Cause: |
---|
| 51 | The rounded corners CSS relies on the ID for the panel, but the ID is |
---|
| 52 | optional. |
---|
| 53 | Solution: |
---|
| 54 | Make sure your panel has an ID of some sort. With mini panels there is |
---|
| 55 | no easy workaround as mini panels currently do not have IDs of their |
---|
| 56 | own. |
---|
| 57 | |
---|
| 58 | Known Issue http://drupal.org/node/165745 |
---|
| 59 | You see a message similar to this: |
---|
| 60 | Table 'drupal.panels_info' doesn't exist query: SELECT * FROM panels_info |
---|
| 61 | WHERE path = 'front_page_new' in... |
---|
| 62 | |
---|
| 63 | The important piece of information is 'panels_info'. |
---|
| 64 | Cause: |
---|
| 65 | The Meta Tags module (also known as nodewords.module) directly reads the |
---|
| 66 | the panels tables and modifies its forms to add the tags. Unfortunately |
---|
| 67 | for this module, Panels has changed *greatly* in the leap from 1.0 to |
---|
| 68 | 2.0 and the tables aren't the same. However, the nodewords module doesn't |
---|
| 69 | yet know this. Look in the nodewords issue queue for panels patches and |
---|
| 70 | you should find something. |
---|
| 71 | |
---|
| 72 | Known Issue http://drupal.org/node/153399 |
---|
| 73 | The drag and drop content UI doesn't seem to work at all under Safari. |
---|
| 74 | |
---|
| 75 | Cause: |
---|
| 76 | Safari 2 has some serious problems with the javascript code. |
---|
| 77 | Solution: |
---|
| 78 | Upgrade to Safari 3 if possible. If not, use an an alternative browser |
---|
| 79 | such as Firefox or Opera. |
---|
| 80 | |
---|
| 81 | Known Issue http://drupal.org/node/207859 |
---|
| 82 | When using the secure pages module, the Panels administrative UI gives |
---|
| 83 | unhelpful "An error occurred" popups when trying to add or edit content. |
---|
| 84 | |
---|
| 85 | Cause: |
---|
| 86 | The secure pages module tries to move the entire administrative section |
---|
| 87 | of the site to HTTPS, but Panels' AJAX calls are using a path that |
---|
| 88 | secure pages doesn't know about. When trying to make non-secure ajax calls |
---|
| 89 | from a secure page, the browser denies the call. |
---|
| 90 | Solution: |
---|
| 91 | The solution is to simply add panels/* to your Secure Pages configuration. |
---|