Thread Starter
tiago
(@tiagogoncalves)
I was not able to upload WooCommerce afterwards through the admin panel with Stream deactivated neither. But I did no get any “notice:” message this time .
I was forced to updated it through FTP.
I’m a bit afraid to activate Stream again afterwards. Needless to say I love Stream. I think these two plugins match perfectly on a online store in order to track customers logins. It would be cool if you guys could assure the compatibility.
Thank you!
Hi @tiagogoncalves,
I’ve just tried to reproduce your error but couldn’t using Stream 1.4.4 and updating WooCommerce to the latest version, it happened seamlessly without errors.
From what i’m seeing in your log, the update didn’t really happened, and Stream would probably have nothing to do with that since it hooks AFTER the plugin has been actually updated. Note:
> Could not remove the old plugin
> Plugin update failed
If you can fix that, you’d probably be fine working with Stream afterwords.
Great to know you’ve fixed the original issue you were having, and this seems like Stream wasn’t able to handle the errornous install attempt, not at all a compatibility issue with Woocommerce.
/five!
Thread Starter
tiago
(@tiagogoncalves)
cool! great to know. so let’s be back on Stream 😉
Thread Starter
tiago
(@tiagogoncalves)
Hey again @shadycb!,
Today i tried to update Stream to its last version and i got exactely the same message:
Notice: Undefined offset: 0 in /var/www/miasapro/wp-content/plugins/stream/connectors/installer.php on line 159
on my error_log.txt also says just that:
[15-May-2014 08:56:06 UTC] PHP Notice: Undefined offset: 0 in /var/www/miasapro/wp-content/plugins/stream/connectors/installer.php on line 159
I have no idea what it’s causing that. I hope this info can be useful to you.
Thread Starter
tiago
(@tiagogoncalves)
and i will install the plugin via ftp, again. if you have any idea about the cause of this, please share it.
Thanks!
I’ve checked the last time and couldn’t either reproduce nor grasp the possible reason for this, update via FTP, and make sure you deactivate/activate the plugin to install any required DB updates, and lets see if that happens again, We’ll certainly work with you then to work it out if it still persist.
/five!
Thread Starter
tiago
(@tiagogoncalves)
The FTP update and the database update seam to have worked just fine. I will update you here in case i have the same error message on a next plugin update 😉 Thanks!
