summaryrefslogtreecommitdiffstats
path: root/system
AgeCommit message (Collapse)AuthorFilesLines
2016-02-15Remove reference usage from last commit ... it's uselessAndrey Andreev1-1/+1
2016-02-15Pass CI_Config as a parameter to CI_URI constructorAndrey Andreev2-3/+3
2016-02-15Don't apply url_suffix, permitted_uri_chars to CLI requestsAndrey Andreev1-50/+68
Close #4085 Close #4460
2016-02-09Rename back a variable changed by the last PR mergeAndrey Andreev1-4/+4
Because.
2016-02-09Merge pull request #4342 from jspreddy/sai/form_validation_refactorAndrey Andreev1-30/+36
Abstract error message fetching in Form_validation
2016-02-09Merge branch '3.0-stable' into developAndrey Andreev8-43/+72
Fixed conflicts: user_guide_src/source/overview/at_a_glance.rst
2016-02-09Code formatting changes, again. I am bad at this.Sai Phaninder Reddy Jonnala1-6/+5
2016-02-09Merge pull request #4323 from ↵Andrey Andreev1-3/+20
jspreddy/sai/log_line_formatting_extensibility_change Refactored CI_Log line formatting to allow extensibility
2016-02-09Merge pull request #4323 from ↵Andrey Andreev1-3/+20
jspreddy/sai/log_line_formatting_extensibility_change Refactored CI_Log line formatting to allow extensibility
2016-02-09Merge pull request #4445 from damiengrandi/developAndrey Andreev1-9/+9
[ci skip] Update QB phpdoc returns
2016-02-09fix a typo editDamien Grandi1-1/+1
2016-02-09Revert some previous changesDamien Grandi1-3/+3
2016-02-09Update DB_query_builder.php - phpdoc (some incorrect return type)Damien Grandi1-12/+12
Edit of some return type in phpdoc. This can also help to fix some autocompletion troubles in some IDE.
2016-02-08Doc block formatting change.Sai Phaninder Reddy Jonnala1-4/+3
2016-02-08code styling changes as suggested by @narfbgSai Phaninder Reddy Jonnala1-21/+15
2016-02-07hunanize() helper: Escaping the $separator argument.Ivan Tcholakov1-1/+1
2016-02-05Merge pull request #4424 from jonty-comp/developAndrey Andreev1-3/+16
[ci skip] Fix PHP session_write_close() warning when writing a new session to Redis
2016-02-05Merge pull request #4424 from jonty-comp/developAndrey Andreev1-3/+16
[ci skip] Fix PHP session_write_close() warning when writing a new session to Redis
2016-02-05Fix regression on PHP7 when regenerating the session (#4362)Jonty Sewell1-1/+3
2016-02-05Fix another regression caused by 805eddaefd9503b5dbbd924bd6da66e29c4768f3Andrey Andreev1-3/+3
Also added a unit test for #4431
2016-02-05Fix a regression caused by 805eddaefd9503b5dbbd924bd6da66e29c4768f3Andrey Andreev1-2/+2
2016-02-05Fix #4431Andrey Andreev1-5/+4
2016-02-05Setting the flag to FALSE is unnecessary since it defaults to FALSE, ↵Jonty Sewell1-10/+1
therefore this block of code can be reduced to a single statement Signed-off-by: Jonty Sewell <jontysewell@gmail.com>
2016-02-05Set the _key_exists flag to TRUE when the key does in fact exist. Set it to ↵Jonty Sewell1-2/+7
FALSE if the ID is being regenerated, and set it to TRUE once it's been written. Signed-off-by: Jonty Sewell <jontysewell@gmail.com>
2016-02-05Add a flag to determine whether the redis key currently exists, and if not, ↵Jonty Sewell1-2/+17
force creation of it at write-time Signed-off-by: Jonty Sewell <jontysewell@gmail.com>
2016-02-05Revert previous changes - fixing the source of the problem rather than ↵Jonty Sewell1-9/+3
working around it Signed-off-by: Jonty Sewell <jontysewell@gmail.com>
2016-02-04[ci skip] fix commentClaudio Galdiolo1-1/+1
2016-02-04[ci skip] fix commentClaudio Galdiolo1-1/+1
2016-02-04Add batch_size param to insert_batch(), update_batch()Andrey Andreev1-6/+6
This should resolve #42
2016-02-04Fix #4430Andrey Andreev1-0/+6
2016-02-04Fix #4427Andrey Andreev1-22/+23
2016-02-03If attempting to write an empty session to Redis, a key will not actually be ↵Jonty Sewell1-3/+9
created, so when the driver tries to set the expiration timeout on the key, 0 is returned, triggering a warning from session_write_close Signed-off-by: Jonty Sewell <jontysewell@gmail.com>
2016-01-30Fix #4415 and add unit tests for https://bugs.php.net/bug.php?id=51192Andrey Andreev1-0/+8
2016-01-29Fix an error from 6af9dd6e24687b6a7b9d14a058a47edcac761e61Andrey Andreev1-1/+1
Related: #4407
2016-01-29Fix #4407Andrey Andreev1-3/+18
2016-01-29Fix a regression in Form helper caused by ↵Andrey Andreev1-2/+2
0139e6a4a99cbe9b0cc06f394fa12d5691193b72
2016-01-27Fix #4401Andrey Andreev1-4/+4
2016-01-26Merge branch '3.0-stable' into developAndrey Andreev3-24/+55
2016-01-26Fix #4399Andrey Andreev1-15/+28
2016-01-25Fix #4395Andrey Andreev1-1/+15
2016-01-20[ci skip] Remove a trailing space from latest PR mergeAndrey Andreev1-1/+1
2016-01-20Respect $config['cur_page'] variable for paginationjekkos1-1/+5
After upgrading to CI3 I noticed that developers are able to determine the current page counter for pagination based on * Explicit query string parameters * URI segment configuration In earlier versions a developer could still set the current page counter in the pagination lib directly which is useful if you want to use pagination with HTTP POST instead of GET. This could be done by passing $config['cur_page'] = '10'; to the pagination function for link generation. Currently this code has changed and will always try to check whether the uri segment is a valid number or not, even if the cur_page variable was passed in the associative array, and fallback to zero if it fails to validate that result. This can be easily resolved by checking whether the counter was already set with a valid number from the $config array before trying to resolve it from the uri segment. This fix give a developer more flexibility and stop CI from overwriting the externally set value with an incorrect one. Signed-off-by: jekkos <jeroen.peelaerts@gmail.com>
2016-01-20[ci skip] Remove a trailing space from latest PR mergeAndrey Andreev1-1/+1
2016-01-20Merge pull request #4384 from jekkos/pagination-fixAndrey Andreev1-1/+5
Respect $config['cur_page'] variable for pagination
2016-01-20Respect $config['cur_page'] variable for paginationjekkos1-1/+5
After upgrading to CI3 I noticed that developers are able to determine the current page counter for pagination based on * Explicit query string parameters * URI segment configuration In earlier versions a developer could still set the current page counter in the pagination lib directly which is useful if you want to use pagination with HTTP POST instead of GET. This could be done by passing $config['cur_page'] = '10'; to the pagination function for link generation. Currently this code has changed and will always try to check whether the uri segment is a valid number or not, even if the cur_page variable was passed in the associative array, and fallback to zero if it fails to validate that result. This can be easily resolved by checking whether the counter was already set with a valid number from the $config array before trying to resolve it from the uri segment. This fix give a developer more flexibility and stop CI from overwriting the externally set value with an incorrect one. Signed-off-by: jekkos <jeroen.peelaerts@gmail.com>
2016-01-20Fix #4391Andrey Andreev1-7/+11
2016-01-20[ci skip] Fix a documentation error on output cache timesAndrey Andreev1-1/+1
2016-01-20Default doctype is now HTML 5Sébastien Adam1-1/+1
2016-01-15Code styling changes as suggested by narfbgSai Phaninder Reddy Jonnala1-8/+10
2016-01-13[ci skip] Mark the start of 3.0.5 developmentAndrey Andreev1-1/+1
generated by cgit v1.2.3-24-g4f1b (git 2.32.0) at 2024-11-06 14:29:34 +0100