CiviCRM Community Forums (archive)

I have an update.  I figured out how to embed PHP code in a WordPress post.  I embed "echo date(DATE_RSS)" in a test post.  It displays GMT.  So the problem is not CiviCRM.

Any ideas on how to trouble shoot this?

For those interested, I installed the "Allow PHP in posts and pages" WordPress plugin.  Here's what I put in the test post:

<phpcode>
<?php echo date(DATE_RSS); ?>
</phpcode>

Has anyone else tried this with success? If I muck around this php file has it broken anything CiviCRM? I guess my question: is this Civi-approved or is that a non-issue? Thank you!

I'm not sure the fix in 4.3.3 fixed all the time zone issues.  In particular when you enter a new contribution the 'Time Received' defaults to UTC not local time.  The mod to " wp-settings.php' makes the default local time.  This was one one reason I originally investigated this.  The other was the CRON run times which I didn't check to see if 4.3.3 fixed.

I tested this by upgraded a vanilla 4.3.1 test installation I have to 4.3.3 and then selecting add new contribution.

I agree that you don't want to hack the code and that it would be best for CiviCRM to set the time.  But in this case I believe the WordPress code is designed to let you set the time zone.  Here is the code:
// Set default timezone in PHP 5.
if ( function_exists( 'date_default_timezone_set' ) )
date_default_timezone_set( 'America/Chicago' );Normally it reads UTC.

Until I can figure this out, I'll have to hardcode the time zone.

Update: We did upgrade to 4.3.3 and the Time Zone did not adjust correctly. I did have to go into the wp-settings.php file and set the default time zone to 'New York', and also changed it in settings in Wordpress dashboard. Date is now showing correctly in CiviCRM. (For example, when adding a contribution for an individual contact, the time did show the correct time.)

Thank you to all who share in this forum, I find it very helpful as a beginner! Peace! 

I'm not sure the patch fixed all of the timezone issues either. Particularly: scheduled jobs (*when executed through the cron.php URL method*) still show UTC time even though other dates reflect the proper timezone.

Going to put the workaround hack in the config files until it's fixed.

I'd like to reiterate that on CiviCRM 4.3.5 this is still broken on the cron.php execution path.
I've noticed that when running scheduled jobs manually, they correctly adjust their timezone (likely because CiviCRM is running inside the Wordpress "context".

However, when running a cron job against /bin/cron.php directly, the timezone offsets are different. This is causing Jobs scheduled to run at say 8AM EST to actually run at 8AM GMT when cron triggers them, but to run at 8AM EST when run manually via /wp-admin/.

Since the cron.php file is being called directly, and not as part of Wordpress, it seems a better solution to this would be if CiviCRM tied the cron.php execution into the existing wp-cron.php functionality that's used on Wordpress sites. At the moment, it doesn't appear to be using that as setting a cron job up for wp-cron.php doesn't cause the CiviCRM scheduled jobs to run.