EasyBlog and EasySocial Stream issue when setting publish date to a future time
By CC Group on Thursday, 10 December 2015
Posted in General Issues
Replies 5
Likes 0
Views 1K
Votes 0
Our environment has EasySocial and EasyBlog integrated with the Blog app for EasySocial.

If one writes a blog post and wants to auto publish that post in the future (it doesn't matter if it's 5 minutes or 5 days or any length of time) then when the blog is posted there will not be any entry in EasySocial stream.

I hope I am not doing something wrong, I have tried this about 5 different times with different settings and I cannot get a stream entry when posting in the future. I have also tried this on your Demo site and have the same issue.

Should it be working this way or is this a limitation of the software? If this is not an available feature, are you working on it?
If this is supposed to work, can you confirm it is a bug or if it is just a configuration issue?

Thank you!!
Hi CC,

Thanks for the report. I just tested this out locally and it seems like the stream will fall under "updated a blog post" stream type instead of "Created a new blog post" stream. Check my screenshot here for a better view, http://screencast.com/t/RAUXm8aM0Utv .

I will add this into our codebase so that they can fix this issue in the next release of easyblog.
Ezrul Fazwan
·
Thursday, 10 December 2015 11:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Ah yes, you are right Ezrul, I realize now my site and the demo site are not set to notify upon updating a blog post. This is why I saw no stream activity at all, but when I enable the notification I can see the "updated a blog post" stream item when future posting. Good work! This may be a workaround for the moment.

However, you are also right and I agree this type of post should fall under "Created a new blog post", so thank you for adding this to the codebase! Do you have a link I can have to track the bug progress?

Thank you!
CC Group
·
Thursday, 10 December 2015 23:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey,

Unfortunately our issue tracker is currently not accessible by public and as much as I want it to be as transparent as possible, I don't have the time to write our own issue tracker

We have actually done this for our changelog / beta testing / voices area but we'll need to figure out a way to make this public in the future
Mark
·
Friday, 11 December 2015 18:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Mark,

Thanks for clarifying that about the issue tracker, and please don't worry about it. It's nice to be able to track, but I can live with just knowing a fix is on the way.
As usual, you and your team are doing great work so just keep it up and I'm sure you'll find time to work on that kind of project if you want to.
CC Group
·
Friday, 11 December 2015 22:19
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks a million for being so understanding!
Mark
·
Saturday, 12 December 2015 00:41
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post