Thank you for reporting this.
We’ve discovered that it’s caused by a typical plugin conflict, where both authors would name their variables in a rather simplistic manner and the coincidence of one such variable between different plugins would cause dysfunctionalities or misbehavior.
Once acknowledged, a fix is usually rather trivial for either party, however in the case of WpStream it may take a couple weeks to release a plugin update due to the rather complex product lifecycle.
To speed thing up, we decided to come up with a patch (downloadable unofficial release), do expect that no later than Tuesday.
Will post an update as soon as we have news, thanks again for letting us know of it.
Thread Starter
dbrady
(@dbrady)
Thank you.
Couple questions:
1) After hotfix, an updated version of WpStream will require another patch or include a permanent fix?
2) Does PeepSo need to update anything on their end after hotfix (besides the obvious of not using such a generic global name too)?
3) Maybe I am being simplistic, but “keys” being global in a WP plugin environment seems silly, by both of you. So I understand, a global name like “wpstream_keys” or for PeepSo, “peepso_keys” would have negated this type of conflict?
Tuesday is fine, and again, thank you…look forward to implementing WpStream on our platform, Don.
@dbrady
1. The updated version aims to include a permanent and stable solution
2. Not required
3. I must agree on the silliness of it; having named the variables as such would indeed have prevented the conflict; checking if there’s more of these has been discussed and will be handled prioritarily
Engineering has dedicated a thread to this matter. Updates will be posted there, technical queries are also welcome.
https://wpstream.net/forums/topic/conflict-between-wpstream-and-peepso
