Hello Rene,

I'm not sure what is happening in your site because I can't replicate it. However, my best guess is this option: http://screen.stackideas.com/2015-01-02_1028.png . Did you deleted a user previously?

hi Nik, i used this Option beföre the acccident and owner for Orhan items was set to ID 62. yes i deleted one User previously via Jomsocial Memberlist, but i beliebe that's not a rreason why All Guest Comments created_by values are changed from 0 to 62!?

b.t.w why did you save all these Guest User ID 0 activities in discuss_users_history? ok for a Registered User ID that makes sense but for Guest Actions? This table get a huge size during one year!

Hello Rene,

I am sorry for the late reply.
I have checked this locally, and actually we do keep track for guest history and I believe you have a good point to remove it since it will overload the database over some time. I will discuss this issue with our developer regarding this issue. Thanks for the heads up.

However, regarding this issue:

All Guest Comments with value created_by 0 in EB easyblog_comment changed now from 0 to 62

I can't replicate this issue with our local. Here is my steps taken:
1. Guest create a new discussion. ( 0 user_id in discuss_users_history table)
2. Guest comment on blog post. ( 0 created_by in easyblog_comments table)
3. I have deleted user_id 0 entrys in discuss_users_history table through phpmyadmin.

However, the created_by 0 in easyblog_comment table doesn't change to new owner for orphan items. Perhaps I have missed some steps reproduce this.

Please advise.
Thanks.

hi nik, what did your developer mean about all those guest (user_id 0) entry in discuss_users_history table?

about the new owner for guest comments:

thanks for your local test..i think your steps are similar then mine, but all i can say is that it happend! the question is now what other EB function is able to change "all" guests comments created_by values from 0 to orphan 62

Hello Rene,

I believe the only function that change the created_by id is when the user is deleted. Which is called in user plugin.

what did your developer mean about all those guest (user_id 0) entry in discuss_users_history table?

This table is used to store any activity in Easydiscuss regardless he is guest or registered user. Meaning here, if Guest user reply to discussion, it will also be stored in the table.

Am I answer your question correctly?

hi Nik, i unterstand if if Guest user reply to discussion or add a comment in EB. but most of the entries in discuss_users_history table are from guests wich viewed a Blog! and this makes no sense i guess and blow the database during the time!

Did i explained the issue correctly?

Hello Rene,

The reason that the database table discuss_user_history is storing those actions is because we are keeping track of user actions and this is only if you have EasyDiscuss installed and if you are using EasyDiscuss. If you don't you don't have to worry.

As to whether or not it blows up your database, I guess we probably need to add an automated archiving system for user actions in EasyDiscuss in the future.

ok this issue is occurred again. some guest comments are changed to orphan item ID 62

how to reproduce:

i remenber that i if have deleted some Active and Archived Activity Stream Items from JS Backend inluding Guest Comments streams. after this action changed those Guest comments from 0 to 62 ID

so i think this is a Bug!

i do now manually restore the previous state in Database but i think you should test this scenario with your local!

Hello Rene,

By default it should behave like that since the deleted user/guest will become an orphan status. This orphan status will then fall back to the current user id set at your backend > easyblog > settings > workflow > maintenance > Orphan Items, http://screen.stackideas.com/2015-03-24_1812.png

Hence I guess it is not a bug after all. Perhaps you might want to create a new user with sole purpose to become the owner of the orphan user and set the user id from the setting that I've mentioned above. Hope these can clarify the issue