PDA

View Full Version : Fatal Error with Myadopts page


Abronsyth
12-29-2014, 01:33 PM
Fatal error: Uncaught exception 'AdoptNotfoundException' with message 'Adoptable 000 does not exist...' in /hermes/bosoraweb162/b1009/ipg.ferrepetscom/classes/class_adoptable.php:26 Stack trace: #0 /hermes/bosoraweb162/b1009/ipg.ferrepetscom/classes/class_ownedadoptable.php(28): Adoptable->__construct('000') #1 /hermes/bosoraweb162/b1009/ipg.ferrepetscom/view/myadoptsview.php(26): OwnedAdoptable->__construct('1') #2 /hermes/bosoraweb162/b1009/ipg.ferrepetscom/classes/class_frontcontroller.php(100): MyadoptsView->index() #3 /hermes/bosoraweb162/b1009/ipg.ferrepetscom/index.php(74): FrontController->render() #4 /hermes/bosoraweb162/b1009/ipg.ferrepetscom/index.php(78): IndexController::main() #5 {main} thrown in /hermes/bosoraweb162/b1009/ipg.ferrepetscom/classes/class_adoptable.php on line 26

That is the error, I have no idea what to do with it. There is one adoptable species, which I named "000". I adopted it just fine, but when going to my Myadopts page I ended up with this error. I get the same error when trying to view my profile. Any ideas..?

Abronsyth
12-29-2014, 01:50 PM
Okay, for some reason Mysidia just didn't like me using an all-numeric name for an adoptable type. Went through and changed it to "Ferret 0" and now all is well.

IntoRain
12-29-2014, 03:54 PM
If the name is a number, the constructor for the adoptable will try to retrieve the adoptable by their id instead of their name xD I'd say it's something that would be useful to correct in future versions of mysidia, or just prohibit number-only names for adoptables