Closed
Bug 1051189
Opened 10 years ago
Closed 9 years ago
Install MobileFrontend extension
Categories
(Websites :: wiki.mozilla.org, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
2015-Q3
People
(Reporter: ckoehler, Assigned: ckoehler)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [featurerequest][extension][dev=2015-07-19] [stage=2015-07-19] [prod=2015-07-19])
The MobileFrontend extension provides a mobile-friendly view.
Updated•10 years ago
|
Target Milestone: --- → 2014-Q3
Assignee | ||
Updated•10 years ago
|
Target Milestone: 2014-Q3 → 2014-Q4
Assignee | ||
Updated•10 years ago
|
Whiteboard: [featurerequest][extension][2014q3] → [featurerequest][extension]
Target Milestone: 2014-Q4 → 2015-Q1
Assignee | ||
Comment 1•9 years ago
|
||
Progress! I've this up and running on the sandbox: http://wiki-sandbox.allizom.org/Main_Page I've only done the very basic configuration, which you can see in this commit: https://github.com/christi3k/wiki.mozilla.org/commit/f778e878b8fa17d8c968fd7468d42222b8daf4b5
Assignee | ||
Comment 2•9 years ago
|
||
Setting $wgMFAutodetectMobileView = true works in the sandbox, but per the documentation[1]: "This solution is NOT compatible with front-end caching, as it provides no way for your cache to know the difference between a mobile view and a desktop view." They recommend using two separate domains for the mobile and desktop versions, pointing both to the same Mediawiki installation, setting a custom header for requests coming to the mobile domain, and setting $wgMobileUrlTemplate accordingly. JD or C, is this possible with our current setup? [1]https://www.mediawiki.org/wiki/Extension:MobileFrontend/Configuring_browser_auto-detection
Flags: needinfo?(jcrowe)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → ckoehler
Comment 3•9 years ago
|
||
Dear Jason, Can you help to shed some light for comment 2 from Christie? Thanks!
Comment 4•9 years ago
|
||
This sounds possible. I think we could just add the new domain to the vhost file.
Flags: needinfo?(jcrowe)
Assignee | ||
Updated•9 years ago
|
Target Milestone: 2015-Q1 → 2015-Q2
Updated•9 years ago
|
Target Milestone: 2015-Q2 → Future
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [featurerequest][extension] → [featurerequest][extension][dev=2015-07-19] [stage=2015-07-19] [prod=2015-07-19]
Target Milestone: Future → 2015-Q3
You need to log in
before you can comment on or make changes to this bug.
Description
•