@Esanders My guess is that the[[ https://www.mediawiki.org/wiki/VisualEditor/Citation_tool | visual editor citation tool ]] will not be supported in current wikitext editor which will be around least couple of years even if not longer and i think that the main value of Proveit is to get new stuff (like support for autogenerated refs) to current editor. Also in coder point of view the citoid is backend and Proveit editing interface and most likely Proveit when it is developed more will be using Citoid too for getting data for references. Least this is my guess.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 10 2016
{ "@metadata": { "authors": [ "Felipe Schenone" ] }, "proveit-list-tab": "Viitteet ($1)", "proveit-add-tab": "Lisää", "proveit-reference-name-label": "Viitteen nimi", "proveit-reference-content-label": "Viitteen sisältö", "proveit-reference-template-label": "Viitemalline", "proveit-cite-button": "Viittaa", "proveit-remove-button": "Poista viite", "proveit-insert-button": "Lisää viite", "proveit-update-button": "Päivitä viite", "proveit-prompt-name": "Viite tarvitsee nimen toimiakseen:", "proveit-confirm-remove": "Oletko varma, että haluat poistaa viitteen?", "proveit-no-template": "Viitemalline puuttuu", "proveit-no-references": "Ilman viitemallinetta" }
Nov 4 2016
Hi, thank you for fast response and November 7 is fine.
Sep 30 2016
I made test page for this and it looks like that Alex Monk is correct.
Sep 26 2016
AlexMonk-WMF, Can you confirm if i understand correctly. TemplateData aliases should work so that if there is in TemplateData parameter {{{Title}}} with alias {{{title}}} and it is used in article like this:
Sep 21 2016
Sep 8 2016
Thank you, it seems to be working as planned.
Sep 7 2016
And still one suggested change. I think that the values should be key => value pairs as the other values in groupOverrides are (?)
Sep 6 2016
@MarcoAurelio, currently we don't have in fiwiki plans to remove FR.
It looks fine to me and thanks for the fast response.
Hmm, I think that there is still old autopromote for patroller group which should be removed at InitialiseSettings.php?
Aug 12 2016
Jul 13 2016
Hmmph, in context of current edithaton it seems that it would be very nice that in case of edit conflict system would save the revision to log (like Abuse Filter log) or to some special page like sandbox where it could be recovered. It should not be too hard to implemet afaik and this would fix some saddest feelings which users will get from edit conflict and losing the content. (in this case back button didn't save the day)
Jun 19 2016
Jun 1 2016
I checked that the change doesn't break fiwikis "mahdollisesti sotkua" filter so it can be removed from the to be fixed list too.
May 20 2016
Eg. user is viewing old version (stable) of the page, but the edit links are pointing to the latest version. Normally when you are looking the old version of the page then edit links are pointing to that version and there is warning that you are gonna to edit the old version.
Aug 19 2015
Tested with enwiki (https://en.wikipedia.org/wiki/Special:Upload) , Firefox 40.0 and file PlotEditsTrendsFI_2015-06-10-bar.png
.- Settings were in defaults (before testing i reset my settings with "Restore all default settings (in all sections)" in preferences and emptied my common.js, common.css, vector.js and vector.css files.)
- When i select the file with "browse" button next to text "Source filename" the selected filename will replace the "No file selected text" and spinner will start.
- Spinner newer stops.
- If I ignore the spinner and just continue it seems that file will be uploaded correctly
- There is no errors in javascript-console.
May 17 2015
Dec 11 2014
Hmm, can somebody push this to the higher priority of Foundation tech guys? Most likely this is a bug in server side so user's cannot do anything without access to server logs. However currently this is also repeatable so somebody should least take debug information from server side to the ticket.
Dec 10 2014
Edited the description because problem seems to be user account specific. Person can fail with one user_name with error 503 but successfully login with another with same computer.