Problem with site

[Max e^{i pi}]

I can't seem to get out of the mobile version on the site.
I did everything I could from my end: flushed cache and cookies, manually adjusted my user agent and tried different browsers.
Must be something server-side.

[matweller]

It does that periodically and I'm not sure why. It doesn't seem to happen in conjunction with anything I do to it, but I don't know if one of the other contributors has more insight. I'll ask around...

[Max e^{i pi}]

It's a Wordpress site, yes?
Pass it forward to their tech support. From this end it looks like a broken script. I think the backend of Wordpress is php, unfortunately my php is rather rudimentary.
And I no longer am experiencing this problem...

[matweller]

Well, I just made the unilateral decision to install the latest updates and see if that helps. It's not really my place, so if there's a new producer next week, it's been real.

[Max e^{i pi}]

Updates are a good thing. Aside from bug fixes and features, they also provide much-needed security patches.
You need a really good reason not to update. One of the few reasons that I know of for not updating is when the update will break legacy software. For example: my previous workplace was using an older version of the Oracle Database engine because the newer versions aren't actually supported by the frontend that they use.

[yicheng]

I had this problem, too.  It looks like purging the browser cache and reloading the page solves the problem. 

Typically, this is caused by client-side script caching or storing of cookies from before the site was upgraded.   Unfortunately, it's not really avoidable without added complexity in code and/or degradation in website performance.

[matweller]

How would a browser cache a mobile version of a site that it never saw?

[Max e^{i pi}]

No. The browser cached the faulty script OR cached a good script that misbehaved because it was running off old data.

[Max e^{i pi}]

I had this problem, too.  It looks like purging the browser cache and reloading the page solves the problem. 

Typically, this is caused by client-side script caching or storing of cookies from before the site was upgraded.   Unfortunately, it's not really avoidable without added complexity in code and/or degradation in website performance.

I don't think that was the problem since I encountered it in an entirely different browser that had never seen the site before.