Geoff Taylor

@xparham Thanks for testing it. @mcdonna I’ll be marking this resolved then.

@mcdonna Can you re-run your tests against Stream 3.6.2?

@mtruitt Recently, I’ve actually been doing some testing on the WooCommerce connector, and you are correct. Despite having an action for tracking WooCommerce attribute deletion, it no longer works as designed due to a possibly moving of the connected hook in update to WooCommerce.

With the move in place, it is not longer possible for the retrieval of any meta data related to the attribute being deleted.

Only the attribute ID is accessible, and there are no other hooks available for use with the data necessary to make a meaningful message.

• This reply was modified 4 years ago by Geoff Taylor.
• This reply was modified 4 years ago by Geoff Taylor.

@ofmarconi Stream is designed to monitor activity in the WordPress dashboard. It sound like to need to monitor front-end traffic something that should be possible with Google Analytics.
A plugin like this may work for what you need.

• This reply was modified 4 years, 2 months ago by Geoff Taylor.
• This reply was modified 4 years, 2 months ago by Geoff Taylor.

@user4302593 All stream records are printed to the stream log in the WordPress Admin, regardless of what alerts are set, however the records can be filtered using the table controls.

@sumeetbiswal Are you loading the connector class using the wp_stream_connectors filter? Read more about it here. If that doesn’t your issue, open an issue on the Stream repository and I will personally help you there.

@gagan0123 I’ve recently been experiencing this issue as well, but had no idea what was causing it. Your insights on when the error begin to occur, actually gives me a really good idea of where this issue is in the code. I’ll determine if my hunch is correct, and begin patching process as soon as I can.