-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GEOFENCE: Presence Functionality Turned Off #1958
Comments
Should already work (UI part), did QA checked it? |
Blocked until guests can receive presence shares. |
The relevant server side ticket hippware/wocky#1325 has been deployed to Staging with version |
A radius represents 'geofence' type of the bot. Presence CTA unsubscribes owner from presence notifications but doesn’t change type of the bot.
Beng, correct me if I’m wrong...
cc @zavreb
… On 22 Mar 2018, at 20:48, mstidham ***@***.***> wrote:
Bot Owner removes presence:
Radius is still visible on bot profile for bot owner.
<https://user-images.githubusercontent.com/20051373/37794198-cdd7033e-2dde-11e8-9e64-ce724d5d196f.PNG>
Who's Here, Visitors CTA continue to display for guest.
<https://user-images.githubusercontent.com/20051373/37794437-712b7f92-2ddf-11e8-89b5-3f485b953931.jpeg>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1958 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQpcbKUlzipVKhFUEVY4gECk--bBIAQks5tg__5gaJpZM4ShFo_>.
|
Maybe we need to define UI specs more precisely... And we should collect them into wiki, not just various tickets... |
Oh, just read that "Bot Owner removes Presence: Presence feature turned off for ALL", sorry I missed it , but it looks very strange and contradicts with our past discussion - that owner could unsubscribe from own bot and other users still will be able to check others presence... |
@mstidham I've just checked and disabled "See Who's Here", and Radius is disappeared for everybody, as expected... |
Thanks @aksonov, the wording is going to be a bit confusing to me for a bit. |
I'm confused too...are we saying this is working according to the original specs in this ticket? |
Wait guys, please hold on this. |
Implementation is correct. Bot Owner toggles "Presence: OFF", the bot has the presence feature turned off after the bot owner taps Saves Changes This means that if the user toggles the Geofence feature off it no longer becomes a Geofence bot. If a owner disables Current implementation is correct cc: @mstidham (cc: @aksonov, @southerneer) |
Bug: User disabled
@southerneer / @aksonov is this is a difficult requirement? |
"Discard changes" doesn't apply for any bot changes. That's a separate ticket. |
Ok thanks, going to continue moving this ticket in the flow then. cc: @thescurry |
Verified on Production Version: 2.6.7 |
Note: This is different from
disabled presence
, this is when presence feature is turned off entirely.Guest disables footprint CTA: Presence feature turned off for Guest:
ON
)Bot Owner removes Presence: Presence feature turned off for ALL
OFF
", the bot has the presence feature turned off after the bot owner tapsSaves Changes
Guests
becomeSubcribers
onlyguests
no longer receives presence related push notificationsThe text was updated successfully, but these errors were encountered: