Wikibooks:Reading room/Technical Assistance

Welcome to the Technical Assistance reading room. Get assistance on questions related to MediaWiki markup, CSS, JavaScript, and such as they relate to Wikibooks. This is not a general-purpose technical support room.

To submit a bug notice or feature request for the MediaWiki software, visit Phabricator.

To get more information about the MediaWiki software, or to download your own copy, visit MediaWiki

There are also two IRC channels for technical help: #mediawiki for issues about the software, and #wikimedia-tech for WMF server or configuration issues.

Creating Book Pages

I am a new user and I am still not familiar with how to correctly create pages in a book. I received this as a comment: Pages should be created as a subpage - e.g,. "Book Name" and "Book Name/Chapter Name" and NOT as "Chapter Name".

It seems that the pages are fixed. Can I create /Chapter Name/ instead? Is this equivalent to Book Name/Chapter Name? --Rjbfigueroa (discuss • contribs)

Renaming Book Pages

How do I rename a Book Page? When I change the name of the Book Page, it seems that the link to the old page is broken and I have copy the old content to the new page that was created as a result of renaming. TIA!

--Rjbfigueroa (discuss • contribs)

@Rjbfigueroa: Can you give an example of a page you wanted to move, and where you wanted to move it to, so we can see what happened?

Fwiw, here's how to move a page, if you're using Vector skin (in the desktop interface, rather than the mobile one): View the page you want to move (not its talk page). There should be a control bar at the top of the browser, and way over on the far right of it there should be a dropdown menu. The only option on that menu should be either "rename" or "move"; use that. --Pi zero (discuss • contribs)

Update on page issues on mobile web

Update on page issues on mobile web

Please help translate to your language Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.

So far, we have drafted a proposal on the design and implementation of the project. We were also able to run user testing on the proposed designs. The tests so far have positive results. Here is a quick summary of what we learned:

• The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
• Page issues make sense to readers and they understand how they work
• Readers care about page issues and consider them important
• Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues

Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page.

CKoerner (WMF) (talk) 20:58, 12 June 2018 (UTC)

Tidy to RemexHtml

The Parsing team will be replacing Tidy with RemexHtml at this wiki on 5 July 2018.

Some pages at this wiki use outdated HTML. This change may change the appearance of those pages. Special:LintErrors has a complete list of affected pages.

Read this e-mail message for more information. Read the instructions at mw:Help:Extension:Linter. You can ask questions at mw:Talk:Parsing/Replacing Tidy. Thank you for helping fix these problems.

m:User:Elitre (WMF) 14:38, 2 July 2018 (UTC)

Consultation on the creation of a separate user group for editing sitewide CSS/JS

(Please help translate to your language)

Hi all,

I'm preparing a change in who can edit sitewide CSS/JS pages. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which are executed in the browser of all readers and editors.) Currently all administrators are able to edit these pages, which poses a serious and unnecessary security risk. Soon, a dedicated, smaller user group will take over this task. Your community will be able to decide who belongs in this group, so this should mean very little change for you. You can find out more and provide feedback at the consultation page on Meta. If you are involved in maintaining CSS/JS code, or policymaking around adminship requests, please give it a look!

Thanks!
Tgr (talk) 10:50, 9 July 2018 (UTC) (via global message delivery)