You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the "new love" script somehow stops tracking after using a new account.
I just logged in to a public plan and on my next visit to my Quick Love page, it showed all planlove as new. I didn't even visit the "Quick Love" page of the other plan, just logged in and posted.
I'm not sure what to propose immediately as a solution, but it was definitely a bummer.
The text was updated successfully, but these errors were encountered:
Thanks for reporting! Not quite sure what's going on here, though. I tried to reproduce (in Safari) by logging out of my plan, logging into a public plan, logging back into my plan, and checking my quicklove, but I couldn't get the same problem to happen (even after visiting a public plan's quicklove).
The two possibilities that come to mind are either somehow your localStorage was cleared or somehow the script started looking for quicklove for the public plan instead of you (although it should only do that if the quicklove user hasn't been set; see https://github.com/niqjohnson/PlansPlus/blob/master/plansplus.user.js#L114).
Let me know if you encounter the problem again and I'll keep digging.
Weird. I'll see if I can reproduce it. I'm pretty darn careful to not clear
my cache and localStorage, so I don't think that's it but you never now.
This was Chrome Win 8.1.
It seems that the "new love" script somehow stops tracking after using a new account.
I just logged in to a public plan and on my next visit to my Quick Love page, it showed all planlove as new. I didn't even visit the "Quick Love" page of the other plan, just logged in and posted.
I'm not sure what to propose immediately as a solution, but it was definitely a bummer.
The text was updated successfully, but these errors were encountered: