Known Issues (Current)

History Key

  • New content
  • Removed content

Recent Versions

Choose two versions to compare, or click the link to view it.

  1. 59. over 1 year by sirebral
  2. 58. almost 2 years by sirebral
  3. 57. almost 2 years by sirebral
  4. 56. almost 2 years by sirebral
  5. 55. almost 2 years by sirebral
  6. 54. about 2 years by sirebral
  7. 53. about 2 years by sirebral
  8. 52. about 2 years by sirebral
  9. 51. about 2 years by sirebral
  10. 50. about 2 years by sirebral
  11. 49. about 2 years by sirebral
  12. 48. about 2 years by sirebral
  13. 47. about 2 years by sirebral
  14. 46. about 2 years by sirebral
  15. 45. about 2 years by sirebral
  16. 44. about 2 years by sirebral
  17. 43. about 2 years by sirebral
  18. 42. about 2 years by sirebral
  19. 41. about 2 years by sirebral
  20. 40. over 2 years by sirebral
  21. 39. over 2 years by sirebral
  22. 38. over 2 years by sirebral
  23. 37. over 2 years by sirebral
  24. 36. over 2 years by sirebral
  25. 35. over 2 years by sirebral
  26. 34. over 2 years by sirebral
  27. 33. over 2 years by sirebral
  28. 32. over 2 years by sirebral
  29. 31. over 2 years by sirebral
  30. 30. over 2 years by sirebral
  31. 29. over 2 years by sirebral
  32. 28. over 2 years by sirebral
  33. 27. over 2 years by sirebral
  34. 26. over 2 years by sirebral
  35. 25. over 2 years by sirebral
  36. 24. over 2 years by sirebral
  37. 23. over 2 years by sirebral
  38. 22. over 2 years by sirebral
  39. 21. over 2 years by sirebral
  40. 20. over 2 years by sirebral
  41. 19. over 2 years by sirebral
  42. 18. over 2 years by sirebral
  43. 17. over 2 years by sirebral
  44. 16. over 2 years by sirebral
  45. 15. over 2 years by sirebral
  46. 14. over 2 years by sirebral
  47. 13. over 2 years by sirebral
  48. 12. almost 3 years by sirebral
  49. 11. almost 3 years by sirebral
  50. 10. almost 3 years by sirebral
  51. 9. almost 3 years by sirebral
  52. 8. almost 3 years by sirebral
  53. 7. almost 3 years by sirebral
  54. 6. almost 3 years by sirebral
  55. 5. almost 3 years by sirebral
  56. 4. almost 3 years by sirebral
  57. 3. almost 3 years by sirebral
  58. 2. almost 3 years by sirebral
  59. 1. almost 3 years by sirebral
 

 

Traipse has some known issues with the code, but thankfully there are simple work arounds for most of them.  If you experience any of the problems, please use the associated work around.

 

Grumpy Goblin

Grumpy Goblin is considered closed.

After the updated code re-working Grumpy Goblin does not start properly. The problem is caused because of the TerminalWriter update from core. This bug is fixed in Ornery Orc and a patch will be released as soon as possible.

I've decided to not update Grumpy Goblin. Please use Ornery Orc instead.

 

Ornery Orc

Ornery Orc is considered closed, though patches may be released.

  • Patch-1 has been released
  • Patch-2 is in Stable 
  • Patch-3 is in Stable

 

Multiple Meta Servers (Ornery 100505-00) - Fixed in Beta

This is a really minor problem. I did not do enough error prevention. When you update to the newest Ornery Orc, your settings will update and metaservers.cache will be replaced with metaservers.xml. Howevever, metaservers.xml is not beinf created correctly.

The work around is easy. Inside the /templates/ folder is a file called default_metaservers.xml. Copy it to your /myfiles/ directory and rename it to metaservers.xml

 

The Server {100505-00} - Fixed in Beta

Unfortunately the server attempts to register rooms to a meta server that does not provide that feature. Also, the server is attempting to register to a meta server twice, creating a duplicate instance of the meta server which returns a server id of 0. This problem creates and eternal loop in the Register Rooms thread.

There is no work around for this issue.

 

Chat Names and Room Creation {100505-00}

This is probably due to the new way I am creating a display name. When a user creates a room their names is duplicated. Sorry. It's really minor and can wait.

 

Update Manager (Vista)

The Update Manager may hang during the Refresh of a Repository when using the .EXE install. Workaround: A) rerun setup.py and copy your myfiles directory to the newly created System folder. B) Download the .ZIP package and run setup.py there. This is caused by a Permissions problem in Vista: Ticket

 

Themes

When starting the slanted theme does not carry the color over from the settings. You are encouraged to use the flat themes for the time, and setup your own custom theme colors. Work in Ornery Orc will remove this problem and allow users to create their own themes and use other peoples themes.

 

CherryPy

I am certain there is going to be some body who does not set their port correctly and then CherryPy will be on auto start set to on.  This will most likely cause a crash.  Work Around: This work around is a lot more difficult then I would like it to be so there is a planned fix for this.  In your System/myfiles/ folder open the plugindb XML and remove the CherryPy auto start entry. It will look like this:

<auto_start type="string">on</auto_start>

Planned Fix: The planned fix will create a check box in the CherryPy plugin menu that users can set the auto start feature with.