when installing a script geting - E_CORE_NOTICE - ????

[loveispoison]

hi

im having this problem im trying to install a script but i get this error on top of the header does any know how to fix this or what it is?


Notice: Use of undefined constant E_CORE_NOTICE - assumed 'E_CORE_NOTICE' in /home/user/public_html/mydomain.com/libs/xx/class.Error.php on line 175

Notice: Use of undefined constant E_COMPILE_NOTICE - assumed 'E_COMPILE_NOTICE' in /home/user/public_html/mydomain.com/libs/xx/class.Error.php on line 176

[garrettroyce]

That's really bizarre. E_CORE_NOTICE and E_COMPILE_NOTICE are system constants that have been defined since PHP4. I wonder if it's a configuration error on the admin side.

[xav0989]

Maybe your script is using outdated functions, or using functions in a wrong fashion

[garrettroyce]

The weird thing is it's saying the constant is not defined, so it's using another constant. But, the constant it's using is the one it was looking for in the first place.

[misson]

im having this problem im trying to install a script but i get this error on top of the header does any know how to fix this or what it is?

Quoting errors is helpful, but it's still damn hard to fix them without knowing the source that generated it. Always give enough information to properly diagnose the issue. If it's a custom script, post a minimal test case that generates the error. If you're using a library, say which library, but you don't (necessarily) need to post source code from the library as most of it will just clutter up the post. Most importantly, RTFM for the library.

E_CORE_NOTICE and E_COMPILE_NOTICE aren't system constants. There are E_(CORE|COMPILE)_(ERROR|WARNING) constants, but apparently Zend doesn't generate notice-level messages, or at least doesn't need to handle them as it does other messages.

The warning messages indicate that the bare identifiers are being turned into the strings 'E_CORE_NOTICE' and 'E_COMPILE_NOTICE', not the values of those (non-existent) constants.

[garrettroyce]

...And again mission finds the subtle nuances. It's treating the non-existent constant as a string.

[xav0989]

...And again mission finds the subtle nuances. It's treating the non-existent constant as a string.

Misson you're on fire!

[misson]

I thought it was documented behavior, but I can't find a reference in the PHP docs. It sure as hell is documented for Perl ("Programming Perl", 3rd ed., p860). It may have been in the documentation around 2006, when Ben Ramsey references it.

Edit: The bit that Ben Ramsey quotes includes a reference to the PHP.net page on arrays that mentions quoting bare strings, but the referenced page isn't intentionally documenting this behavior; it's more of an offhand comment.

[loveispoison]

i dont realy understand what u guys are talking about and specialy what mission is saying lolz

and i have removed that live from the script i got it working but then getting another error and removed that iswell then the script didt work and its a custom made script old 1

[garrettroyce]

If your script uses the constant a lot, you'll probably get a whole slew of errors if you remove the line in which it's referenced. I would add this to the beginning of the file that you got the original error from:

define('E_CORE_NOTICE', E_CORE_WARNING);
define('E_COMPILER_NOTICE', E_COMPILER_WARNING);

Without knowing exactly what your script is doing, it's hard to pinpoint an exact solution, but I think this is a reasonable solution requiring little re-coding.

This is what is happening:

$var = ERROR_DOESNT_EXIST;
echo $var; // prints ERROR_DOESNT_EXIST (a string) and throws an error

define('ERROR_DOESNT_EXIST', 12345);
$var = ERROR_DOESNT_EXIST;
echo $var; // prints 12345 (no error)