Armory bug

[arnis5]

There is a bug on armory when you are checking Raid ID details or someone's talents you can see following msg:
[phpBB Debug] PHP Notice: in file /var/www/armory/includes/classes/class.character.php on line 2968: Undefined index: playerBytes
[phpBB Debug] PHP Notice: in file /var/www/armory/includes/classes/class.character.php on line 2969: Undefined index: playerBytes2
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Solution:
// @define('DEBUG', true);
// @define('DEBUG_EXTRA', true);
or
// Report all errors, except notices
error_reporting(E_ALL ^ E_NOTICE);

[Naxp]

or just make them pre-defined as a value counted as null :p

ur second solution may give hidden issues in the future, if vulnerables appear, staff will have less chance to even know about it ^^

[arnis5]

or just make them pre-defined as a value counted as null :p

ur second solution may give hidden issues in the future, if vulnerables appear, staff will have less chance to even know about it ^^

Yes this can work aswell:
error_reporting(0);
But might casue some problems like geting blank pages after posting something

[Naxp]

or just make them pre-defined as a value counted as null :p

ur second solution may give hidden issues in the future, if vulnerables appear, staff will have less chance to even know about it ^^

Yes this can work aswell:
error_reporting(0);
But might casue some problems like geting blank pages after posting something

hmm still only good for temponarly use.. such as previews..

this index undefined is caused by an variable who comes inside without being predefined

I'm not sure about Etros code, but those two below is the most common solutions.

Sol.1
[hide]

Code: Select all

//Predefining the variable @start of section using a NULL expression such as empty or simply Null if SQL

$playerBytes = ""

[/hide]

Sol.2
[hide]

Code: Select all

//Going from behind, thats how we like it

if (isset($_POST['buttonProceed'])) {

    

  //Section code goes here

}

[/hide]

[Etro]

I'm not sure about Etros code, but those two below is the most common solutions.

Hmm?

[Nyeriah]

I have notified Nuko about it, but it's probably best to post these errors at the armory thread since he's subscribed to it, so he'll get an email notification about it when you post it there.

http://www.truewow.org/forum/viewtopic. ... 23#p187323

[Naxp]

I'm not sure about Etros code, but those two below is the most common solutions.

Hmm?

Sorry, meant Nok

[Nuko]

A very belated LOL at Etros piccy

I like how it so naturally draws ones attention to the subject at hand.

Anyway, should be fixed, the error was originating from trying to extract the playerBytes and playerBytes2 fields from an SQL query result but the fields no longer exist due to a recent update. I've updated the field names so all should be fine.

The undefined index error comes from attempting to read a value from an associative array (ie the query result) by something like

Code: Select all

$this->playerBytes = $queryRow['playerBytes'];

but since the playerBytes field no-longer exists, the $queryRow array no longer has an element with index "playerBytes" assigned to it when the query result is returned. Hence PHP gets rather offended and feels the need to complain via a strongly worded warning output.

[Naxp]

A very belated LOL at Etros piccy

I like how it so naturally draws ones attention to the subject at hand.

Anyway, should be fixed, the error was originating from trying to extract the playerBytes and playerBytes2 fields from an SQL query result but the fields no longer exist due to a recent update. I've updated the field names so all should be fine.

The undefined index error comes from attempting to read a value from an associative array (ie the query result) by something like

Code: Select all

$this->playerBytes = $queryRow['playerBytes'];

but since the playerBytes field no-longer exists, the $queryRow array no longer has an element with index "playerBytes" assigned to it when the query result is returned. Hence PHP gets rather offended and feels the need to complain via a strongly worded warning output.

Ahh, clean & simple ^^