summaryrefslogtreecommitdiffstats
path: root/system/core/Exceptions.php
AgeCommit message (Collapse)AuthorFilesLines
2014-10-28Add a real exception handlerAndrey Andreev1-0/+38
Close #1590 Close #3200
2014-10-27[ci skip] Switch to MIT license; close #3293Andrey Andreev1-14/+25
2014-10-05config_item() to return NULL instead of FALSE for non-existing itemsAndrey Andreev1-6/+10
Close #3001 Close #3232 Related: #3244
2014-04-25Minor fixesvlakoff1-1/+1
2014-04-14Different method for handling "error_views_path" config itemvlakoff1-15/+10
2014-04-14Rename config item "error_templates_path" to "error_views_path"vlakoff1-2/+2
2014-04-12Make the error templates path configurablevlakoff1-2/+15
2014-03-13Partially revert PR #2190Andrey Andreev1-1/+1
The core shouldn't depend on constants that are not defined by itself
2014-02-112013 > 2014darwinel1-1/+1
Update copyright notices from 2013 to 2014. And update one calendar example in user_guide from year 2013/2014 to 2014/2015.
2013-11-12Add CLI error templates and only send HTTP status headers for non-CLI ↵Andrey Andreev1-14/+39
requests (issue #1743)
2013-09-13Drop the unused parameter from log_message() / CI_Log::write_log()Andrey Andreev1-1/+1
2013-03-04Updated in accordance with feedback from @narfbgDaniel Hunsaker1-1/+1
- Removed commented lists of constants from the three reference conventions, replacing each with the URLs at which more information can be found. - Renamed a few constants to more closely reflect CodeIgniter conventions. - Modified a couple of lines which were in violation of the CI Style Guide. Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
2013-02-23Updated exit codes as constant valuesDaniel Hunsaker1-1/+1
Re-allocated exit status codes according to three references, which follow: BSD sysexits.h:http://www.gsp.com/cgi-bin/man.cgi?section=3&topic=sysexits GNU recomendations:http://www.gnu.org/software/libc/manual/html_node/Exit-Status.html Bash scripting:http://tldp.org/LDP/abs/html/exitcodes.html The GNU recommendations stem from and expand upon the standard C/C++ library (stdlibc) definitions, while also suggesting some best-practice conventions which happen to prevent exit status code collisions with bash, and probably other shells. The re-allocated codes are now mapped to constant values, set in *application/config/constants.php*, and used throughout the CodeIgniter core. They would additionally be used in *index.php*, but the constants file hasn't been loaded at that point, so the integer values are used instead, and a comment follows each such use with amplifying information on why that particular value was selected. Finally, the errors documentation has been updated accordingly. Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
2013-01-25Updated all cases of exit() to return a valid codeDaniel Hunsaker1-1/+1
Specific codes are as follows, but can easily be changed if a different order/breakdown makes more sense: - 0: Success; everything executed as planned - 1: Configuration Error; something is wrong with/in the configuration file(s) - 2: Class Not Found; what it says - 3: Driver Method Unsupported; the method you're trying to use on a Driver doesn't exist - 4: File Not Found; 404 error - 5: Database Error; something is broken in the database somewhere - 6: Invalid Input; the user attempted to submit a request with invlaid characters in 1+ key names 7 through 26 are reserved for future use - 27: Generic Error; generated by show_error() when the status code is >= 100 28 through 127 are errors generated by user applications, normally by using show_error() with a status code below 100 128 through 254 should not be used by applications, as they are reserved by system-level functions - 255: PHP Fatal Error; automatically generated by PHP for fatal errors, and therefore not allowed for our use Status codes below 100 are shifted up by 28 to place them in the user error range. It may make more sense to have these codes left alone and instead shift the CI errors into the 101 through 127 space, but that's not what I opted for here. It would probably also be a good idea to replace the hard-coded numbers with constants or some such, but I was in a bit of a hurry when I made these changes, so I didn't look around for the best place to do this. With proper guidance, I could easily amend this commit with another that uses such constant values. Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
2013-01-01[ci skip] Happy new yearAndrey Andreev1-1/+1
2012-11-01Manually apply PR #1594 (fixing phpdoc page-level generation/warnings)Andrey Andreev1-1/+2
Also partially fixes issue #1295, fixes inconsistencies in some page-level docblocks and adds include checks in language files.
2012-10-27Docblock improvements to the Config library and remove ↵Andrey Andreev1-1/+1
CI_Config::_assign_to_config() Existance of _assign_to_config() is pointless as this method consists just of a foreach calling CI_Config::set_item() and is only called by CodeIgniter.php - moved that foreach() in there instead.
2012-10-27Docblock improvementsAndrey Andreev1-23/+25
2012-06-24Use the VIEWPATH constant, instead of assuming the user hasn't moved themNicholas Avenell1-2/+2
2012-06-12Change file permissions for system/core/*.php and system/database/DB.php so ↵Andrey Andreev1-0/+0
that they don't differ from the rest
2012-05-17merge upstreamTimothy Warren1-4/+6
2012-05-17Cleanup the core classesAndrey Andreev1-5/+7
2012-05-14Move errors to views folderTimothy Warren1-2/+2
2012-04-23Use tabs to separate class propertiesTimothy Warren1-2/+2
2012-04-19Additional formatting fixesTimothy Warren1-13/+13
2012-04-19Normalize comments in core filesTimothy Warren1-6/+3
2012-03-26Add visibility declarations where they remain missingAndrey Andreev1-4/+2
2012-03-09Bumped CodeIgniter's PHP requirement to 5.2.4.Phil Sturgeon1-1/+1
Yes I know PHP 5.4 just came out, and yes I know PHP 5.3 has lovely features, but there are plenty of corporate systems running on CodeIgniter and PHP 5.3 still is not widely supported enough. CodeIgniter is great for distributed applications, and this is the highest we can reasonably go without breaking support. PHP 5.3 will most likely happen in another year or so. Fingers crossed on that one anyway...
2012-01-07Revert DIRECTORY_SEPARATOR changesAndrey Andreev1-2/+2
2012-01-07Improve core Controller & Exceptions librariesAndrey Andreev1-48/+35
2012-01-02Updating copyright date to 2012Greg Aker1-1/+1
2011-10-20adding new license file (OSL 3.0) and updating readme to ReSTDerek Jones1-4/+16
added notice of license to all source files. OSL to all except the few files we ship inside of the application folder, those are AFL. Updated license in user guide. incrementing next dev version to 3.0 due to licensing change
2011-08-14Added some docs to CI core filesDavid Behler1-2/+3
2011-08-14Added some docs to CI core filesDavid Behler1-0/+14
2011-07-02backed out 648b42a75739, which was a NON-trivial whitespace commit. It ↵Derek Jones1-3/+3
broke the Typography class's string replacements, for instance
2011-04-25Fixed double-space typo.Razican1-3/+3
2011-04-19Removing internal references to the EXT constant. Additionally, marked the ↵Greg Aker1-2/+2
constant as deprecated. Use ".php" instead. Also adding upgrade notes from 2.0.2 to 2.0.3.
2011-01-05Hey look, it's 2011Greg Aker1-1/+1
2010-11-10Changing all class constructors to __construct()Greg Aker1-2/+1
2010-11-10Updating PHP requirements in files 5.1.6Greg Aker1-1/+1
2010-10-04Cleanup of stray spaces and tabsBarry Mieny1-13/+13
2010-08-05Added an optional second parameter to <kbd>show_404()</kbd> to disable logging.Derek Allard1-2/+7
2010-03-02fixed EOF code comment file locationsDerek Jones1-1/+1
2010-03-02moving core library files out of libraries into new core folderDerek Jones1-0/+174