summaryrefslogtreecommitdiffstats
path: root/system/libraries/Trackback.php
AgeCommit message (Collapse)AuthorFilesLines
2018-05-18http:// to https://Mehdi Bounya1-2/+2
2018-01-09Annual copyright updateMaster Yoda1-2/+2
2016-12-31Update copyright data to 2017Master Yoda1-2/+2
2016-08-10Better usageVivek Dinesh1-1/+1
Based on GitHub discussion. Signed-off-by: Vivek Dinesh <vivekdinesh5@gmail.com>
2016-08-09URI schemes are not case sensitiveVivek Dinesh1-1/+1
Signed-off-by: Vivek Dinesh <vivekdinesh5@gmail.com>
2016-01-11[ci skip] Update ellislab.com links to https tooAndrey Andreev1-1/+1
2016-01-11[ci skip] Update codeigniter.com links to httpsAndrey Andreev1-2/+2
2016-01-11[ci skip] Bump year to 2016Andrey Andreev1-2/+2
2015-01-21Remove closing blocks at end of PHP filesvlakoff1-3/+0
2015-01-20[ci skip] Change some log messages' levelAndrey Andreev1-1/+1
'Class Loaded' type of messages flood log files when log_threshold is set to 2 (debug). They're now logged as 'info' level. This is manually applying PR #1528, which was created to do the same thing, but became outdated.
2015-01-09Bulk (mostly documentation) updateAndrey Andreev1-3/+3
- Remove PHP version from license notices - Bump year number in copyright notices - Recommend PHP 5.4 or newer to be used - Tell Travis-CI to test on PHP 5.3.0 instead of the latest 5.3 version Related: #3450
2014-10-27[ci skip] Switch to MIT license; close #3293Andrey Andreev1-14/+25
2014-04-09Minor changes in FV, TrackbackAndrey Andreev1-19/+24
2014-02-11Utf8/iconv/mbstring-related changesAndrey Andreev1-1/+8
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-03-04Reverting changes to functions that have no business being used in CLI apps ↵Daniel Hunsaker1-4/+2
to begin with Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
2013-03-04Oops, missed a few places where EXIT_SUCCESS was being used.Daniel Hunsaker1-2/+2
Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
2013-02-23Updated exit codes as constant valuesDaniel Hunsaker1-2/+2
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-2/+2
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-10A tiny improvementAndrey Andreev1-3/+2
2013-01-01[ci skip] Happy new yearAndrey Andreev1-1/+1
2012-11-12Some micro-optimizationsAndrey Andreev1-1/+1
2012-11-01[ci skip] DocBlocks for Pagination, Session, Trackback, Jquery librariesAndrey Andreev1-4/+37
Partially fixes issue #1295
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-24[ci skip] style and phpdoc-related changes (rel #1295)Andrey Andreev1-0/+5
2012-06-04Revert/optimize some changes from 773ccc318f2769c9b7579630569b5d8ba47b114b ↵Andrey Andreev1-1/+1
and d261b1e89c3d4d5191036d5a5660ef6764e593a0
2012-06-02Replaced `==` with `===` and `!=` with `!==` in /system/librariesAlex Bilbie1-6/+6
2012-04-03Fix an issue in CI_Trackback::validate_url() and do some cleanup and ↵Andrey Andreev1-58/+42
optimizations in the library
2012-03-12Replace function_exists() checks with MB_ENABLED constanttiyowan1-1/+1
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-02Updating copyright date to 2012Greg Aker1-1/+1
2011-12-27Remove access lines from method descriptionsAndrey Andreev1-19/+0
2011-12-25Improve the Trackback libraryAndrey Andreev1-34/+15
2011-12-21Also replace old-style 'var' with 'public'Andrey Andreev1-6/+6
2011-12-19Add method visibility declarations and optimize display_errors() method in ↵Andrey Andreev1-24/+18
Image_lib, Trackback and Upload libraries
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-07-02backed out 648b42a75739, which was a NON-trivial whitespace commit. It ↵Derek Jones1-8/+8
broke the Typography class's string replacements, for instance
2011-04-25Fixed double-space typo.Razican1-8/+8
2011-02-14Whitespace cleanup in libraries/Pascal Kriete1-2/+2
2011-01-05Hey look, it's 2011Greg Aker1-1/+1
2010-11-10Changing all class constructors to __construct()Greg Aker1-1/+1
2010-11-10Updating PHP requirements in files 5.1.6Greg Aker1-1/+1
2010-10-04Cleanup of stray spaces and tabsBarry Mieny1-123/+123
2010-03-19Changed a few strstr to strpos for consistency w performance guidelines and ↵Robin Sowell1-1/+1
to mirror EE2.
2010-03-03changing casing on some booleansDerek Jones1-4/+5
2010-01-05updated copyrightsDerek Jones1-1/+1
2009-04-22updated copyrights to 2009Derek Jones1-1/+1
2009-03-11ereg eradicationDerek Jones1-5/+2
2008-11-13Changing EOL style to LFDerek Allard1-549/+549
2008-09-13(no commit message)Rick Ellis1-1/+1
generated by cgit v1.2.3-24-g4f1b (git 2.32.0) at 2024-11-14 04:20:29 +0100