Does anyone know where the code template for try-catch blocks is stored in Netbeans settings? The specific template I'm referring to is inserted when I type try { and then hit Enter. After I do that, the following code block appears:
try {
} catch (Exception $ex) {
}
I would like to insert a newline between the try block and the catch statement but I don't know how to change this. I tried going to Tools->Options->Editor->Code Templates but I couldn't find whatever causes the above block to expand.
With Tools->Options->Editor->Code Templates you are on the right way look up in the first column of the table the Abbreviation: trycatch then youll see bellow the editable template and do it as I show you, dont forget to apply chages:
try {
"new line" // this line here I have put it
${selection}${cursor}
} ${CATCH_STMTS uncaughtExceptionCatchStatements default="catch (Exception e) {}" editable=false}
I have test it on NetBeans IDE 8.1 RC2 (Build 201510122201) and after writing trycatch and press tab it generates:
try {
"new line"
} catch (Exception e) {
}
I hope it helps!!!!
Related
Now that we can catch fatal errors in PHP7 (set_error_handler cannot), would it be a good idea to use it to catch errors on a whole project? Mine is always going through index.php, so I was planning to do this:
try {
//All the code and includes, etc.
} catch(Error $ignored) {
//save the error in log and/or send a notification to admin.
}
I tried first to be sure:
set_error_handler(function(int $number, string $message) {
echo "Error $number: '$message'" . PHP_EOL ;
});
$var = $undeclared_var //The error is sent to the error_handler.
function_dont_exist(); //The error isn't sent to the error_handler.
try {
function_dont_exist();
}
catch(Error $E){
echo "Error"; //That works.
}
Is it a good idea / good practice to envelope the whole code with a try/catch/error to deal with them? It sounds good, but I wonder why I don't see it much. I tried and I believe it works, but it sounds too easy.
Thank you for your help!
I'm using CodeIgniter and am trying to execute code in a try/catch block with the idea that errors will stop execution of the code after the error until the catch block is reached, as you would normally think it would work.
However on encountering PHP Errors, the code is continuing. This is causing a database transaction complete command to execute which is .... very bad if there's an error and all of the instructions weren't carried out properly. For example, I have this code which is executed in an ajax request:
// start transaction
$this->db->trans_start();
try {
$this->M_debug->fblog("firstName=" . $triggerOpts->{'firstXXXName'});
$data = array("test_col" => 123);
$this->db->where("id", 4);
$this->db->update("my_table", $data);
// if got this far, process is ok
$status = "process_ok";
// complete transaction
$this->db->trans_complete();
} catch (Exception $ex) {
// output the error
$this->M_debug->logError($ex);
}
In this code, I'm trying to execute a database update as part of a transaction.
My call to $this->M_debug->fblog() is designed to just log a variable to PHP Console, and I've deliberately tried to log a variable that does not exist.
This causes a PHP error, which I guess is a fatal error, and the desired result is that the code after the log commands fails, and the transaction does not complete. However after this error, despite reporting the PHP error in Chrome console, the code keeps right on executing, the database is updated and the transaction is completed. Would appreciate any help in how i could stop this from happening.
Thanks very much, G
EDIT --
As requested heres fblog(), it's simply a Chrome console log request of a variable
public function fblog( $var ) {
ChromePhp::log( $var );
}
Assuming you're using PHP 7.0 or higher, you can catch PHP errors as well as exceptions, however you need to catch Error or the parent Throwable type rather than Exception.
try {
...
} catch (Throwable $ex) {
//this will catch anything, including Errors and Exceptions
}
or catch them separately if you want to do something different for each of them...
try {
...
} catch (Exception $ex) {
//this will catch Exceptions but not errors.
} catch (Error $ex) {
//this will Errors only
}
Note that if you're still only PHP 5.x, the above won't work; you can't catch PHP errors in older PHP versions.
I'm working with the PHP Slim Framework in the version 2.6.1 (due to some limitation to upgrade PHP no a newer version) and when trying to use flash messages inside of a try/catch block the messages are not stored in the session when the template is rendered.
For example, the code below works fine (when the validator get some error the page is redirected with the desired flash messages):
$objValidation = FormValidator::isValidData($post);
if($objValidation->bolHasError)
{
$app->flash('objValidation', serialize($objValidation));
$app->flash('selectedData', $post);
return $app->redirect('/app/edit/form/components/');
}
But if I start using a try block, like below, then the flash message is not stored in the $_SESSION (or even in the {{ flash }} in templates):
try {
$objValidation = FormValidator::isValidData($post);
if($objValidation->bolHasError)
{
$app->flash('objValidation', serialize($objValidation));
$app->flash('selectedData', $post);
return $app->redirect('/app/edit/form/components/');
}
# some other stuff processed here...
}
catch(Exception $e) {
# do something
}
P.S.: the sessions are stored in the PHP native way ( session_start() ).
There are any limitations of scope for using the flash messages in that way?
I've figured out that the try block create a "isolated scope". So, I tried to to put a return false before the redirect to test if the in next page the flash message would show up. And finally the flash message was stored in the $_SESSION variable (of course the redirection was not executed, but at least I've discovered that the issue is related with the try scope).
Then, the solution I found was to raise an exception and do the redirect inside the catch block. Like this:
$objValidation = FormValidator::isValidData($post);
if($objValidation->bolHasError)
{
throw new Exception('validation_error');
}
and then capture the error into the catch block:
catch(Exception $e)
{
if($e->getMessage() == 'validation_error')
{
$app->flash('objValidation', serialize($objValidation));
$app->flash('formData', $post);
return $app->redirect('/api/form/change/components/');
}
}
In that way I was able to get the flash message into template.
SOLUTION: I've been working on the iOS side of it at the same time and must have got the languages switched up. Instead of the $, I put *.
I am trying to get a try{} catch{} working in PHP. My code works when I remove the try{} catch{}. Once I put it back in, it breaks my script. I even tried making it empty in both the try{} catch{}, but it still crashes my script.
try {
}
catch (Exception *e) {
}
Is there a reason the try{} catch{} would cause the script to crash? When I run it in my browser it just shows a white screen.
I even went and made another empty PHP file and put this code in without the if statement. And still, it doesn't work. The page is still white. I had it echo in the try.
Your catch declaration is incorrect.
catch (Exception *e) {
Should be.
catch (Exception $e) {
The inaccurate code would cause a parse error, thus preventing the script from running at all, and producing a white screen.
Maybe possibilities catch is not getting the object values. You should use it as:
try
{
some statement....
}
catch(Exception e)
{
some statement...
}
My code is
try{
$this->_db->beginTransaction();
$stmt = $this->_db->prepare("...");
$stmt->execute(array($var1, $var2));
...
} catch (Exception $e) {
$stmt->rollBack();
}
I want to log this action to my log file with a function
as you see this one meant to save errors in transaction. Another one should also save the succeeded attempts. BUT if I put them inside of try{} and catch{} they not working for some reason. outside it does work good but I'm not sure what exactly should I check here for true/false to see the result outside of try/catch.
Thanks for your answers. I'm just learning so my questions might be stupid. Sorry for this. =)
Update.
What I've tried to do is:
try{...
} catch (Exception $e) {
$stmt->rollBack();
file_put_contents(LOG_CONST, date("r")." UderID: ".$id." Error: ".$e->getMessage()."\n", FILE_APPEND);
}
And it didn't put anything.
Update 2
Not sure if I have to add a new details here or I should answer to myself... Anyway. Right now I'm trying this code
try{
$this->_db->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
$this->_db->beginTransaction();
$stmt = $this->_db->prepare
..................
$stmt->execute(array($var));
file_put_contents(DATACHANGE_LOG, date("r")." ".n307." UderID: ".$id."\n", FILE_APPEND);
$this->_db->commit();
} catch (Exception $e) {
file_put_contents(DATACHANGE_LOG, date("r")." Hello! \n", FILE_APPEND);
$stmt->rollBack();
}
I have a same result with valid and not valid data at my log file. It's the first row from try{} which means that rollback is not affective at file_put_contents. However if the data at queries not valid rollback working agains them and there is no changes at DB. But the row before rollback never works.
Errors are enabled but it doesn't show anything... I just can't give up I have to understand it...
Update 3
What is invalid data?
I've tried MySQL errors/table,row errors.
Why do I need this at all?
I'm learning and doing a lot of things that I don't need actually just to understand how it works. As I see now it throwing errors in MySQL itself so really not useful logger in this particular case. Anyway I've got my errors and here is it.
Working code:
try{
$this->_db->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
$this->_db->beginTransaction();
$stmt = $this->_db->prepare
QUERIES
$stmt->execute(array($var));
file_put_contents(DATACHANGE_LOG, date("r")." ".n307." UserID: ".$id."\n", FILE_APPEND);
$this->_db->commit();
}catch(PDOException $e){
file_put_contents(DATACHANGE_LOG, date("r")."Error". $e->getMessage()." UserID: ".$id."\n", FILE_APPEND);
if($this->_db->rollback())
header("Location: http://link");
}
header("Location: http://anotherlink");
There is nothing essentially different inside try..catch blocks. And your file writing code should be working the same way as outside, no difference.
The only issue I can think of is irrelevant to try..catch but to exceptions in general: a thrown exception terminates further code execution. Say, if there is an error in $stmt->rollBack(); - no code below will be executed. So, it's better to move a logger at the top of the block.