How to remove old json data? Answered
Does memberstack store JSON cookies / cache locally? And if so is there anyway to overrule that? I’ve changed the json in the dashboard but the front end keeps loading old json data that doesn’t even exist anymore with the getMemberJSON function
Even logging member in and out, still getting old json data
https://memberstack.slack.com/files/U0400M2PMHU/F053EEF98R3/video_clip__2023-04-17_11_21_06_.mov (Sorry for not using loom lol)
Bleurgh:doop was the first JSON I had there. And it keeps loading. Here is the code that is supposed to bring it in. Looks fine to me
Comments
17 comments
It doesn't store locally to my knowledge - I Haven't seen this before. Trying to figure out what the issue is now
I searched applications: cookies and local storage but didn’t see any JSON data there so I think you’re right that ms doesn’t store it. Weird af
could you try this:
This way we could figure out if clearing the cache does the trick - in which case, it must be storing locally somehow, someway, somewhere
🫠 Gonna have to sign back into all services but ok haha
you should just be able to clear data only for this one site
Cleared all, was faster. Still getting blerugh doop
Absolute madness !
ah okay, and in that case it seems like its not updating anywhere 🤔 from another test account is the same thing happening?
I can try the other test account. Gimme a minute
Wtf getting bleurgh doop on that one too
Didn’t even have any JSON. It seems blerugh doop is like associated with the entire account/website rather than a member. Not sure how that’s possible
Maybe a test account bug?
exactly what I'm thinking, I'm trying to replicate on another test project
Also, where was bleurgh doop updated from? Back end manually just like you showed in that video, or elsewhere?
Do I need memberId inside the () at the end of function getMemberJSON()?
I added it manually in the beginning for Edward.goin@gmail.com to test if I could replace even if a key didn’t match in a key value pair
The weird thing is updating memberjson appears to work fine. It’s the read
Adding memberId inside () didn’t help
try to comment out that return line 212
Also, could you send me this code perhaps so i can replicate a but more accurate
first ill try commenting out 212
ok still bluergh doop with 212 commented out. ill paste the relevant code.
and here’s the console log
thanks! Checking now
one issue, could you send it to me as a code block? When you send it as a slack message it converts a bunch of characters and makes it not work
in the formatting options on slack, just hit code block then paste
note i just checked the same on firefox rather than chrome. still getting the bleurgh doop
so its DEFINITELY not the browser.
you want me to resend the code in a code snippet. Here it is:
persisting across multiple members, multiple browsers, and a full cache clear… no hard-coded instances of bleurgh or doop in my code… it HAS to be a memberstack bug right?
oh fuck this is embarrassing. i think i found the bleurgh doop. your original question.
exactly what I’m thinking, I’m trying to replicate on another test project
Also, where was bleurgh doop updated from? Back end manually just like you showed in that video, or elsewhere?
— i think i see it in a legacy HTML code block. im gonna delete it. if that fixes it, i owed you the biggest apology for wasting your time
it was inserted manually on the dashboard, i wasn’t wrong about that. but i may have also done the other part too
Hopefully that does fix it!! No worries if that's the case, if it ever happens again, I know the first thing to investigate 😎
and thats why you have to finish a task on a day, if u sleep on it you forget these little bastards you leave behind
yeah its working now. im such a fuckface. sorry if i ruined your morning Julian.
thank you so much for your help 😞
Oh ive been there before, don't worry at all 🤣 No problem at all, I'm just glad we got it figured out 🙏 if there's anything else, just let me know! Don't feel bad about it, i totally would have forgot about that too
Please sign in to leave a comment.