Tech

From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search

Navboxes problem on mt.wiki[edit]

On the Maltese Wikipedia the navigation boxes displayed at the end of certain pages are broken. They use the Navbox template, but when one tries to collapse/show the content of the template nothing happens. I tried checking the Common.js file but couldn't find any problems. Last May the code was changed to handle JQuery, but I reverted it back to see if that change has affected anything. But nothing happened. Can someone take a look at it and tell me what the problems may be. Thanks. —Chrisportelli 12:55, 12 June 2014 (UTC)

[1]. You left #wikimedia-tech 20 seconds before I replied you. --Nemo 13:00, 12 June 2014 (UTC)
The same issue appears to be affecting en.WN (reported in IRC about 20 hours ago, see also n:en:Wikinews:Water_cooler/technical#Broken??) - Amgine/meta wikt wnews blog wmf-blog goog news 17:52, 12 June 2014 (UTC)

Urgent: IP cap lifted for edit-a-thon[edit]

Dear Techs, I am training a group of people in Cape Town to contribute to Wikipedia for Youth Day. Please can you lift the IP cap on Wikipedia logins for the following IP: 41.133.182.152. Apparently, I need a sysadmin to do this. Please help!Islahaddow (talk) 07:50, 14 June 2014 (UTC)

Self-help material: mw:Help:Mass account creation. --Nemo 07:55, 14 June 2014 (UTC)
@Islahaddow: This will require a bugzilla: request. If you are looking to do this on enWP, they could also look to make you (or someone else that we can trust) an account creator, which gives greater privileges outside some of the normal choke points. If you are editing in more than just enWP, then pop over to SRP and place a request there with the info on where you will be editing, and stewards will see what they can do outside of the big WPs.  — billinghurst sDrewth 08:01, 14 June 2014 (UTC)
@Islahaddow: I have intervened and granted you temporary account creator rights for meta, and will complete the remainder of the paperwork at Meta:Requests for help from a sysop or bureaucrat, and would appreciated you popping passed that page, when you have spare time, to see whether that should be extended, or removed in a few days.  — billinghurst sDrewth 08:18, 14 June 2014 (UTC)
billinghurst Thank you so much, i will definitely do what you advise in the future, and will also pass through that page to close the request on Monday night, after the event finishes. Thank you again!! Islahaddow (talk) 08:31, 14 June 2014 (UTC)
I think this should be solved more smartly:
When a user creates an account in an edit-a-thon, if the wiki says that the account cannot be created immediately due to a cap rate, the information page should contain a form saying that this limitation can be overriden by asking to an administrator present, that will enter his login name and login password to login temporarily, andd to authorize the account creation: this will allow to bypass this block, by granting the "confirmed by account creator" right (a log entry will list the name of the admin authorizing the account creation above the cap). If the admin logs in successfully and confirms the account creation, then the administrator will be logged out immediately, and the user that wanted to create his account will be able to login with the new account. The right "confirmed by admin" should be handled exactly like new accounts". The account may be "autoconfirmed" later, but should have the same edit rate cap than other new accounts created isolately at home.
Ideally, once each participant in the edit-a-thon event has his account and is logged in, they should sign up to the event by signing the participation list (that allows monitoring the event and tracking participation statistics), but they should not be required to do so (they may want to participate to the event without being monitored later. For Wikimetrics, there should exist an option that allows users to sign up only for a much shorter period limited to the event time, without being tracked for the next months after the event. So signup options should offer the choice, and Wikimetrics should support cohorts where each user has a date limit. It could be a choice like: one day (up to the day after the event), one week, one month, six months.
Also users should be informed about the cohorts in which they are registered, so that they can unsubscribe it in Wikimetrics, when they want after a minimum period (that minimum period should not exceed one week, so that edit-a-thons will still have useful metrics collected for most users in that period, except those that did not want to signup including for their active presence in the event).
It's up to the event organizer to explain to participants why participants should signup with their existing or new account to the data collection in Wikimetrics, and up to the organizer to provide the necessary information about the data collected; as explained in Wikimetrics help page (which explains the registration procedure).
No more need to create accounts in advance by the event organizer. Participants should continue creating accounts themselves at home
They can also create an account during the event with their smartphone or tablet connected to the Internet by their own mobile operator, before using their account with the shared Internet access available at the event.
To simplify things, the event organizer could print a QRCode linking to the Wikimedia account creation page: users will scan it with their smartphone they will follow the normal procedure to fill the form and immediately they will be logged in without searching and using much data bandwidth. Then they'll be able to use this account using the shared internet access of the event instead of using the mobile network (often expensive and much slower when used indoor). verdy_p (talk) 06:34, 26 June 2014 (UTC)

Meine Vorstellung, Mimis Lyrik[edit]

Warum ist es so schwierig die Foren zu konvertieren und zu veröffentlichen? Mimis Lyrik: Mail= beten@live.de

What do you want to convert and publish in "the forum". Are you talking about the forum on this page ? Weren't you able to ask your question here ? And what did you want to convert in this page ???
That page is left multilingual and people can ask questions in any language, others will help you translate it if needed
(or if an automatic translation does not produce something reliable enough, but your question here causes no diffculty to Google)
verdy_p (talk) 18:59, 15 July 2014 (UTC)

Cannot find server[edit]

I cannot connect to Wikisource, Wikiversity, or Wiktionary. I'm told "network can't find server" regardless of the browser I use. However, I can connect to Commons, Wikipedia, and Wikidata. Is anyone else having these problems? Has something gone amiss that has affected some of the WM projects? I had no problems a few hours ago. --EncycloPetey (talk) 22:09, 16 July 2014 (UTC)

Problem has now resolved itself (or someone did purposefully). --EncycloPetey (talk) 23:09, 16 July 2014 (UTC)
It may happen eveytime to everyone with any website. Most often this is because your ISP (or your local router) has not received in due time a reply to a DNS resolution request, and has cached the error for some hours.
Generally, just rebooting your router is enough to solve the problem. Many ISPs also have DNS servers configured in their Internet access that do not scale for all the accesses made by their own subscribers. This does not mean that the web sites have any problem. If you're in doubt, try opening the site using a third party proxy.
Another solution: replace the default DNS servers proposed by your ISP by a thinrd party DNS service (I use OpenDNS.com, whose addresses to configure in your router instead of "automatic addresses" configured by DHCP, are: 208.67.222.222 and 208.67.220.220). This is not a proxy, you still have a direct access to the sites with their standard domain name, and their standard IP addresses (with IPSEC and HTTPS still working, as well as authentication certificates).
But at least you avoid that your ISP incorrectly redirect you to some other unrelated sites hen they want, to send you to a "customer help" webpage showing adds ands proposing other websites with which they have partenered commercially. Many ISPs are doing it today, breaking the "net neutrality" and forcing you to visit sites you did not want, simply because they incorrectly think that the site you wanted is unavailable (or unresponsive to their own bugged tests). If for a couple of minutes during maintenance time a wikimedia site is slow or down and restarting, some ISPs are redirecting you (with their commercial DNS) to their commercial parking page using their own ad-pormoted search engine, and they will cache this for about 1 hour and up to 24 hours, during which their DNS server will really lie to you with falsified information. I no longer trust any commercial ISP that can show you these redirects without any explicit permission (well, they do it with a "permission" hidden in cryptic small lines in their subscription contract, saying that they don't offer any warranty to connect you with the sites you wanted).
(OpenDNS may redirect some sites, but with **your** full control, and it brings you detailed logs about when this occured; it can do this for example to implement a useful filter to block known sites hosting malware, phishing or cybersquatting intended to trump you with faked marks, or currently under attack and whse security is known to be compromized, but it will neer redirect you directly to another site without first explaining what's happening.
Some antivirus solutions also propose to replace the malicoous DNS server of your ISP by their own DNS, with your permission and with a personal control and logging page allowing you to set what to check and which kind of blacklists you want to use (e.g. it can implement a parental filter to blocks some respectable domains but that are not suitable for children, such as dating sites, online gambling, and many personal pages hosting unmonitored photos and videos, or sites using simple on-click per-per-view "micro-"payments without confirming any credit card info).
Note: Wikimedia sites are now all accessible with HTTPS and are authenticated. If you don't see the "locker" icon when connecting to a Wikimedia site, and see any other page proposing you to connect somewhere else or with ads, you know that your ISP is abusing. Forget their DNS server immediately even if you've seen that only once! Don't use the IP setting to use the DNS server from DHCP, and configure your IP parameters (in your router if possible, otherwise on the device hosting your browwer) by setting the IP addresses of a trustable DNS provider, even if your own IP address/mask Intenet gateway remains configured by DHCP. verdy_p (talk) 21:50, 20 July 2014 (UTC)