Добродошли у Писарницу, портал заједнице Викизворника на српском језику. На овој страници сви корисници могу постављати техничка питања или питања о Викизворнику, писати коментаре, молбе и предлоге и износити нове идеје.
Right now, the feature is behind a feature flag - to use it on your wiki, please go to the Special:Undelete page, and add &fuzzy=1 to the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=1. Then search for the pages you're interested in. There should be more results than before, due to using ElasticSearch indexing (via the CirrusSearch extension).
We plan to enable this improved search by default on all wikis soon (around August 1, 2017). If you have any objections to this - please raise them with the Discovery team via email or on this announcement's discussion page. Like most Mediawiki configuration parameters, the functionality can be configured per wiki.
Once the improved search becomes the default, you can still access the old mode using &fuzzy=0 in the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=0
Please note that since Special:Undelete is an admin-only feature, this search capability is also only accessible to wiki admins.
The MediaWiki developers have been slowly improving the accessibility of the user interface. The next step in this transition will change the appearance of some buttons and may break some outdated (non-updated or unmaintained) user scripts and gadgets.
You can see and use the old and new versions now. Most editors will only notice that some buttons are slightly larger and have different colors.
Comparison of old and new styles
Buttons before the change
Buttons after the change
However, this change also affects some user scripts and gadgets. Unfortunately, some of them may not work well in the new system. If you maintain any user scripts or gadgets that are used for editing, please see mw:Contributors/Projects/Accessible editing buttons for information on how to test and fix your scripts. Outdated scripts can be tested and fixed now.
На Википедији је покренута расправа за формални концензус да се ажурира лого. Добродошла су мишљења свих уредника ако их има, а расправа је покренута тамо из практичних разлога, јер има више уредника (који ће се можда и активирати на неком од сродних пројеката као што је овај) и да све буде на једном месту. --Obsuser (разговор) 15:17, 2. август 2017. (CEST)
Покрећем расправу да се постигне формални консензус за промену вредности $wgArticleCountMethod на „any” за овај Вики тако да се броје све странице осим преусмерења и сл., као и на Википедији. Наиме, ово је већ грешком урађено без консензуса јер је таск на Фабрикатору заправи био намењен Викицитату а не Викизворнику. Проблем је био што се не броје странице без најмање једне викивезе итд. (прочитати одељак „Број цитата” на овом Тргу, ако неко не зна енглески има Гугл преводилац); примера ради, q:Херман Хесе, валидна страница, није се бројала све до последње измене када је додата веза човек.
Дакле, треба да се постигне концензус, да се захтев на Фабрикатору не враћа (таск). --Obsuser (разговор) 14:16, 15. август 2017. (CEST)
Currently, when you search on this wiki, the search results only return certain namespaces. It has recently been noticed that the "main content namespaces" list doesn't match the "default search namespaces" list on this wiki. (phab:T170473)
Currently this wiki's search returns the main namespace. The content namespace Аутор is also available if the community thinks that adding this namespaces is appropriate.
Would this community like to discuss adding Аутор to the search results? I am more than happy to help make the change however the community decides.
For the initial deployment, the feature will be available to Google Chrome browsers on Android. Support for other mobile browsers to come in the future. For Chrome, the feature will use the native Android print functionality. Users can choose to download a webpage as a PDF. Mobile print styles will be used for these PDFs to ensure optimal readability for smaller screens.
Помозите у превођењу на свој језик
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.
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.
Hi. With the requirement to fix the page categorisation as notified at phab:T198470, I would like to propose to the community to have our bot run through and address the problem with the solution identified. The bot has been used to resolve issue previously on the Wikisources.
Above I have added a bot request, as this wiki is not within the global bot project, per list m:Special:WikiSets/2. Would the community consider opting in to the global bots, so that when we have Wikisource-wide fixes for mw:Extension:ProofreadPage that is possible to organise the bots to do the jobs within Phabricator, and simply get the fix in place. Billinghurst (разговор) 14:16, 7. јул 2018. (CEST)
I would support the accession of the Serbian Wikisource to the Global Bot Project. --Новак (разговор) 00:34, 9. јул 2018. (CEST)
To improve the security of our readers and editors, permission handling for CSS/JS pages has changed. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which contain code that is executed in the browsers of users of the site.)
A new user group, interface-admin, has been created.
Starting four weeks from now, only members of this group will be able edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage).
You can learn more about the motivation behind the change here.
Please add users who need to edit CSS/JS to the new group (this can be done the same way new administrators are added, by stewards or local bureaucrats).
This is a dangerous permission; a malicious user or a hacker taking over the account of a careless interface-admin can abuse it in far worse ways than admin permissions could be abused. Please only assign it to users who need it, who are trusted by the community, and who follow common basic password and computer security practices (use strong passwords, do not reuse passwords, use two-factor authentication if possible, do not install software of questionable origin on your machine, use antivirus software if that's a standard thing in your environment).
Editing of sitewide CSS/JS is only possible for interface administrators from nowУреди
(Помозите у превођењу на свој језик)
as announced previously, permission handling for CSS/JS pages has changed: only members of the interface-admin (Администратори интерфејса) group, and a few highly privileged global groups such as stewards, can edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage). This is done to improve the security of readers and editors of Wikimedia projects. More information is available at Creation of separate user group for editing sitewide CSS/JS. If you encounter any unexpected problems, please contact me or file a bug.
The Wikimedia Foundation will be testing its secondary data centre. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
They will switch all traffic to the secondary data center on Wednesday, 12 September 2018.
On Wednesday, 10 October 2018, they will switch back to the primary data center.
Unfortunately, because of some limitations in MediaWiki, all editing must stop when we switch. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
You will not be able to edit for up to an hour on Wednesday, 12 September and Wednesday, 10 October. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Thursday 13 September and Thursday 11 October).
If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
There will be code freezes for the weeks of 10 September 2018 and 8 October 2018. Non-essential code deployments will not happen.
The ProofreadPage extension can now join together a word that is split between a page and the next.
In the past, when a page was ending with "concat-" and the next page was beginning with "enation", the resulting transclusion would have been "concat- enation", and a special template like d:Q15630535 had to be used to obtain the word "concatenation".
Now the default behavior has changed: the hyphen at the end of a page is suppressed and in this case no space is inserted, so the result of the transclusion will be: "concatenation", without the need of a template. The "joiner" character is defined by default as "-" (the regular hyphen), but it is possible to change this. A template may still be needed to deal with particular cases when the hyphen needs to be preserved.
Please share this information with your community.
Хтео бих да затражим право бирократе на један дан због тестирања када се ово буде омогућавало, да ли све функционише како треба. Право је неопходно да ми се да у недељу после 16 часова на 24 часа како би ми се аутоматски уклонило у понедељак после завршеног теста и омогућавања додатних корисничких права. Zoranzoki21 (разговор) 21:23, 17. октобар 2018. (CEST)
Change coming to how certain templates will appear on the mobile webУреди
Change coming to how certain templates will appear on the mobile web
Помозите у превођењу на свој језик
Example of improvements
In a few weeks the Readers web team will be changing how some templates look on the mobile web site. We will make these templates more noticeable when viewing the article. We ask for your help in updating any templates that don't look correct.
What kind of templates? Specifically templates that notify readers and contributors about issues with the content of an article – the text and information in the article. Examples like Template:Unreferenced or Template:More citations needed. Right now these notifications are hidden behind a link under the title of an article. We will format templates like these (mostly those that use Template:Ambox or message box templates in general) to show a short summary under the page title. You can tap on the "Learn more" link to get more information.
The Community Wishlist Survey. Помозите у превођењу на свој језик.
The Community Wishlist Survey is the process when the Wikimedia communities decide what the Wikimedia Foundation Community Tech should work on over the next year.
The Community Tech team is focused on tools for experienced Wikimedia editors. The communities have now posted a long list of technical proposals. You can vote on the proposals from now until 30 November. You can read more on the wishlist survey page.
until December 7th, people can add their name and a short explanation on who they are and why they want to go to the summit. Nomination of other people is allowed, the nominated person should accept their nomination.
starting December 7th, and for a week, the community vote to designate the representative.
These new requirements will apply to new accounts and privileged accounts. New accounts will be required to create a password with a minimum length of 8 characters. Privileged accounts will be prompted to update their password to one that is at least 10 characters in length.
These changes are planned to be in effect on December 13th. If you think your work or tools will be affected by this change, please let us know on the talk page.
Love is an important subject for humanity and it is expressed in different cultures and regions in different ways across the world through different gestures, ceremonies, festivals and to document expression of this rich and beautiful emotion, we need your help so we can share and spread the depth of cultures that each region has, the best of how people of that region, celebrate love.
Wiki Loves Love (WLL) is an international photography competition of Wikimedia Commons with the subject love testimonials happening in the month of February.
The primary goal of the competition is to document love testimonials through human cultural diversity such as monuments, ceremonies, snapshot of tender gesture, and miscellaneous objects used as symbol of love; to illustrate articles in the worldwide free encyclopedia Wikipedia, and other Wikimedia Foundation (WMF) projects.
The theme of 2019 iteration is Celebrations, Festivals, Ceremonies and rituals of love.
Sign up your affiliate or individually at Participants page.
A new beta feature will soon be released on all wikis: The FileExporter. It allows exports of files from a local wiki to Wikimedia Commons, including their file history and page history. Which files can be exported is defined by each wiki's community: Please check your wiki's configuration file if you want to use this feature.
The FileExporter has already been a beta feature on mediawiki.org, meta.wikimedia, deWP, faWP, arWP, koWP and on wikisource.org. After some functionality was added, it's now becoming a beta feature on all wikis. Deployment is planned for January 16. More information can be found on the project page.
You will not be able to edit the wikis for up to 30 minutes on 17 January 07:00 UTC. This is because of a database problem that has to be fixed immediately. You can still read the wikis. Some wikis are not affected. They don't get this message. You can see which wikis are not affected on this page. Most wikis are affected. The time you can not edit might be shorter than 30 minutes. /Johan (WMF)
Next, create a page (or a section on a Village pump, or an e-mail thread – whatever is natural for your group) to collect information from other people in your group. This is not a vote or decision-making discussion: we are just collecting feedback.
Then ask people what they think about communication processes. We want to hear stories and other information about how people communicate with each other on and off wiki. Please consider asking these five questions:
When you want to discuss a topic with your community, what tools work for you, and what problems block you?
What about talk pages works for newcomers, and what blocks them?
What do others struggle with in your community about talk pages?
What do you wish you could do on talk pages, but can't due to the technical limitations?
What are the important aspects of a "wiki discussion"?
Update on the consultation about office actionsУреди
Last month, the Wikimedia Foundation's Trust & Safety team announced a future consultation about partial and/or temporary office actions. We want to let you know that the draft version of this consultation has now been posted on Meta.
This is a draft. It is not intended to be the consultation itself, which will be posted on Meta likely in early September. Please do not treat this draft as a consultation. Instead, we ask your assistance in forming the final language for the consultation.
For that end, we would like your input over the next couple of weeks about what questions the consultation should ask about partial and temporary Foundation office action bans and how it should be formatted. Please post it on the draft talk page. Our goal is to provide space for the community to discuss all the aspects of these office actions that need to be discussed, and we want to ensure with your feedback that the consultation is presented in the best way to encourage frank and constructive conversation.
Please visit the consultation draft on Meta-wiki and leave your comments on the draft’s talk page about what the consultation should look like and what questions it should ask.
The Wikimedia Foundation wants to work on two things that affect how we patrol changes and handle vandalism and harassment. We want to make the tools that are used to handle bad edits better. We also want to get better privacy for unregistered users so their IP addresses are no longer shown to everyone in the world. We would not hide IP addresses until we have better tools for patrolling.
We have an idea of what tools could be working better and how a more limited access to IP addresses would change things, but we need to hear from more wikis. You can read more about the project on Meta and post comments and feedback. Now is when we need to hear from you to be able to give you better tools to handle vandalism, spam and harassment.
You can post in your language if you can't write in English.
Feedback wanted on Desktop Improvements projectУреди
Помозите у превођењу на свој језик
Здраво. The Readers Web team at the WMF will work on some improvements to the desktop interface over the next couple of years. The goal is to increase usability without removing any functionality. We have been inspired by changes made by volunteers, but that currently only exist as local gadgets and user scripts, prototypes, and volunteer-led skins. We would like to begin the process of bringing some of these changes into the default experience on all Wikimedia projects.
We are currently in the research stage of this project and are looking for ideas for improvements, as well as feedback on our current ideas and mockups. So far, we have performed interviews with community members at Wikimania. We have gathered lists of previous volunteer and WMF work in this area. We are examining possible technical approaches for such changes.
We would like individual feedback on the following:
Identifying focus areas for the project we have not yet discovered
Expanding the list of existing gadgets and user scripts that are related to providing a better desktop experience. If you can think of some of these from your wiki, please let us know
Feedback on the ideas and mockups we have collected so far
We would also like to gather a list of wikis that would be interested in being test wikis for this project - these wikis would be the first to receive the updates once we’re ready to start building.
When giving feedback, please consider the following goals of the project:
Make it easier for readers to focus on the content
Provide easier access to everyday actions (e.g. search, language switching, editing)
Put things in logical and useful places
Increase consistency in the interface with other platforms - mobile web and the apps
Plan for future growth
As well as the following constraints:
Not touching the content - no work will be done in terms of styling templates or to the structure of page contents themselves
Not removing any functionality - things might move around, but all navigational items and other functionality currently available by default will remain
No drastic changes to the layout - we're taking an evolutionary approach to the changes and want the site to continue feeling familiar to readers and editors