Mike's Nightly Updates

-It appears their ranks were set to Applied Manually to prevent spamming from the issue that was already fixed. Asked the client to confirm for more testing. After client removed Applied Manually, users are receiving new ranks upon login. Filed an issue to make the description more explicit: https://vanilla.freshdesk.com/a/tickets/89492

-Tested & Filed: https://vanilla.freshdesk.com/a/tickets/88687

-Added a quick note and asked for clarification: https://vanilla.freshdesk.com/a/tickets/89427

-Linked: https://vanilla.freshdesk.com/a/tickets/89489

-Did some basic reconaissance and left a note for Elize: https://vanilla.freshdesk.com/a/tickets/89506

-Investigated, discovered the missing string in Transifex, & filed: https://vanilla.freshdesk.com/a/tickets/89748

-Ran a quick test on the fix that was deployed to staging: https://vanilla.freshdesk.com/a/tickets/89027

-Created some test discussions and comments without issue in various places, including where she posted. I imagine the problem has ceased; asked for confirmation. Filed an ops ticket with the RayID for investigation: https://vanilla.freshdesk.com/a/tickets/89769

-Checked if this was in the theme editor yet; applied manually: https://vanilla.freshdesk.com/a/tickets/90024

-Extensive testing and filed. Asked Max a followup question: https://vanilla.freshdesk.com/a/tickets/90010

-Client seems to think this is urgent. Inquired as to why. Attempting to placate the client’s -seemingly unwarranted- fears: https://vanilla.freshdesk.com/a/tickets/89918

-Added a quick note: https://vanilla.freshdesk.com/a/tickets/90014

-Quick explanation for enabling API tokens: https://vanilla.freshdesk.com/a/tickets/89924

-Quick note from my investigation: https://vanilla.freshdesk.com/a/tickets/90022

-Tested & Filed bug: https://vanilla.freshdesk.com/a/tickets/90202

-Investigated/tested different approaches. Postulated the best course of action and asked other agents about current expected bahavior: https://vanilla.freshdesk.com/a/tickets/90188

-Investigated the anomalies, but this could be easily explained away; asked for some more info from the client: https://vanilla.freshdesk.com/a/tickets/90182

-Tested & Filed: https://vanilla.freshdesk.com/a/tickets/90183

-Created a quick export and sent it securely: https://vanilla.freshdesk.com/a/tickets/90205

-Filed chore: https://vanilla.freshdesk.com/a/tickets/90481

-Tested & Filed: https://vanilla.freshdesk.com/a/tickets/90474

-Examined the colors and different sections, but it looks correct. Asked for clarification: https://vanilla.freshdesk.com/a/tickets/90496

-Big write-up on alternative solutions for member-restricted messages: https://vanilla.freshdesk.com/a/tickets/90497

-Figured out the cause with the client's help and filed: https://vanilla.freshdesk.com/a/tickets/90494

-Tested all the fields in the upcoming events box and proposed a couple fixes for the devs: https://vanilla.freshdesk.com/a/tickets/90482

-Went to take some screenshots for an explanation and discovered the permissions have already been changed. Notified the client as such: https://vanilla.freshdesk.com/a/tickets/90657

-Explained more things and linked previously reported bug: https://vanilla.freshdesk.com/a/tickets/90578

-Explained how to correct the permissions: https://vanilla.freshdesk.com/a/tickets/90657

-Checked and updated client: https://vanilla.freshdesk.com/a/tickets/90353

-Explained a quick fix for the user, but the client just seems to be complaining for complaining's sake now: https://vanilla.freshdesk.com/a/tickets/90578

-Reopened and updated: https://github.com/vanilla/support/issues/3723

-Also couldn't find the user on 3 different sites; sent out a list of followup questions: https://vanilla.freshdesk.com/a/tickets/91047

-Asked for some info. Delayed the client and asked Cam to find some info on the Bulk Import client: https://vanilla.freshdesk.com/a/tickets/90657

-Investigated and worked with ops to fix: https://vanilla.freshdesk.com/a/tickets/91075

-Enabled Event Logger and asked client to attempt the sso login again: https://vanilla.freshdesk.com/a/tickets/91047

-Tested & Filed: https://vanilla.freshdesk.com/a/tickets/91080

-Tested & Filed: https://vanilla.freshdesk.com/a/tickets/91063

-Ran category counts on MOSC: https://vanilla.freshdesk.com/a/tickets/91258

-Did some extra testing and added findings to the issue: https://vanilla.freshdesk.com/a/tickets/90546

-Asked Olivier and Andrew about general practices/possibilities. Updated ticket with new info: https://vanilla.freshdesk.com/a/tickets/90059\

-Reassured the customer that we're looking into the cause of this unexpected change: https://vanilla.freshdesk.com/a/tickets/91182

-Worked with Adam to resolve the problem, tested, and notified the client. Also sent over a groups export Adam included so it'll be easier for them: https://vanilla.freshdesk.com/a/tickets/90187

-Reassured the client that it's likely nothing to worry about, notified Paul, and put it in the Security folder: https://vanilla.freshdesk.com/a/tickets/91266

-Issue was temporarily closed. Reopened the child ticket and set as Filed: https://vanilla.freshdesk.com/a/tickets/88822

-Quick note for Danni: https://github.com/vanilla/support/issues/3512

-Answered a question for David: https://github.com/vanilla/support/issues/3763

-Asked for user emails to send to dev team: https://vanilla.freshdesk.com/a/tickets/91491

-Filed RCA Request: https://vanilla.freshdesk.com/a/tickets/91471

-Couldn't find export issue so I created a shareable link and sent: https://vanilla.freshdesk.com/a/tickets/91458

-Site seems fine; cloudflare not showing any issues. Asked for details: https://vanilla.freshdesk.com/a/tickets/91494

