Shady Sharaf

Thank you Greg, always happy to help!

You may need to refresh your permalinks, just be visiting ‘Settings > Permalinks’ page. Let me know if it worked.

Or it can be some custom code in your theme, and as @luke has said, author/IP represents the session owner, not necessarily that he initiated the action himself, but instead plugin/theme code would be responsible for this while the user is on the website.

I’ve just created an issue to track such problems even better:
https://github.com/x-team/wp-stream/issues/467

However, i think you can narrow the suspect code base by using the following shell command in the root of your site:
grep -r ‘update_option.*expiration’ /root/to/your/site

The issue has been resolved and an update should be out shortly.

Thanks for your patience, and sorry for any inconvenience this might have caused you.

Shady

The issue has been resolved and an update should be out shortly.

Thanks for your patience, and sorry for any inconvenience this might have caused you.

Yes it should retain your historical data, and your data is probably still there in database, Stream just might not be able to display it because the database upgrade did not go smooth.

Can you tell me what version did you upgrade from, so i can reproduce the error ?

Thanks,
Shady

Hi bemdesign,

Have you been able to update your database table, through the notice that should have been shown in admin area after updating to the new version ?

You’ll need to disable TML to get access to the page within administration area, where links should be working.

Hi darlantc,

It seems that your opcache handler has a problem with Closures, try disabling caching to double check. Your hosting provider can probably help as well.

This issue has been fixed recently, though not yet released. Please expect it to be fixed in the new version, which should be out quite soon.

I’ve just opened a new ticket at our GitHub repo ( https://github.com/x-team/wp-stream/issues/434 ) so we can investigate this further.

Thanks for reporting this! We’ll get back to you once the ticket has been looked into.

Can you please check if Stream is tracking normal user login from wp-login.php ? eg: for administrators.
We need to narrow down possible causes.

Yes, this is probably the cause of your problem, however .. wp_signon does fire the wp_login action which we hook into, but you need to make sure that the final do_action('wp_login', ...) receives proper expected arguments.

You can check Stream settings so you make sure you have not excluded that specific rule, or the login action altogether.

And just to make sure, no user login events are tracked at all ? or just author logins ?

Also make sure you’re running the latest version of Stream.

Stream does track user logins. Have you had any problems with this specific feature ?