You must login to post a comment. Don't have an account? Register to get one!

• 

  • Reply
  • #19

  Balreign Jan 20, 2011 at 14:27 UTC - 0 likes

  So... I've fix the issue, but with a durty way...

  On the OnEnable() function I add a SpellBookFrame:Show() and next a SpellBookFrame:Hide()

• 

  • Reply
  • #18

  Balreign Dec 18, 2010 at 16:59 UTC - 0 likes

  Here is the way everybody can reproduce the error.

  I tryed with only Collectinator, bugsack and !BugGrabber:

  Log into the game, open your bags or mail if you have a pet to learn in your mails. Learn it before opening the Speellbook & Abilities panel.

  You'll raise the error.

• 

  • Reply
  • #17

  fixitman Dec 02, 2010 at 05:01 UTC - 0 likes

  I realize they were added in alpha, I just prefer to stick to release versions whenever possible :)

• 

  • Reply
  • #16

  pompachomp Dec 02, 2010 at 02:07 UTC - 0 likes

  ... those new pets were added in an alpha

• 

  • Reply
  • #15

  fixitman Dec 01, 2010 at 21:43 UTC - 0 likes

  I just made the change described by Asteague, and it took care of the error when adding Lil' Ragnaros to my collection. I don't know if it affected the addon's automatic SavedVariables update or not because this companion isn't in the latest release version. I did get an error message (in chat) when adding it. It stated "Pet with ID 95787 not in database", leading me to believe it tried, but didn't know what it was. I'll wait until a new release version is available before adding this companion to all my alts.

• 

  • Reply
  • #14

  Asteague Nov 25, 2010 at 11:42 UTC - 0 likes

  I took a look at the responsible code and came up with the following question: Why are you even trying to pass companion_frame.currentTab.bookType as third parameter? Looking at the Scan function I don't even see it used when triggerd by an event, which would set the second parameter autoupdatescan to true, resulting in the following evaluating to false.

  	if not autoupdatescan and scantype then
  

  Thus scantype isn't even used. Can't we just change the call in l. 492

  self:Scan(false, true)
  

  ?

• 

  • Reply
  • #11

  fixitman Nov 06, 2010 at 01:05 UTC - 0 likes

  I always get three pets whenever I create a new character: core hound pup, unhatched mr. chilly, and a warbot .I just rolled 10 rogues specifically to find out what addon was causing this conflict (I have 3 accounts for multi-boxing). I just used these characters to gradually whittle down to the conflicting addon(s) causing this error. After 15 pets, I found that the error occurs with no other addons enabled. I then confirmed this occurs on a new character that has never before had a pet, or utilized Collectinator. I even went so far as to remove Collectinator with all SavedVariables, and then start a new character with a fresh install of the addon. With only Collectinator enabled, I still see the same error.

  I was really hoping to help out, by finding a source for the conflict. Unfortunately, all I did was confirm this is indeed an issue with collectinator alone. The error is the same as above, but the "stack" portion is slightly different (points to the libs in a Collectinator sub-folder instead of an ARL sub-folder). All this testing is based on the last release version. I have not tested with any alpha versions. Should I provide the Lua error, or is this enough information?

  Last edited Nov 09, 2010 by fixitman
• 

  • Reply
  • #10

  pompachomp Nov 04, 2010 at 22:43 UTC - 0 likes

  Everyone, please don't comment anymore on this ticket saying that you got a certain companion/mount and you received this error. Thanks.

• 

  • Reply
  • #9

  Oukami Nov 04, 2010 at 22:37 UTC - 0 likes

  Just bought and learned a Silver Covenant Hippogryph and got this error.

• 

  • Reply
  • #8

  pompachomp Nov 04, 2010 at 13:39 UTC - 0 likes

  it must be a conflicting addon.....i just learned pet and mounts with no error.