Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Also, their property is no longer public and the utility class no longer extends CI_DB_forge.
|
|
|
|
|
|
- PDO subdrivers are isolated from each other now.
- Added compatibility for pretty much all of the features, for every DB platform.
- Unified the way that stuff works in general.
- Fixes issue #1005.
|
|
Fails if called prior to the DB connection initialization.
|
|
Seems to be causing issues (see #1970).
Also updated the Controller docs, mainly to include an important note related to #1967.
|
|
Fix / Disallowed Key Characters.
|
|
Fix #1946 dbforge add_key
|
|
|
|
squaresurf/d2ae1d1d7fdc4b8a21369a25487c2c42e5a496bf
Refactored Unit_test in order to remove redundant code.
|
|
|
|
Fixed typo in logs
|
|
It appears to break get_instance()->*_package_path*() usage which is very common.
Need to figure out how to resolve this.
|
|
|
|
The Unit_test::run method was adding another dimension to the
Unit_test::$results array. For example:
Array
(
[0] => Array
(
[0] => Array
(
[test_name] => first_test
[test_datatype] => integer
[res_datatype] => integer
[result] => passed
[file] => ########################################
[line] => 60
[notes] => Im expecting this test to pass!
)
)
[1] => Array
(
[0] => Array
(
[test_name] => second_test
[test_datatype] => integer
[res_datatype] => boolean
[result] => failed
[file] => #######################################
[line] => 65
[notes] => Im expecting this to fail.
)
)
)
The above unneeded dimension created a need to loop through an array in the
Unit_test::result method if the method was looping through all results.
Signed-off-by: Daniel Paul Searles <daniel.paul.searles@gmail.com>
|
|
That method used to be called by the CI_Controller constructor
and was required because of the possibility to instantiate the
Controller class twice due to 404_override, and so some properties
needed to be reset.
Following the last commit - this is no longer the case.
|
|
- Don't instantiate the CI singleton twice.
- General clean-up.
- Fix issue #953.
|
|
|
|
|
|
|
|
|
|
An improved version of changes suggesed in PR #1352, and more specifically:
https://github.com/sourcejedi/CodeIgniter/commit/8f7d2dfe42bd8543981c0f295e391e433d82fd42
https://github.com/sourcejedi/CodeIgniter/commit/d2de251c092d9d822fc4898e3681b64e9c74dd2a
(thanks again @sourcejedi)
|
|
Partially fixes issue #1295.
|
|
Partially fixes issue #1295.
|
|
Partially fixes issue #1295.
|
|
Partially fixes issue #1295.
|
|
Partially fixes issue #1295
|
|
Partially fixes issue #1295
|
|
Partially fixes issue #1295
|
|
|
|
Supersedes PR #642
|
|
Also partially fixes issue #1295, fixes inconsistencies in some page-level docblocks and adds include checks in language files.
|
|
|
|
|
|
Re-instaing an improved form_prep() function, reverting most of the changes from 74ffd17ab06327ca62ddfe28a186cae7ba6bd459.
|
|
|
|
- Changed docs CREATE TABLE ci_sessions example to have the PRIMARY KEY of session_id, ip_address and user_agent combined.
- Changed DB updates to add WHERE clauses for the ip_address and/or user_agent strings if sess_match_ip and/or sess_match_useragent are set to TRUE.
|
|
|
|
(thanks to @sourcejedi, PR #1326)
Up until PHP 5.2.4 (which is our new lowest requirement),
there was a bug related to PATH_INFO which made REQUEST_URI
a more reliable choice. This is now no longer the case,
see https://bugs.php.net/bug.php?id=31892 for more details.
Also removed ORIG_PATH_INFO from the suggested alternatives
for uri_protocol in application/config/config.php as it will
not exist in most of PHP's recent versions and is pointless
when you can use PATH_INFO anyway.
|
|
add_key not setting multiple-column keys when given array
Signed-off-by: GDmac <grdalenoort@gmail.com>
|
|
f2b19fee7876708c7a7bb5cba6b7df682a9d2a53
|
|
(thanks to @sourcejedi, PR #1326 for pointing inconsistencies with RFC2616
|
|
Processed routes
|
|
|
|
|
|
(thanks to @sourcejedi, PR #1326 for most of the ideas)
- Renamed _detect_uri() and _parse_cli_args() to _parse_request_uri() and _parse_argv() respectively.
- Added _parse_query_string() which allows us to detect the URI path from QUERY_STRING much like it is done in _parse_request_uri().
(the above changes also allow for a simpler logic in the case where the *uri_protocol* setting is not set to 'AUTO')
- Updated application/config/config.php with a better list of the *uri_protocol* options.
- Added _reset_query_string() to aid in re-processing from the QUERY_STRING (utilized in _parse_request_uri() and _parse_query_string()).
|
|
(thanks to @sourcejedi, PR #1326)
For HTTP/1.1 compliance, RFC2616 specifies that both relative
and absolute URI formats must be accepted:
- http://localhost/path/ (absolute)
- /path/ (relative)
|
|
|
|
Where the email library removed multiple spaces inside a plain text message.
Signed-off-by: GDmac <grdalenoort@gmail.com>
|