By JF on Wednesday, 04 February 2015
Posted in Technical Issues
Replies 3
Likes 0
Views 0.9K
Votes 0
Basically the issue I'm having is that when you use the EasyBlog migration import function in EasySocial, it imports everything as a blog entry with the date of when the import was run, not when the blog entry was originally posted. So I have 8 years' worth of posts that now all appear over a few hours of stream entries. They also are in reverse order so it is even weirder.

Expected behavior: importing items and making new stream entries for Kunena and EasyBlog would result in stream entries having the timestamp of the item being imported, making it a useful function vs. something I'm going to have to figure out how to delete now (which brings me to my second question - is there an option somewhere to clear out the stream?)
Hi,

I apologize as I can't replicate this issue locally. Can you kindly provide us backend access and FTP access so that we can further investigate this issue on your site?

As per your second inquiry, you can clear the stream by purging/trashing the stream at EasySocial > Stream > delete/purge.

Hope this help.
·
Wednesday, 04 February 2015 13:52
·
0 Likes
·
0 Votes
·
0 Comments
·
I don't have FTP on my server, but I'm happy to give you a site backup or backend access if you want to pull down a backup.

Did you check it with EasyBlog specifically? Importing Joomla articles into EasyBlog articles pretty specifically sets the stream items as the time/date of the import vs. the creation/modification date of the article. Should be simple to replicate that part.
JF
·
Wednesday, 04 February 2015 23:59
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

If I understand your issue correctly, you're migrating Joomla article to EasyBlog, then it creates EasySocial streams in your site isn't? If so, here I have attached to you a file, can you please download it and put it in your site here: .../components/com_easyblog/helpers/easysocial.php .

Please give it a try.
·
Thursday, 05 February 2015 00:36
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post