Page MenuHomePhabricator
Search Advanced Search
    • Task
    This task is about revising where signatures appear in relation to barnstars/wikilove. This task was inspired by @Jdforrester-WMF who suggested [i] having the [Wikilove extension](https://www.mediawiki.org/wiki/Extension:WikiLove) place signatures //outside// tables/templates as a potential solution to T250126 which, as @Ladsgroup notes [ii], seems to have regressed since June 2020. [iii] === Open questions - [ ] What are cases where signature appearing //outside// the template/table would be problematic? --- i. https://w.wiki/mso ii. https://w.wiki/msp iii. T250126#6194963
    • Task
    NOTE: low priority. Just wanted to capture this somewhere and start the conversation given the many extensions that use these. https://codesearch.wmcloud.org/search/?q=SkinTemplateNavigation%3A%3ASpecialPage&i=nope&files=&excludeFiles=&repos= https://codesearch.wmcloud.org/search/?q=SkinTemplateNavigation%22%3A&i=nope&files=&excludeFiles=&repos= Every time the SkinTemplateNavigation::SpecialPage and SkinTemplateNavigation hooks are run we also run the SkinTemplateNavigation::Universal hook. The latter is always run based on the current page. We could just run the latter and get rid of 2 needless hooks. # Proposal: Having 3 hooks doing pretty much the same thing seems gratutious. I would suggest standardizing on **SkinTemplateNavigation::Universal ** and for the hooks themselves to do the required checks they need. I am however open to keeping all three after hearing from the current extensions using these hooks (tagged) and benefits they see in having three of them. The SkinTemplateNavigation hook is deprecated in favor of SkinTemplateNavigation::Universal . It's up to callers to check whether the title exists if they care. The SkinTemplateNavigation::SpecialPage is deprecated in favor of SkinTemplateNavigation::Universal. Callers must use $skin->getTitle() to check whether the page is a special page # Fixed Extensions/skins that are fixed are listed here and have been untagged. [x] Vector [x] FileExporter [x] QuizGame [x] PictureGame [x] BlueSpice [x] NSFileRepo [x] FlaggedRevs [x] AdvancedMeta [x] TimedMediaHandler [x] Newsletter [x] TinyMCE [x] ProofreadPage
    • Task
    Steps to reproduce: * Open wikilove part of the toolbar * Select "Send WikiLove" without selecting any editors * Proceed through wikilove interface, and send Expected result: Error given lack of recipients Actual result: Since wikilove can also be activate from a user page, if no recipients are specified when the interface is opened, the default is to try and send to `mw.config.get( 'wgTitle' )`, which isn't a good idea in this case (sending wikilove to an article)
    • Task
    Steps to reproduce: Send a wikilove message using PageTriage Actual result: PageTriage isn't tagged (though WikiLove is) Expected result: Both are tagged See also {T226789}
    • Task
    Steps to reproduce: Send wikilove to a user through the page triage toolbar (Note: the preview will appear to have been automatically signed by the user) Expected result: Message is sent as it was previewed, and the posted message includes a signature automatically Actual result: No signature is added
    • Task
    **Steps to reproduce:** **on Flow pages (reproducible in betalabs)** # Open WikiLove (click heart icon) and pick a kitty to send. Type a message. # Use the X in the corner of the box to close it. # Open WikiLove again (click heart icon again). # Preview. # Send. **Actual results:** Two identical messages posted. **Expected results:** One message sent. **Extra fun:** Double-click the Send button in step 5. Then you can send four kitties. On wikitext User talk pages, the steps are as above, but the Send button **must ** be double-clicked.
    • Task
    MacOS 10.12.6 (16G1212) Chrome Version 64.0.3282.186 (Official Build) (64-bit) Also reproducible with Safari Version 11.0.3 (12604.5.6.1.1) When the window isn't wide enough to fit all the tabs, some of the tabs get merged in a weird way. See the left pane in the attached screenshot. The right pane is exactly the same page, but with the window stretched wider so all the tabs fit. When I check "Temporarily disable the visual editor while it is in beta" under Special:Preferences#mw-prefsection-editing, I can't reproduce the problem. {F15273054}
    • Task
    This project is about converting MediaWiki extensions [[ https://www.mediawiki.org/wiki/Extension:WikiLove | WikiLove ]] and [[ https://www.mediawiki.org/wiki/Extension:MassMessage | MassMessage ]] to use [[ https://www.mediawiki.org/wiki/OOUI | OOUI ]]. OOUI is the Wikimedia Foundation's widget library that follows our [[ https://design.wikimedia.org/style-guide/ | style guide ]]. We are trying to move all interfaces to this new library so that we no longer have a mix of old CSS, no CSS and jQuery UI. For the project you'll need to: * Look at the current design of the extension and see how it can be redesigned using OOUI [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=widgets&theme=wikimediaui&direction=ltr&platform=desktop | widgets ]], [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=dialogs&theme=wikimediaui&direction=ltr&platform=desktop | dialogs ]], and [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=widgets&theme=wikimediaui&direction=ltr&platform=desktop#Outlined-BookletLayout | layouts ]] * Migrate the forms to [[ https://www.mediawiki.org/wiki/HTMLForm | HTMLForm ]] where applicable * Switch the interface to using OOUI There are many extensions and special pages that have already been converted: * {T137017} * {T104299} * {T96914} ### Subtasks * {T104419} * {T89815} ### Skills required * HTML * Javascript * PHP * UI design * Familiarity with OOUI & [[ https://www.mediawiki.org/wiki/HTMLForm | HTMLForm ]] ###Mentors: * @Prtksxna ### Get started * Download and setup [[ https://gerrit.wikimedia.org/r/#/admin/projects/oojs/ui | OOUI ]]. ** See `README.md` to get started ** Checkout the demo page [[ https://doc.wikimedia.org/oojs-ui/master/demos/?page=widgets&theme=wikimediaui&direction=ltr&platform=desktop | online ]], and build it locally: `npm run build` ** Understand the basics of OOUI by [[ https://doc.wikimedia.org/oojs-ui/master/demos/tutorials/index.html | following the tutorial ]]. * Download and setup MediaWiki using [[ https://www.mediawiki.org/wiki/MediaWiki-Vagrant | Vagrant ]] * Install and try the above mentioned extensions: [[ https://www.mediawiki.org/wiki/Extension:WikiLove | WikiLove ]], and [[ https://www.mediawiki.org/wiki/Extension:MassMessage | MassMessage ]] * Take a loot at [[ https://phabricator.wikimedia.org/search/query/azZSfI1etlLu/#R | easy tasks related to OOUI ]] * Talk to us here, or on IRC: `#wikimedia-dev` or `#wikimedia-editing`
    • Task
    As [[https://en.wikipedia.org/wiki/Wikipedia_talk:WikiLove/Archive_1#Strange_behaviour_by_WikiLove?|suggested]]: > the wikitext emitted from the WikiLove tool should have a comment in it to say it was produced by the WikiLove tool with some suitable link, so it educates people to use the tool I.e. WikiLove should automatically add a hidden comment after the user's signature, such as: `<!-- message sent using the WikiLove tool. Click the ♥ at the top of userpages to send WikiLove. -->` or similar.
    • Task
    See https://www.mediawiki.org/wiki/User_talk:IKhitron I clicked once. Based on testing at https://www.mediawiki.org/wiki/User_talk:Quiddity_(WMF)#A_barnstar_for_you.21 the **steps to reproduce** might be: # Go to Quiddity's talk page on mw.org # Open Wikilove. Choose a barnstar from the drop-down menu. # Press Esc to cancel. (Go do something else, e.g., scroll down the page or open a link in another tab.) (If you skip this step, then Wikilove works normally.) # Open Wikilove again. Choose a barnstar from the drop-down menu. # Press Esc to cancel. (Go do something else, e.g., scroll down the page or open a link in another tab.) # Open Wikilove a third time. Choose a barnstar (maybe needs to be the same as the first one?) from the drop-down menu. # Fill in the box. # Send Wikilove. # See two identical barnstars on the page. # Refresh the page. # See three identical barnstars on the page. I've only tested this in Flow.
    • Task
    Port it to use the server-side MessagePoster interface in core
    • Task
    When posting a Wikilove message to a usertalkpage that uses Flow, the preview shows a signature, but the signature is actually removed (purposefully, because signatures are not needed/used in Flow posts). Ideally, the preview would not show the signature, if the page is using the Flow content model. {F1297105}
    • Task
    Duplicate section headings make pages hard to edit and navigate. Please find a system that reduces the number of == A barnstar for you! == section headings. My three ideas are: == An Original Barnstar for you! == == A barnstar for you! (August 2014) == == A custom section heading for you! == The last would use the same form as "Make your own", pre-populated with the default section heading. This way it would be easy to change it if you wanted to. -------------------------- **Version**: unspecified **Severity**: enhancement
    • Task
    WikiLove logs actions to a custom database, for analytics purposes. This was before we had EventLogging infrastructure. Since we now do have EventLogging infrastructure, we should migrate to that and ditch the database. -------------------------- **Version**: unspecified **Severity**: enhancement
    • Task
    At https://www.mediawiki.org/wiki/Thread:User_talk:Peachey88/A_kitten_for_you! WikiLove added a signature in the message itself even though LQT adds in a signature at the bottom of the message. Somewhere in the WikiLove javascript, a request is made to action=wikilove, and the text parameter of that request already has ~~~~ in it. We can either have that portion of JS check whether we're on a LQT enabled page, or postpone adding the signature in the PHP portion, and add it if we're not on LQT. -------------------------- **Version**: unspecified **Severity**: normal **URL**: https://www.mediawiki.org/wiki/Thread:User_talk:Peachey88/A_kitten_for_you!
    • Task
    Using my laptop monitor which is of a lower resolution, the preview for a wikilove message goes down past the bottom of the window, hiding the send button In Chrome 29 I'm unable to move the scroll bar down to reach the button. I can use page up/down though... -------------------------- **Version**: master **Severity**: minor
    • Task
    It'd be nice if WikiLove had a javascripty autocomplete for image names (at least local ones) -------------------------- **Version**: master **Severity**: enhancement
    • Task
    Wikilove places messages in interface language of the user who using wikilove to pass appreciation. It should either be in wiki language or be like other interface messages (switch languages per user.) https://commons.wikimedia.org/w/index.php?title=User_talk%3ARas67&diff=102879216&oldid=102817340 -------------------------- **Version**: unspecified **Severity**: normal
    • Task
    The WikiLove heart icon is currently solid red. It sits next to the watch star icon, which is transparent with a blue border until a user clicks the star icon (i.e., watches a page), in which case the star icon becomes solid blue. It's a bit strange that the heart icon appears to indicate that you've already doled out wikilove to the user by being solid red, particularly when it's juxtaposed with the "empty" (transparent) star icon. Perhaps the icon should use a red border instead. -------------------------- **Version**: unspecified **Severity**: trivial
    • Task
    **Author:** `shijualex` **Description:** As of now, by default the wiki love message is placed on User Talk page even if we click the wiki love icon from User Page. But in most wikis (at least in Malayalam Wikipedia) the barnstars are usually placed on User Pages. So there should be an option to place the message directly on User page apart from the current User Talk page. That is, if we click the WikiLove icon from User page the message should be placed on User Page. Same way if we click the Wiki Love icon from User Talk page then the message should be placed on User Talk page. -------------------------- **Version**: unspecified **Severity**: enhancement
    • Task
    Many people who don't know JavaScript would like to add customized WikiLove awards, but customizing WikiLove awards requires editing cryptic JavaScript pages. It also requires sysop rights, even though it is not needed for the classic barnstars. It would be nice to have an interface through which all users would be able to edit awards without having to know programming. -------------------------- **Version**: unspecified **Severity**: enhancement
    • Task
    **Author:** `eggcentricwiki` **Description:** Since wikilove is making edits to other users' talk pages, I think there ought to be an "add to watchlist" checkbox, much as there is if one were making the edit entirely manually. I should imagine this will take about 20 minutes, if that, to implement. -------------------------- **Version**: unspecified **Severity**: enhancement