-
Notifications
You must be signed in to change notification settings - Fork 319
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
Removal Issue #126
Comments
Comment editing and moderation is my next thing to tackle. |
Btw I received my first "toobusy-js" status message... so it appears to be working. |
Assigned to @sizzlemctwizzle since he took this on with above commits... needs a bit additional tlc to finish this up including retesting. (hint, hint ;) |
Rolled back production to last stable master HEAD of d64f754 to not block moderation as well as potential abuse with mentioned line notes on commits... resync to master on production when finished with this issue. :) |
btw this is BLOCKING from my standpoint e.g. I won't do any merges/upvotes until resolved with either a rollback on dev source here or fixes with a close. (and retesting of course) Do we have something similar to a |
Sorry I was too tired last night to test my changes. Probably shouldn't have deployed my changes, but I figured I might get lucky. |
Well besides those issues I'm thrilled that you know how to do this so easily... I started tinkering yesterday with this and failed miserably. Manually is cumbersome and I do appreciate you taking the time... just needed testing before deployment to iron out the kinks... I was quite tired too. :) |
* `./libs/remove.js` should do it all for this issue * `./controllers/discussion.js` shouldn't be doing a "post" job cleanup e.g. should be done in remove.js as a "pre" job cleanup Refs with line notes: * OpenUserJS@a156657 * OpenUserJS@1a9933c
Revert changes at try for #126 Auto-merge
@sizzlemctwizzle I'm still not ready to tinker with this more even with your additional assistance but I do have a little better understanding of how you designed it initially and how I do it manually... so might have a solution in the near future to combine the two... left some notes in the (revert) commit on my current thoughts. |
I probably won't be able to work on it for a while.
|
* This will probably be needed for ordered and decrementing mass removals down the line... and uncovered a few logic issues * Add some TODOs ... since this is a work in progress guestimating what should be done... final may be slightly different * Some STYLEGUIDE.md conformance * Add an error handler in `getFlaggedListForContent`... this will tell us if a flag has been found but no user in the non-long-term... Post OpenUserJS#643 fix in Moderation eyeball **NOTES** * Tested mostly on dev and some on local pro Applies to OpenUserJS#126, OpenUserJS#93 and trounces madly upon OpenUserJS#262 (comment) ... sawwy but tiz a boog.
* Show the actual model name in stderr * Elaborated more on line notes Applies to OpenUserJS#126 and trounces profoundly upon OpenUserJS#262 (comment)OpenUserJS#262 (comment)
* This doesn't fix the Discussion count yet but I will do that manually when needed until the TODO's are put in... saves me a query, and kill of Discussion/Comment and I'll just do a lookup of the Discussion id when needed. Cherry picked from OpenUserJS@a156657 Applies to OpenUserJS#126
* Calling this removal reparse for lack of better naming * Fix bug on User removal when there is no other content * Fill in the basic construct for Comment and Discussion removal... designed so the top portion can be moved around to a separate function if needed... yes it might need some compression but not until the remaining switch cases are filled in to see what can code be reused. * Removal of an owned discussion "orphans" others comment however it's not fatal and keeps their comments around * When comment editing comes around... will need to call remove Comment and check if the Discussion needs to be removed as well. * Tested orphans to ensure they didn't get reassigned if a topic is resurrected. * May need a little tweaking on User Comments list with breadcrumbs but that is UI specific. * Very literal coding here... using `null` in all *async* fields... I'm aware of `undefined` but lessens the readability and contributor understanding... negligible impact * Watching for VPS timing issue with potential multiple comments... and it has been attempted on pro already by others... added a TODO for this and will watch stderr **NOTES** * Keeping OpenUserJS#126 open until all removal issues are with minimal coverage Applies to OpenUserJS#126 ... shamelessly treads on OpenUserJS#262 (comment)
* When promoting/demoting a User future flagging/unflagging can wreak havoc on critical *(relative)* flags properties. * Project bump since requires a bit of migration * Needs followup testing with OpenUserJS#1109 Applies to OpenUserJS#126 and post OpenUserJS#641
Removed the this author from their homepage and traces seem to be still present on the site. See in the garage with this h2.comment-title.
I've manually trumped that discussion and 2 malware script comments from production but the issue still remains on account removal to the graveyard.
The text was updated successfully, but these errors were encountered: