info/php-the-right-way
1
0
Fork 0
mirror of https://github.com/codeguy/php-the-right-way.git synced 2025-08-16 02:34:00 +02:00
Code Issues Projects Releases Wiki Activity

Update links in Errors section to use https

Browse Source
This commit is contained in:
Josh Lockhart
2018-06-19 14:36:52 -04:00
parent b65103c026
commit f8278e5357
2 changed files with 16 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
_posts/09-02-01-Errors.md
View File

@@ -1,5 +1,5 @@
---
isChild: true
---
isChild: true
anchor: errors
---
@@ -104,7 +104,7 @@ with the following.
xdebug.scream = On
{% endhighlight %}
You can also set this value at runtime with the `ini_set` function
You can also set this value at runtime with the `ini_set` function
{% highlight php %}
<?php
@@ -131,8 +131,8 @@ PHP is perfectly capable of being an "exception-heavy" programming language, and
make the switch. Basically you can throw your "errors" as "exceptions" using the `ErrorException` class, which extends
the `Exception` class.
This is a common practice implemented by a large number of modern frameworks such as Symfony and Laravel. In debug
mode *(or dev mode)* both of these frameworks will display a nice and clean *stack trace*.
This is a common practice implemented by a large number of modern frameworks such as Symfony and Laravel. In debug
mode *(or dev mode)* both of these frameworks will display a nice and clean *stack trace*.
There are also some packages available for better error and exception handling and reporting. Like [Whoops!], which comes with the default installation of Laravel and can be used in any framework as well.
@@ -150,11 +150,11 @@ More information on this and details on how to use `ErrorException` with error h
[errorreport]: /#error_reporting
[Xdebug]: http://xdebug.org/docs/basic
[Scream]: http://php.net/book.scream
[Error Control Operators]: http://php.net/language.operators.errorcontrol
[SitePoint]: http://www.sitepoint.com/
[Whoops!]: http://filp.github.io/whoops/
[errorexception]: http://php.net/class.errorexception
[Predefined Constants for Error Handling]: http://php.net/errorfunc.constants
[error_reporting]: http://php.net/function.error-reporting
[Xdebug]: https://xdebug.org/docs/basic
[Scream]: https://secure.php.net/book.scream
[Error Control Operators]: https://secure.php.net/language.operators.errorcontrol
[SitePoint]: https://www.sitepoint.com/
[Whoops!]: https://filp.github.io/whoops/
[errorexception]: https://secure.php.net/class.errorexception
[Predefined Constants for Error Handling]: https://secure.php.net/errorfunc.constants
[error_reporting]: https://secure.php.net/function.error-reporting

6
_posts/09-03-01-Exceptions.md
View File

@@ -71,7 +71,7 @@ standard Exception which is vague, or creating a custom Exception just for that,
[splext]: /#standard_php_library
[exceptions]: http://php.net/language.exceptions
[splexe]: http://php.net/spl.exceptions
[nesting-exceptions-in-php]: http://www.brandonsavage.net/exceptional-php-nesting-exceptions-in-php/
[exceptions]: https://secure.php.net/language.exceptions
[splexe]: https://secure.php.net/spl.exceptions
[nesting-exceptions-in-php]: https://www.brandonsavage.net/exceptional-php-nesting-exceptions-in-php/
[exception-best-practices53]: http://ralphschindler.com/2010/09/15/exception-best-practices-in-php-5-3