Duplicate After saving a template page refresh goes back to top of page

[Mr Lucky]

Affected version

2.3.0 beta 1

Previous tom 2.3.0 you could make an edit way down the page and then save (without exiting). The page would refresh but still display at the position it was at. Now it goes back to the top.

 

[willl]

This one has been driving me nuts while I work to update our styles for 2.3.

 

[Osman]

Yes, it is really annoying. This issue has been reported.

Fixed Thread 'Saving template change does not work'

Mar 19, 2024

After editing a template, the page is refreshed every time after the save action. However, in XF 2.2.x versions, the changes were shown as saved.

• Osman
• Replies: 1
• Forum: Resolved bug reports

 

[Mr Lucky]

I saw that but it didn't seem to be the same thing. In this case saving the template change does work, just that it goes back to top afterwards.

 

[Jeremy P]

It's a bit confusing from the wording, but that's the same issue.

 

[Mr Lucky]

It's a bit confusing from the wording, but that's the same issue.

Now I am confused as it's actually not the same issue and is still happening in beta 2. The template saves but instead of staying at the same line as in 2.2, the page now shows at line 1.

 

[Jeremy P]

That’s right, that issue is about form edits not saving over AJAX, which causes the page to reload completely. The refresh will cause the scroll position and undo history to be lost.

Unless I’m misunderstanding this issue?

 

[Mr Lucky]

Unless I’m misunderstanding this issue?

No, obviously I'm misunderstanding or not able to explain because I still have the issue I'm talking about in beta 2

The supposed duplicate bug says saving template changes doesn't work. I am finding it does work, just that it goes back to the top.

 

[Jeremy P]

The wording is a bit misleading, it does not work [as intended, as the changes are not saved over AJAX].

 

[Mr Lucky]

Not to worry, it's probably just my age and a touch of dementia not understanding, or not understanding why it says resolved when the issue still happens. Or does that mean it is resolved in the next beta?

 

[Jeremy P]

It’s confirmed, not resolved. A fix is still outstanding.

 

[Mr Lucky]

It’s confirmed, not resolved. A fix is still outstanding.

Ah, OK. Just that this is in the resolved bug reports forum. I think that is what confused me.