#18231 closed defect (bug) (worksforme)
Opera Mini being reported as out of date
| Reported by: | Ipstenu | Owned by: | nacin |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | WordPress.org Site | Version: | 3.2.1 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
From http://wordpress.org/support/topic/latest-opera-mini-flagged-as-old-version-of-opera?replies=1
I use the latest Opera Mini for Symbian v 6.1.25570 for access to my WordPress.org blogs from my mobile phone. It works well for comment moderation, minor edits to posts and upgrading plugins.
Since upgrading to WP 3.2.1 I've been seeing "It looks like you're using an old version of Opera.." on my Dashboard.
This message is incorrect as I AM running the latest version of Opera Mini. It's only a minor annoyance but it would be nice if it was fixed.
Change History (9)
#1
@
15 years ago
- Component Administration → WordPress.org site
- Milestone Awaiting Review → WordPress.org
- Owner set to
- Status new → assigned
#2
@
15 years ago
Desktop: (Stable/alpha version) Opera/9.80 (Windows NT 6.1; U; en) Presto/2.9.168 Version/11.50 Opera/9.80 (Windows NT 6.1; U; Edition Next; en) Presto/2.9.181 Version/12.00 Latest Mobile: Opera/9.80 (Android 2.3.4; Linux; Opera Mobi/ADR-1107051709; U; en) Presto/2.8.149 Version/11.10 Latet Mini: Opera/9.80 (Android; Opera Mini/6.1.25577/25.685; U; en) Presto/2.5.25 Version/10.54
Both are "outdated" rendering engines by a version or 2 compared to the desktop variant.
#3
@
15 years ago
Also keep in mind that many Opera Mini devices have no upgrade capability, cannot install version 6 if they wanted to.
#4
@
15 years ago
Also keep in mind that many Opera Mini devices have no upgrade capability
I assume the API would just ignore Mini/Mobile and not give the nag for them at all.
#7
@
14 years ago
- Component General → WordPress.org site
- Milestone Awaiting Review → WordPress.org
You're right. My mistake.
#8
@
13 years ago
- Milestone WordPress.org
- Resolution → worksforme
- Status assigned → closed
If this is still an issue, please file a new ticket on the meta trac, but this issue should be fixed.
#9
@
13 years ago
FWIW, with the latest Opera Mobile for android has merged Mini+Mobile, it's completely changed it's core code, so this doesn't appear to apply anymore.
Mozilla/5.0 (Linux; Android 4.0.3; LG-P880 Build/IML74K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.63 Mobile Safari/537.36 OPR/15.0.1162.61541
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
There's Opera Mini, Opera Mobile, and Opera Desktop, all with "distinct" User agents(If you're testing for one or the other)
I'll grab the latest User agent strings for comparison later.