Drupal instances may not always work the way they should. Here is a list of issues that we know about and their status.
Drupal 5
- Categories and Menus - When working with categories or containers, menus may appear do move around, disappear, or appear before publishing.
- This is due to the way that the category module operates with Drupals menuing system. It will be fixed in the next release of the category module for Drupal 6.
- Work Around - Once a menu item changes place you must go into the osu_menu options and reorder the menu item. If a hidden menu item appears, go into the osu_menu options and "disable" the menu item.
- Paste from Microsoft Word - When pasting text in from Microsoft Word some formatting is lost on preview of the node.
- Source formatting will be stripped out of a post when pasted using the "Paste from Word" button or after a "Preview" of the page is done. Word uses antiquated <font> tags and inline styles which are stripped out by the editor and Drupal. This is done to keep text display on the site uniform.
- Rejected Node Disappears - When a new node that has been submitted is rejected by a gatekeeper it seems as if the node disappears.
- To locate the node you must navigate to the "View Pages" menu item and locate the page in that listing of nodes.
- Users Can't Disable Emails - Currently only Administrators have the ability to disable or enable email notifications sent to users when nodes are in the queue, accepted, or rejected.
- In the next phase we will address this problem by adding customizable settings accessed in the user's preferences page.
- Blocks - Links Do Not Internalize Automatically - When adding internal links to blocks they are not automatically converted to the 'internal:node/5' format on save.
- Due to the way Drupal allows us to hook into it, we can not modify the links as they are saved from blocks. Users are required to use the 'internal:' format manually for all links in blocks. When opening the block for editing a second time, the links will be replaced with their full paths again and must be corrected before saving.
- Failure to "internal"ize links in blocks will cause them to break when a site is moved.
- Work Around - Use Nodes if possible when creating panel layouts.
- Deleting a Page with Drafts creates new (DELETED) pages - When deleting a node with drafts, Drupal will take these drafts and turn them into unpublished nodes. There is currently an issue with deleting these new pages, and a process must be followed:
- Edit the (DELETED) node.
- Submit the (DELETED) node and approve the page in the Approval Queue.
- Edit the (DELETED) node again.
- Click on "list" under drafts, check the box next to the drafts, then click "Delete" to remove the draft.
- Now the (DELETED) page can be deleted as usual by clicking the Delete button in the edit page.
- Deleting a Draft Before a Node is Published Causes Errors - When working with drafts of a node that has not been published yet and one of the first drafts of the node is deleted a user's ability to open other drafts is broken.
- Work Around - To prevent Drupal from entering this state for a node you must make sure that at least one of the Drafts has been published before deleting any of the other Drafts.