Age | Commit message (Collapse) | Author | Files | Lines |
|
Supersedes PR #3132
|
|
I don't see why it should be enabled by default. Also, this is the functionality triggering #2923
|
|
|
|
|
|
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
As described in issue #2870
+ A change in the „How to create a library” example in the user_guide
|
|
Update copyright notices from 2013 to 2014.
And update one calendar example in user_guide from year 2013/2014 to
2014/2015.
|
|
|
|
- Initialize and cache the value in the class constructor instead of searching for it every time
- Removed the preg_quote() call from _filter_uri() to allow more fine-tuning from configuration
- Renamed _filter_uri() to filter_uri() - it was public anyway and using it cannot break anything
Related: issue #2799
|
|
Based on PR #964
|
|
Added ['standardize_newlines']
Also altered the Session cookie driver, which experienced issues with this
feature due to it's HMAC verification failing after the Input class alters
newlines in non-encrypted session cookies.
Supersedes PR #2470
|
|
Nginx and Lighttpd
* The rangeDownload() function has been moved to libraries/Ddownload/drivers/Ddownload_php.php
* The nginx and lighttpd drivers can be set via $config['download_driver']
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
|
|
To enable set:
$config['authentication_driver'] = 'fluxbb';
$config['auth_fluxbb'] = array('database' => 'fluxbb');
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
Add example array to config.php
Remove $optional_functions from Duser_fluxbb to follow
bb9f9274e8c2d661a1adffd87c87c3d81ec47b4d.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
|
|
Added list of valid characters to sess_cookie_name
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
This supports more caching backends and doesn't force users to install
the memcache extension.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
|
|
whatever is preferred. example (.log)
This is a follow up to this pull request.
https://github.com/EllisLab/CodeIgniter/pull/2243
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
This can be used to track data for all kinds of one-time actions like
invitations and password resets.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
so that it's only called by drivers that need it ('mysql', 'mssql').
As proposed in issue #2187.
|
|
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
|
|
(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.
|
|
(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()).
|
|
|
|
Signed-off-by: dchill42 <dchill42@gmail.com>
|
|
Apart from database.php, config.php and memcache.php the files shouldn't
be different so we can just track them in the repo.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
|
|
|
|
https://github.com/atiredmachine/CodeIgniter into develop
|
|
time_reference setting - 'GMT' is a valid timezone, so nothing needs to be changed in order to work properly (upgrade notes) - Altered some description text
|
|
|
|
changed.
|
|
|
|
|
|
|
|
|
|
|
|
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...
|
|
|
|
CSRF optional token regeneration
|
|
|
|
|