-
-
Notifications
You must be signed in to change notification settings - Fork 178
Stuck on post where neither "deleting" nor "hiding" was an option #22
Comments
I'm going to close this again, since I am not sure anymore this is what actually happened and I might have jumped the gun here. |
I think this is a real thing, but it's hard to reproduce. I think Facebook has removed certain features over the years so things are a bit inconsistent. |
Reopening since I think it might be a real issue but it's hard to reproduce. |
I'm consistently stuck on this step, and the situation is this: A friend posted a picture on another friends' wall in which I was tagged. The option presented in the context menu is to "Remove Tag". Edit: it's unclear whether or not this is the only case, but I untagged myself and ran the script again to continue on as normal. |
Found another post with it, the parameter for selenium is:
|
Thanks, I think I can add that, even if I can't test it
…On Mon, May 27, 2019, 2:05 PM Joseph Bennett ***@***.***> wrote:
Found another post with it: the parameter for selenium is:
data-feed-option-name="UNTAG"
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#22?email_source=notifications&email_token=AAC4L3YQXYTLXFEIXUM6OV3PXQPIFA5CNFSM4HOWWKP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKJRKY#issuecomment-496277675>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAC4L37Q3DKCENG6RHCF7W3PXQPIFANCNFSM4HOWWKPQ>
.
|
It should just need an additional case here to handle it DeleteFB/deletefb/tools/wall.py Lines 24 to 27 in 565e01f
|
#44 may solve this Could someone test? @jsmbennett @Neugierdsnase |
Should be fixed now |
Maybe related to #17. The program seems to have been stuck on a post from 2013 where neither "deleting" nor "hiding" was an option. I manually "untagged" me from the post/photo and restarted the program, which worked fine, but this might want to be considered fixing as a future enhancement.
The text was updated successfully, but these errors were encountered: