CodeIgniter Date Helper vs PHP DateTime: Automatic DST Adjustment

Direct Answer

The CodeIgniter Date Helper does not implement its own DST engine. It delegates to PHP's date() and DateTime, so DST is applied automatically only when you supply a valid IANA timezone identifier such as America/New_York. Passing a raw UTC offset or an abbreviation will not reliably honor daylight-saving transitions.

Runtime changes to the framework's timezone configuration are respected for subsequent helper calls without a restart. In CodeIgniter 3.x, now() reads config['timezone'] on every invocation, so $this->config->set_item('timezone', 'Europe/London') takes effect immediately for the next call. Editing config.php on disk, however, requires a cache clear or process restart to be picked up.

The recommended pattern is to store all timestamps in UTC and convert at render time using PHP's native DateTime and DateTimeZone classes, which handle DST transitions correctly.

Confirmed Behavior vs. Likely Explanation

Confirmed: When you pass a valid zone string to the helper, PHP's underlying date functions apply the appropriate DST offset for that date. The helper adds no extra logic that would suppress or alter this behavior.

Likely explanation for confusion: Developers often call now() without a zone argument, relying on the global default. If that default is a fixed offset or an abbreviation rather than an IANA zone, DST will be wrong. Also, changing date_default_timezone_set() globally affects every date() call in the request, which can produce inconsistent results if other code assumes the application default.

Recommended Steps

1. Set $config['timezone'] = 'UTC' in application/config/config.php (CI3) or the equivalent environment setting (CI4).
2. Store database timestamps as UTC DATETIME or TIMESTAMP values.
3. When rendering, create a UTC DateTime object and convert it to the user's DateTimeZone:

   $utc = new DateTime($dbValue, new DateTimeZone('UTC'));
   $utc->setTimezone(new DateTimeZone($userZone));
   echo $utc->format('Y-m-d H:i:s');

4. If you prefer the helper, pass the user's zone explicitly: now($userZone) or use mdate() with a zone-aware format after temporarily setting the default.

Caveats

• The helper does not cache timezone objects. Repeated calls with many different zones in one request may add overhead from repeated date_default_timezone_set() calls.
• Changing the global default timezone mid-request affects all subsequent date() calls, not just the helper. Prefer explicit DateTimeZone objects for per-user rendering.

Assumption: This answer targets CodeIgniter 3.x, where the Date Helper reads the timezone config item on each call. If you are on CodeIgniter 4, verify whether your helper or service layer reads the config dynamically, because the framework's timezone handling differs between major versions.