Can't remove "mobile theme"

English Forums Feedback
#1

Hi,

I am new to the forums.

While playing with settings I wanted to try out the different themes. One of them was the “mobile” theme.

However after choosing it I can’t find a way to revert to the devault one - neither the URL of the Settings page works, nor the “Full Site” link in the footer (https://forums.opensuse.org/forum/?styleid=48). The later gives a 404 page.

Can a mod/admin help to please reset my setting to the default theme please?

#2

If you are using Chrome/Chromium/Vivaldi, open this in your URL bar:

chrome://settings/cookies/detail?site=forums.opensuse.org&search=cookie

Then either remove all (which will remove cookies from this site and will require you to relogin) or remove the bb_userstyleid cookie parameter.

#3

I always use incognito mode. Restarting the browser to remove the cookies and login again didn’t change anything. I am still in the “mobile theme” and “Full Site” is a 404 page.

Also checking browser console shows no bb_userstyleid cookie.

#4

After some digging into the ugly obfuscated JavaScript of the site I found a workaround:

  1. Open https://forums.opensuse.org/forum.php?styleid=48 (this will open the page with the opensuse-CMS style)
  2. Edit settings to set the opensuse-CMS style as default

Solved :slight_smile:

#5

Nice you solved it. And thanks for reportng back. You never know if someone else experiences the same.

#6

Yes, that’s why I shared my findings.
In any case this sounds like a bug (at least the 404 page). Should that be reported to bugzilla?

#7

Hi
You could, but unlikely to get far :wink: See the ‘contact us’ link down the bottom of the page, use that instead…

#8

I asked for help on this through the ‘contact us’ link 4 days ago. No reply.
Considering that a bug report is also unlikely to work (I wonder why) - both things are quite unfortunate.

#9

Hi
The forums are in maintenance mode since the sale of SUSE, Microfocus are just supporting the hardware and software until we move off to a new platform. So it’s likely on the low priority list and in this case a fix would be unlikely…

#10

I see.
Thanks for the extra info :slight_smile: