확장기능:모바일 프론트엔드
 출시 상태: 안정 |
|
|---|---|
 |
|
| 구현 | 사용자 인터페이스, Hook |
| 설명 | 모바일 친화적 보기 제공 |
| 만든이 | |
| 최신 버전 | 2.3.0 |
| 호환성 정책 | Snapshots releases along with MediaWiki. Master is not backward compatible. |
| MediaWiki | 1.33+[1] |
| PHP | 5.5.9+ |
| 라이선스 | GNU General Public License 2.0 or later |
| 다운로드 | README |
| 예제 | m.mediawiki.org |
|
|
|
|
| MobileFrontend 확장 기능 번역 (translatewiki.net에서 가능한 경우) | |
| 이슈 | 미해결 작업 · 버그 보고 |
모바일 프론트엔드 확장기능:
- 모바일 이용자들을 위한 별도의 모바일 UI를 만듭니다.
- 시스템 관리자는 다른 스킨을 제공 할 수 있습니다. 예. 스킨:미네르바 노이어.
- 다양한 컨텐츠 변환 기능을 제공하여 컨텐츠를 더욱 친숙하게 만듭니다.
- Notably section collapsing and content re-arrangement and removal, including putting the lead paragraph above the lead photo or info box, even if the lead paragraph is below them in the page's source code.
- 모바일 하단바를 간단하게 만들고 데스크톱/모바일 사이트 링크를 만듭니다.
- provides replacements for special pages that are not mobile friendly:
Special:History, Special:Contributions, Special:Watchlist, Special:Preferences, Special:MobileDiff
- provides the special pages Special:Nearby, Special:MobileOptions (for mobile skin preferences), Special:MobileLanguages (for language selection),
- provides a beta mode with a feature management system for adding experimental features for anonymous users.
This page is designed for end users who want to install it on their development instance. If you are keen to help us build it and improve it we encourage you to get involved.
| This extension is maintained by the Reading Web team. |
전제조건
Before installing MobileFrontend, if you make heavy use of templates and/or inline styles (the style attribute) you should review your content to see whether it is mobile friendly. The TemplateStyles extension can be used to style content so that it renders nicely on mobile and desktop. MobileFrontend will not magically fix this for you!
In particular, you may want to review your landing page (main page). Mobile Gateway/Mobile homepage formatting|모바일 대문 설정을 참조.
설치
- Vagrant를 사용하고 있는 경우에는,
vagrant roles enable mobilefrontend --provision로 설치해주세요
- 수동 설치
- Download and place the file(s) in a directory called
MobileFrontendin yourextensions/folder. - 아래의 코드를 LocalSettings.php의 말미에 추가합니다:
wfLoadExtension( 'MobileFrontend' );
- 만약 사용자의 편의에 필요한 구성
완료 – 위키의 ‘Special:Version’에 이동해서, 확장기능이 올바르게 설치된 것을 확인합니다.
Nearby 셋업
MobileFrontend provides the Special:Nearby page with a little configuration. To get this to work a few optional steps are required:
- Due to browser security you will need to be running a secure site over SSL — it is not possible to request a user's location over HTTP.
- Install the GeoData extension
- Run update.php
- In LocalSettings.php add
$wgMFNearby = true; - Determine article coordinates:
- Add location data to your articles by using the
coordinatesparser function, for example{{#coordinates:37.786971|-122.399677|primary}}. For syntax details, see the documentation for GeoData. - Alternatively you can use a separate MediaWiki installation for Nearby by setting
$wgMFNearbyEndpointin your LocalSettings.php file. For example,$wgMFNearbyEndpoint = 'https://en.m.wikipedia.org/w/api.php';will use coordinates of English Wikipedia articles. The nearby endpoint will be used to find content related to a given location.
- Add location data to your articles by using the
스킨 설치
MobileFrontend provides you with a mobile formatted website to go alongside your existing desktop website. You can skin it however you want.
// Choose one of these and add chosen code to bottom of LocalSettings.php file:
wfLoadSkin( 'MinervaNeue' );
$wgMFDefaultSkinClass = 'SkinMinerva'; // use Minerva skin (You need to download and install it separately, otherwise you'll get an exception)
wfLoadSkin( 'Vector' );
$wgMFDefaultSkinClass = 'SkinVector'; // use Vector skin
wfLoadSkin( 'Timeless' );
$wgMFDefaultSkinClass = 'SkinTimeless'; // use Timeless skin
The following skins are compatible with MobileFrontend:
- Skin:Minerva Neue (stable, default on WMF wikis)
- Skin:Vector (default desktop skin, uses an experimental responsive mode for mobile)
- Skin:Timeless (experimental skin)
구성 설정
Additional tweaks
Get the most out of MobileFrontend by adding these optional compatible extensions:
- Extension:GeoData - Get Special:Nearby and geotag your articles.
- Extension:PageImages - Adds images to search and nearby results.
- Extension:VisualEditor - Add Visual editing to your mobile experience.
로컬 커스터마이징
CSS 설정
To apply CSS to your mobile theme, edit MediaWiki:Mobile.css, the counterpart of MediaWiki:Common.css.
In order for the stylesheet to function you may have to add mw.loader.using('mobile.site.styles') to your MediaWiki:Mobile.js.
MobileFrontend does not load the global MediaWiki:Common.css, neither does it load any of the user stylesheets.
자세한 정보
If you would like to test the mobile extension on a desktop browser or your device doesn't render the mobile version, you can append the following key-value pair to the URL query string: ?useformat=mobile. For example: https://en.wikipedia.org/wiki/Chuck_Schuldiner?useformat=mobile
If you would like to view the mobile version of a page without enabling the extension across the entire site you can append the string to the URL on that page, too.
Legacy features of MobileFrontend
MobileFrontend has traditionally been a very large extension. Many features have either surpassed their requirements or will do at some future date. These are listed below.
API
APIs are provided by the MobileFrontend extension, but long term we expect to deprecate them in favour of Page Content Service. Use these APIs at your own risk. They may disappear (although we will give you sufficient notice when they do)!
MobileView API
Extended action=parse
action=parse accepts extra parameters:
mobileformat=- Return rendered page HTML in a mobile format 1.23+. Prior to MediaWiki 1.23, you could specify
mobileformat=htmlto output HTML for modern phones ormobileformat=wmlto output WML for dumb phones (see mailing list messagefor details). noimages- Disable images in mobile output.
mainpage- Apply mobile main page transformations.
예시:
| Result |
|---|
{
"parse": {
"title": "Therion (band)",
"text": {
"*": "<div><table class=\"infobox vcard plainlist\" style=\"width:22em\"><tr><th colspan=\"2\" style=\"text-align:center;font-size:125%;font-weight:bold;background-color: #b0c4de\"><span class=\"fn org\">Therion</span></th>\n</tr><tr><td colspan=\"2\" style=\"text-align:center\"><a href=\"/wiki/File:2130860153_281d30b3bf_b.jpg\" class=\"image\">
...
|
meta=siteinfo
The domain of the mobile version of the site (which might or might not be the same as the normal domain) is available under the mobileserver key of the general siteinfo information.
For developers/sysadmins
Setup
You may need to run npm install and install php composer to get the precommit hook to run, depending on what you're doing with the extension.
Testing with articles on a foreign wiki (live data)
MobileFrontend can now be configured locally to render articles from other MediaWiki instances.[2]This can help you debug problems locally instead of importing articles which may have dependencies on various templates and Wikibase identifiers from production to your local instance. This is not recommended for production usage.
The code below will turn your local MediaWiki mobile site into a Wikivoyage viewer:
$wgMFContentProviderClass = 'MobileFrontend\ContentProviders\MwApiContentProvider';
$wgMFMwApiContentProviderBaseUri = 'https://en.m.wikivoyage.org/w/api.php';
This is particularly useful for testing different mobile skins using the wgMFDefaultSkinClass config option.
모바일 뷰 사용하기
WMF 사이트들
On Wikimedia Foundation-run sites, we use Varnish caching servers to check the user agent of your device.
WMF를 사용하지 않는 사이트들
For non-WMF sites, you can either set up your configuration to mimic how things are done at the WMF (doing device detection at the proxy layer and setting specific X-Device headers), or you can simply use "?useformat=mobile" to switch an article to use the mobile view.
$wgMFMobileHeader = 'X-WAP'; or modify your cache (Varnish) header setting, as long as they match.FAQ
The following questions frequently appear on our talk page. Please check this list before posting about them on the talk page or use the existing talk topic, if available, to receive clarifications.
Q: 어떻게 미네바 스킨의 메인 메뉴를 커스터마이징하죠?
A: This is tracked in phabricator but you can see Topic:Tiggc18fvd3stmsf has an interim solution.
Q: How do I add HTML to the Minerva skin, for example to add ads or additional script tags?
A: You can do this by editing the template file for the skin (currently include/skins/minerva.mustache). See this discussion for details.
Q: The extension I am using doesn't seem to work on MobileFrontend. Why?
A: It's likely the extension is old and needs to add compatibility to MobileFrontend. Please contact the developer of the extension and point them to ResourceLoader/Writing a MobileFrontend friendly ResourceLoader module. Please do not post to the talk page, as in this case it would be better to file a bug on Phabricator (you can login using your MediaWiki.org username) for a quicker response.
Q: I upgraded MobileFrontend and now I'm getting a fatal exception!
A: You are probably using incompatible versions of MobileFrontend and MediaWiki. In most cases, we can't help you here. Try upgrading MobileFrontend or MediaWiki to resolve your issue.
Q: After upgrading MediaWiki I'm getting an exception wgMFDefaultSkinClass is not setup correctly.
A: MobileFrontend currently assumes you have the 스킨:미네르바 노이어 skin installed. If you don't you'll need to install this or configure your mobile skin per instructions above.
확장기능 개발자를 위한
By default resource modules in extensions will not be loaded in mobile view.
Should a module need to be loaded while in mobile view this guide on writing MobileFrontend friendly modules will be of help.
같이 보기
각주
- ↑ :Fatal error: Uncaught ExtensionDependencyError: MobileFrontend is not compatible with the current MediaWiki core (version 1.32.2), it requires: >= 1.33.0.
- ↑ See this YouTube demo video
| This extension is being used on one or more Wikimedia projects. This probably means that the extension is stable and works well enough to be used by such high-traffic websites. Look for this extension's name in Wikimedia's CommonSettings.php and InitialiseSettings.php configuration files to see where it's installed. A full list of the extensions installed on a particular wiki can be seen on the wiki's Special:Version page. |