Titan Network

More Titan Projects => City Info Tracker => Bugs and Support => Topic started by: BitLoadR on January 20, 2012, 08:05:47 AM

Title: PHP Error in Auto-Badge Information page
Post by: BitLoadR on January 20, 2012, 08:05:47 AM
When viewing an account on the Auto-Badge Information page (Menu > My Account > My Account Badges) the account that has not been selected shows too but produces an error message:

Code: [Select]
A PHP Error was encountered
Severity: Notice
Message: Undefined index: unobtained
Filename: manage/global_badge_view.php
Line Number: 26

If I select the first account, the second account will show this message in the "Badges Not Obtained" section. While the first account shows the correct information.
If I select the second account, the first account will show this message while the second account shows the correct information.
Title: Re: PHP Error in Auto-Badge Information page
Post by: Keen on February 01, 2012, 01:15:00 PM
The PHP notices have now been fixed internally and should be applied to the Live site in the next publish. Thanks for reporting!

As for both accounts showing up, I'm investigating that. I've noticed in my local tests that my global name is being doubled with and without the "@". Can you confirm if that's your case as well?
Title: Re: PHP Error in Auto-Badge Information page
Post by: BitLoadR on February 02, 2012, 11:33:22 AM
The PHP notices have now been fixed internally and should be applied to the Live site in the next publish. Thanks for reporting!

As for both accounts showing up, I'm investigating that. I've noticed in my local tests that my global name is being doubled with and without the "@". Can you confirm if that's your case as well?

No, not the case with me.
I have 2 globals: @Star Jewel and @Star Jewel2.
Both of them are shown no matter which one I choose.
No duplicates with or without an @.

And when will this next publish be?
Title: Re: PHP Error in Auto-Badge Information page
Post by: eabrace on March 29, 2012, 12:09:58 AM
Some changes were published on March 23.  Any change in behavior for you since then, bitloader?