Fixed on:

Tomcat 7 + MySQL 5. 6.1.x EE Portal GIT ID: 4e3c632a20e2070de862b7e2eddd3629a993b2c9.
Tomcat 7 + MySQL 5. 6.2.x EE Portal GIT ID: b6a46f65504614434eaa52c4aa4cbc3bf45971cd.

Committed on:
Portal 6.1.x CE GIT ID: 431e82da4afcfe2cb42d9838fb0a7bc02d5367f6.
Portal 6.2.x GIT ID: 656006aab3af139ce37ac91b6a871bbc5edb2da2.

It was possible to set the display date in the future, but the side effects of that behaviour wasn't take into account.
There are several non-covered use cases that we're fixing in this ticket

Juan,

I've performed the changes, can you please take a look on it? Let me know if you have any questions.

Thanks,

Máté

Hi Juan,

For the separate LPS tickets, I wouldn't go that way, because all of the bugs are related, basically the root cause for all the problems are that if you create a blog entry with a future display date, all the related things won't be up-to-date when to future date for that entry comes. Like the Blogs Stats are not getting updated at the specified future date, but the social activity on the other hand will show a new record. So after all the bugs are related, the changes are taking place in the similar classes and similar parts of the portal, that's why I decided to go with one single LPS.

About the merging: I can merge the things you have asked for, the reason I did it this way is because this way the commit history shows clearly what happened with that specific part of the code what happened after what, but I'll go ahead, merge the stuff, and I'll send a new pull request to you.

Thanks,

Máté