LQT pages have been converted to Flow on OfficeWiki! We had to stop and then restart the conversion process, which caused some unexpected bugs -- but we figured it out, and the LQT threads are Flowified now. The next step is moving wiki talk pages to archives, which we'll start next week with the project talk namespace.
*Erik*:
Working on LQT conversion -- individual imports worked for headers and topics. The issue was: we moved the LQT pages out of the way, but we had to stop the process partway through. Rolling the changes back didn't move those pages back, so things got confusing when we tried to run the script again. The templates in the headers need to be updated. One good thing -- Nick is still subscribed to the LQT threads he was subscribed to!
Also working on L2: Analytics queries from existing data. Wrote most of the queries, they're probably correct. Needs to be tested. Planning to put that into Limn today, see what comes out.
*Matthias*:
Today - worked out more pieces of CirrusSearch maintenance script, 3 new patches up for Nik to look at. (We may not be able to reach him until after Thanksgiving.) Tomorrow -- continue that, and do some code review -- take care of Erik's backlog.
Matt is off today for Thanksgiving weekend, and all the Americans will be out Thursday and Friday. Team members in Canada, Belgium and Spain will have to fend for themselves.
On 11/26/2014 01:59 PM, Danny Horn wrote:
The issue was: we moved the LQT pages out of the way, but we had to stop the process partway through.
What required the process to stop/restart originally?
Matt Flaschen
there were two different bugs which caused us to have to revert then restart the process. (should also note the process was designed for restarting from where it stopped, but we didn't take into account undoing the previous conversion then starting from the beginning).
1. We were using a FauxRequest passed into ApiMain to query liquid threads. While this works fine on normal wikis, for office wiki we needed to provide a user to get around the read restriction 2. Upon creating a RequestContext and attaching the appropriate User and FauxRequest to it we would pass the basic wiki level security checks on officewiki, but LQT was doing its internal checks against $wgUser instead of the User object passed into ApiMain.
Fixed 1 in Flow and 2 in LQT.
Erik B.