From Djpaul’s suggestion.,
Deactivating all plugins……
Timestamps still wrong.
I am using buddypress columns theme
The “omgpizza” patch is outdated for 1.2.7
@Bigjimmysisco how do you mean patch is outdated? The patch was to correct an issue found and it was rolled into 1.2.7 as part of the reason 1.2.7 was released to push through a few important fixes in advance of 1.3. If you are running 1.2.7 then that patch should be merged in to 1.2.7 so you shouldn’t need to change anything but if those lines are missing then there’s something odd at work.
@all I’m afraid that without someone providing access to an affected machine it is really hard for anyone to fix the issue or track the issue down.
I have checked my live test install and that is running 1.2.6 with the omgpiza patch manually applied and I see no issues, which tends to bring me back to thinking it’s a server timezone issue – not the time itself but the timezone the server thinks it’s in, however I’m perplexed by the fact that posting a WP comment reports correct time.
Actually I have an idea that might fix the issue.
Where in the core are the timespamps’s code located? Because if I take the code from 1.2.5.2, (where it works) and replace it in 1.2.7, it might fix the issue for us that are having problems. for example like is it in bp-tamplatetags.php?
@hnla I mean outdated as in the fix is already applied in 1.2.7.
`
From Djpaul’s suggestion.,
Deactivating all plugins……
Timestamps still wrong.
I am using buddypress columns theme
`
Can you test again with no extra plugins on the BP-Default theme, and when you post a new activity stream item? The “new activity stream item” bit is important. Thanks.
@bigjimmysisco, good idea! I will do some copy and pasting from 1.2.5.2 into 1.2.7 to see what file is causing it..
@bigjimmysisco I mean the username/password to your files, so I can access them through an FTP client. I have a feeling that this problem is not going to be solved unless I or another developer can test on an actually affected installation.
Everybody, I think I have found my solution.
Please forgive me and I am so sorry, as I am the buggiest moron!
This could be a bug, but I have no idea.
For some reason, setting your wordpress timezone to the “set city” sections, such as setting it to “denver”, the timezone gets off by hours.
In wordpress general settings, in the timezone, scroll all the way down to the “manual offsets” such as UCT-7 and that type of time code.
This solved my problem, I have no idea why it does this… mmhm
Awesome!!!! worked!!! times are back to normal! Thanks!!! 
Set “los angeles” to manual time offset UTC-6
Hmm have to say I’ve never set it other than by using the UTC settings, just tested changing to city ‘London’ and it didn’t produce any problems on my live test server.
Setting it to UTC didn’t do anything for me… it’s still off by 4 hours. 
You said earlier:
good idea! I will do some copy and pasting from 1.2.5.2 into 1.2.7 to see what file is causing it..
Did you actually do that? as 1.2.5.2 wasn’t fixed for this issue and you would have introduced the problem not solved it and no setting would change that fact.
@VegasParty607 Make sure you set it to the proper UTC offset – not simply UTC, but UTC-5 (for example, if you are in the US Eastern Time Zone)
Thanks for your patience with this, gang. I’m going to investigate whether this is a BP problem or a problem with WP itself.
@hnla, every single one i did, I got a Cannot Re-declare notice so I sort of gave up.
Wow, you are awesome! Thank you! I had the same problem and changing it from New York to UTC-5 fixed this for me. Thanks!
Thanks a bunch!!! Worked!!! changed it from Denver to UTC-7 fixed it!!
@bigjimmysisco, worked. You are a lifesaver!
Wondering if it’s some sort of weird WordPress bug or something unusual on your host’s servers.
UTC-5 works for me. I was originally 4 hours ahead.
Strange – i implemented the workaround (setting timezone to UTC-5 rather than ‘New York’) several weeks ago and it resolved the problem, but the problem resurfaced today without anyone touching the timezone setting.
Anyone else experiencing this?
