Thread

One S for every time I’ve mentioned this, but since upgrading I’ve lost what line has the data/date typo and again entries are advancing one hour.  What line was it again in 20101215?

Blair,

Can you give some more detail please? What version did you upgrade from? I presume you are referring to EE2.1.3 you upgraded to?

And you say your entries are again advancing by an hour?
I remember previous bug but it should not be occurring again and I have seen no reports of it doing so.

Can you confirm you following the version update docs as opposed to the build update docs?

Specifically https://support.ellislab.com/bugs/detail/13150/ is back, and I’m looking for what line to change (instead of 105).  Last time I made this modification and it fixed the issue.

Blair,

Can you please confirm your Version and Build number.  It should be Version 2.1.3 Build 20101220.

Sincerely,

Barry Cogan

Yes, it is 2.1.2 and 20101215 as previously said.

Hi Blair,

Well then you need to to upgrade to our latest version 2.1.3 which fixes this issue, as John previously pointed out.

Sincerely

Barry Cogan

Is this in the change log?  http://ellislab.com/expressionengine/user-guide/changelog.html  I didn’t see it so I haven’t made the switch.

EE 2.1.3 is a required update for all users of 2.1.2. Please do upgrade.

Will this fix the +1 hour on edit issue without causing any additional issues?

Sorry Ingmar, I just noticed you pinged my last post about the change log about not “may not contribute* to resolving this support issue.”  Its the first time I’ve sen this, and I think it is very relative to helping resolve the issue of why a simple update has not been done.  It would be best for those looking at this forum thread in the future to know how this issue can be fixed and why other admins may make the same choices.

Blair,

Will this fix the +1 hour on edit issue without causing any additional issues?

If you run into any issues after upgrade feel free to post here again but your date issue should not be there anymore

It would be best for those looking at this forum thread in the future to know how this issue can be fixed and why other admins may make the same choices.

I’m not quite following here. I think I am missing a bit of the picture. What other post of yours are you referring to?

Sorry Ingmar, I just noticed you pinged my last post about the change log about not “may not contribute* to resolving this support issue.”

Just for the record, that wasn’t me. That said, yes, an upgrade is strongly recommended in any case.

I can’t continue this thread until this is resolved.

Hi Blair,

I’m sorry, I’m not following you. Have you upgraded to 2.1.3?

Cheers

Greg

Sorry guys, I just can’t continue if you’re censoring posts.  It’s bad support, and bad business, and we’re not getting anywhere by doing so.