-Tested Site and updated client: https://vanilla.freshdesk.com/a/tickets/90496

-Asked Flynn and Shauna about backporting to 003 for Oracle: https://github.com/vanilla/support/issues/3771

-Sent the client a quick, but awful manual approach; asked Laura for some advice: https://vanilla.freshdesk.com/a/tickets/91456

-Tested and diagnosed what appears to be a big API issue. Filed: https://vanilla.freshdesk.com/a/tickets/91441

-Tested recent fix and notified Brendan: https://vanilla.freshdesk.com/a/tickets/91445

-Did some more testing and certified it is working. Updated client site and notified client: https://vanilla.freshdesk.com/a/tickets/91056

-Clarified the situation for Dani: https://github.com/vanilla/support/issues/3512

-Completed the Marketing survey.

-Responded to the conversation with Cam and Val about the removal of the $oauth2 SmartID feature.

-According to Olivier the export should be deleted within 24 hours; requested to forestall the deletion. Attempted to download the export just in case, but the creds are bad; noted in issue. Also emailed Ops and slacked the issue owners. Olivier made a backup, all is well: https://vanilla.freshdesk.com/a/tickets/83762

-Replicated the problem; asking for clarification on the specifics from the client: https://vanilla.freshdesk.com/a/tickets/91635

-Tested & Filed: https://vanilla.freshdesk.com/a/tickets/91641

-Updated client: https://vanilla.freshdesk.com/a/tickets/91250

-Slacked PK to se if he could clarify: https://vanilla.freshdesk.com/a/tickets/91570

-Asked some questions to get this diagnostic started: https://vanilla.freshdesk.com/a/tickets/91630

-Fixed by adding name attribute to config: https://vanilla.freshdesk.com/a/tickets/91632

-Asked Andrew to check-in with Sussan to see if this has been completed: https://vanilla.freshdesk.com/a/tickets/91491

-Sent user list export: https://vanilla.freshdesk.com/a/tickets/91915

-Tested & Filed: https://vanilla.freshdesk.com/a/tickets/91875

-Reopened and updated GH issue: https://vanilla.freshdesk.com/a/tickets/91802

-Searched, attempted to use Kibana, but it's unresponsive. Filed: https://vanilla.freshdesk.com/a/tickets/91882

-Asked client to resend without secure info for the moment: https://vanilla.freshdesk.com/a/tickets/91932

-Filed and asked what the client is worried about here: https://vanilla.freshdesk.com/a/tickets/91914

-Double-checked option was there and relyed info to Rhys: https://vanilla.freshdesk.com/a/tickets/91720

-Asked client for an update on retrieving the export: https://vanilla.freshdesk.com/a/tickets/83762

-Double-checked fix on client site and notified CSM: https://vanilla.freshdesk.com/a/tickets/91724

-Updated client and closed: https://vanilla.freshdesk.com/a/tickets/89911

-Ran utility update to correct db issue and disabled plugin: https://vanilla.freshdesk.com/a/tickets/92122

-Tested & Filed. Sent some css to hide the button temporarily: https://vanilla.freshdesk.com/a/tickets/92124

-Enabled the ideation plugin: https://vanilla.freshdesk.com/a/tickets/93057

-Subscription tested fine for me; asked to try for them and recommended a couple fixes. Subscribed the user myself and asked if they'd like to continue diagnosing: https://vanilla.freshdesk.com/a/tickets/91920

-Checked the comments and everything seems kosher on the user's part; I'm thinking it was a simple false positive from the spambot. Instructed the user in best-practices for using the verified status: https://vanilla.freshdesk.com/a/tickets/93046

-Tested, discovered what's happening, but filed the Why: https://vanilla.freshdesk.com/a/tickets/93050

-Ran comms for Tim while he was working the re-indexing. Filed meeting request: https://vanilla.freshdesk.com/a/tickets/93054

-Tested, hunted through the patch, and filed: https://vanilla.freshdesk.com/a/tickets/89949

-Updated client with current info and updated Paul to get a final answer: https://vanilla.freshdesk.com/a/tickets/90545

-Gave a more detailed explanation of the universal comments unique identifier and offered to give a "best" approach: https://vanilla.freshdesk.com/a/tickets/93171

-Inquired about an old GH issue that's gone stale: https://vanilla.freshdesk.com/a/tickets/93250

-Looked through our documentation and GH, but couldn't find an answer. Asked for specifics so we can test: https://vanilla.freshdesk.com/a/tickets/93254

-Filed and put in dev-support. Discovered the related GH requests and explained the situation to the devs. Also tagged Richard: https://vanilla.freshdesk.com/a/tickets/93256

-Tested & Filed: https://vanilla.freshdesk.com/a/tickets/93254

-Updated issue: https://github.com/vanillaforums/exports/issues/744

-Updated Client: https://vanilla.freshdesk.com/a/tickets/90386

-Diagnosed and worked out it was a false alarm where an admin was having caching issues: https://vanilla.freshdesk.com/a/tickets/93448

-Created Ops request to remove repo users: https://vanilla.freshdesk.com/a/tickets/91491

-Checked in, but it looks like a browser issue or a user error: https://vanilla.freshdesk.com/a/tickets/93455

-Upgrade priority to High since it's a deploy bug...also a launch blocker for Family Search: https://github.com/vanilla/support/issues/3911

-Explained how to enable Banner via Advanced Settings variables: https://vanilla.freshdesk.com/a/tickets/93455

-Checked the chinese locale and listed which translations we still need: https://vanilla.freshdesk.com/a/tickets/91504

-Created several examples API queries that should satisfy their requirements: https://vanilla.freshdesk.com/a/tickets/93340

-Heard back from Tim and notified client of completion: https://vanilla.freshdesk.com/a/tickets/91491