New "Feature"?

[SmilingLez]

Just started happening when I like posts

 

[ToPleaseHim]

That’s odd. I haven’t seen that on my end at all.

 

[ICantLeafYou]

I'm also not seeing it.

 

[barefootgirl69]

Are you using modern or classic style?

 

[SmilingLez]

Are you using modern or classic style?

The default

 

[SmilingLez]

Another new "feature"?

 

[barefootgirl69]

Okay, you're in the modern style.
I think the rest of us are classic, and it's not happening in that style.

The "oops" happens a lot and I just need to refresh. It's a PITA.

 

[SmilingLez]

Okay, you're in the modern style.
I think the rest of us are classic, and it's not happening in that style.

The "oops" happens a lot and I just need to refresh. It's a PITA.

Can you explain the difference in the two styles? I figured the default was the most stable, so I never changed. I am using an Android phone. TIA

 

[Wonderer67]

I had this happen to me a few days ago. I closed out all my browsers on my phone and then got out of the web browser app.

Once I restarted it, it was all good.

 

[barefootgirl69]

I'm on my android, too.

The classic is what it was before "The Hullabaloo" when everything changed.

Here's a pic

 

[ToPleaseHim]

Yeah, I think the majority of us who have been here more than a few years use the classic style for Lit. I don’t think I’d ever be able to adjust to the modern look.

#BackInMyDay

 

[TheWritingGroup]

I "wowed" the threadstarter with no confirmation. Firefox.

 

[SmilingLez]

Just started happening when I like a posts

View attachment 2679060

It still happening randomly. Four times now. Using latest version of Chrome on my Android phone.

 

[BeechLeaf]

I've never seen that confirmation request. I've just liked your initial post, and again not seen it. I'm on default (new) view.

The oops message appears sporadically. Just refreshing always fixes it. If it happens when you're posting text, make sure you copy it all before refreshing it, because the refresh usually loses some of what you've typed.

 

[anthrodisiac]

I've never seen that confirmation request. I've just liked your initial post, and again not seen it. I'm on default (new) view.

The oops message appears sporadically. Just refreshing always fixes it. If it happens when you're posting text, make sure you copy it all before refreshing it, because the refresh usually loses some of what you've typed.

I'm glad the oops isn't just me. It happens if the page gets left open long enough, looks like an authentication issue if you open the console to look. I'll have to check next time to verify, but iirc, it had something to do with the token no longer being valid or something to that effect.

 

[BeechLeaf]

Often it's seemed like it's associated with a delay, like when I'm writing a longish comment, but I have sometimes had it on actions that shouldn't have any delay.

 

[SmilingLez]

Just started happening when I like posts

View attachment 2679060

This has not happened again, so it is a random thingamabob. Glad I was able to get a screenshot for proof.

That would be a cool feature to have in the forum after clicking Post reply. It would make certain people think before they post

 

[Voboy]

I'm glad the oops isn't just me. It happens if the page gets left open long enough, looks like an authentication issue if you open the console to look. I'll have to check next time to verify, but iirc, it had something to do with the token no longer being valid or something to that effect.

Often it's seemed like it's associated with a delay, like when I'm writing a longish comment, but I have sometimes had it on actions that shouldn't have any delay.

I think it happens if something you're watching or replying to gets updated while you're typing. But I'm unsure.

Regardless, @BeechLeaf is absolutely right: cut out whatever you were typing before you refresh.

 

[anthrodisiac]

Okay, so it looks like there's a certain point where you lose authorization for whatever reason, and a refresh will fix that up. The network response and console logs are vague, it's a simple "PHP: Unauthorizated" message, no further data. But it does occur on a GET request. I've noticed it tends to happen the longer the page stays open, so I wonder if it's a response to inactivity, or just the longer the page is open, the more likely it is that this bug occurs (probably the latter, since I've also seen it happen when I'm just typing long responses over a period of time.

 

[Voboy]

...just the longer the page is open, the more likely it is that this bug occurs (probably the latter, since I've also seen it happen when I'm just typing long responses over a period of time.

This fits my own observations.