Page MenuHomePhabricator

Vector 2022 is unexpectedly re-appearing after switching to legacy Vector
Closed, ResolvedPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

  • Step 1: Have Twinkle on (idk if it is this)
  • Step 2: Switch the old look on
  • Step 3: Visit any Wikipedia page

What happens?:
Wikipedia keeps changing the look back to the new look. Even when i turn on the old look, it still changes back to the new look most of the time. Can anyone help?
I suspect Twinkle may have something to do with it, but otherwise i just need help to fix this.

What should have happened instead?:
It should have just kept the old look.

Software version (skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):
My browser is Microsoft Edge.

Event Timeline

I assume you're clicking the "Switch back to old look" link? If so, make sure you select Vector legacy (2010) and save your preferences.

If Vector 2022 is still re-appearing after doing so, try turning off Twinkle/any other userscripts and gadgets before re-enabling legacy Vector.

Remagoxer renamed this task from Look problem to Vector 2022 is unexpectedly re-appearing after switching to legacy Vector .Jan 18 2023, 4:18 PM

The change is gradually taking effect between 15:30 and 16:30 UTC. During this time, individual pages do appear in the new skin or the old skin, as we are deploying in multiple stages. Since we are currently rolling out in stages in order to minimize server load, we are updating the skin default in four stages, which is affecting local preferences. Local preferences will work once again as expected when the deployment is completed, in about 20 minutes.

The change is gradually taking effect between 15:30 and 16:30 UTC. During this time, individual pages do appear in the new skin or the old skin, as we are deploying in multiple stages. Since we are currently rolling out in stages in order to minimize server load, we are updating the skin default in four stages, which is affecting local preferences. Local preferences will work once again as expected when the deployment is completed, in about 20 minutes.

Thanks.