Is there a fast way to delete all the achievements I've created for my Facebook app? (I got hundreds..)
No, you need to delete each one individually
Related
At the bottom of each issue page there is a History of changes. Some of those are autogenerated by external tools, or by a user that made a mistake, so it would be useful to be able to delete them. Is this possible?
I tried in the standard form and also in the editable form after clicking "Update". I also tried with History updates made with my own user
I am used to do this from the database backend, there's a table which can be edited/emptied. If that helps in your use case.
PA
Yeah, you need to truncate the following tables: journals, journal_details. This way you will not destroy any other content. Just do not delete the tables.
PA
I am looking for a way how to delete an object and create new one (in new model) at the same time. I mean I want to have a base of deleted elements. I got table with delete button within form (DeleteView). Thank you for answers.
Try to override delete method
https://docs.djangoproject.com/en/2.1/topics/db/models/#overriding-model-methods
or use singnals, but I would recommend first option.
I am trying to add new actions to the right click context menu when you select a file or many files. I am writing a program in C++ which contains the functionality that I want to trigger.
As far as I know I have to add new entries to the registers when installing my program and also, I have to use COM(here I got completely lost).
Is there a straightforward way of doing this?
As already suggested by #Igor Tandetnik you can do almost everything you want with Registry entries.
https://msdn.microsoft.com/en-us/library/windows/desktop/cc144169.aspx
Lets say I have a FB app I've created, and for whatever reason the server code for the app is responsible for posting stories to the app user's wall (using a token).
Now let's say we want to take down that post at a later date - easy, right? Because the app created the post, it owns it, and using the ID it received originally it can take that post down. (I presume the ID I get back is actually an "object id" referring to my content, rather than specifically to the post on the user's wall - correct?)
Here's the thing though. What if one or more friends of the user shared that story to their own wall - what if this happened a number of times, spreading through the friend relationship tree further and further. Does my app still have the power to remove all of these posts, because it created the original post?
Additionally, what if the original user deleted the post themselves from their wall, but not until it had been shared by his/her friends? Would this have the same effect (delete everywhere), or would it only be that one specific post being removed? Would my app get an error when it tried to delete the post itself if the post had already been deleted by the user?
The reason I ask is because, if my app deleted the original post that it made to the user's wall, I would want all of the shared posts or likes to also be deleted, no matter where they were down the friend chain. I don't want to delete my original post and assume all is well, only to discover that because it was shared several times down the chain that it is still visible somewhere.
In case it's relevant, the "post" my app will make would require a custom image and a specific return URL - I tried the /user_id/links graph API and it didnt work (there's a bug with it). So I'd be most likely using /user_id/feed to make the post.
if my app deleted the original post that it made to the user's wall, would all of the shared posts also be deleted from everywhere?
Yes
What if the original user deleted the post themselves from their wall, but not until it had been shared by his/her friends? Would this have the same effect?
Yes
How did I know this? I tested it.
I posted a status update to a test user Betty
Then had three other test users share it one after the other
So Tom shared it > Joe shared what Tom shared > Patricia shared what Joe shared
Then for completeness I had Betty share it again
On delete, all posts are gone from all test users, including the re-share Betty made.
As long as the user shares via the action link all subsequent shares will be deleted if the original is deleted.
But if the user manually copies it or saves a photo then re-uploads then no.
In terms of documentation, you have to bite bullet and realize there is no comprehensive documentation for Facebook and not all Facebook engineers know all features about Facebook. There are many items that haven't been able to get a word from Facebook about, and that's when I test things. That's what developers do. Create new test paths, do coverages, make branches and arrive at a conclusion
If you post a link on your user's wall, the shared content cannot be deleted
where as if you post a photo, it will be deleted
If you delete a post (whether it was a link, status update, photo etc), deleting will delete all Likes and Comments from the Object, as well as the related newsfeeds from anyone connected to the object (e.g. it will remove things like Friend has commented on Someone's post etc).
It won't, however, delete any re-shares of that post from users' timeline.
I'm confused about the correct way to reset or clear the data associated with a QAbstractItemModel.
I'm writing an application in which the user can "start over" with a new set of data (empty, or small).
Should I be deleting the old model when the user makes this request? Or should I leave the model alone and just remove all of the rows?
Regards,
Dan O
Generally I would prefer to have the model react to changes and take the necessary actions to update it's view (indirectly ofcourse). However, programming models can be (=is) a PITA, so I would probably look through the fingers if I was reviewing code that created a new model and deleted the old one. Only do this if you are sure the user only will delete all rows. If the user may delete items from the model incrementally you're probably best off implementing removal properly in the first place...
Also, ModelTest might help you discover problems with your Qt models.
If the user is truly starting over with a new set of data, then it makes sense to me to simply delete the old model and create a new one. Simple, effective, and it matches up to what the user is doing.
I don't know which way it truly "better" but removing all the rows can be a rather simple function something like:
void MyModel::Clear(void)
{
// remove all data from internal data structures
...
// Call QAbstractItemModel::reset to ensure any views know that everything has changed.
reset();
}