Thu, Jul 18
Disclaimer - the above works only when viewing the gendered category page. When the page is directly edited or the history page is directly accessed this does not work.
There's the InitializeArticleMaybeRedirect hook in the "root" MediaWiki class that could be used to completely redirect incoming request that match e.g. a certain mapping. This would make it possible to look for page access on gendered category pages and redirect them to the wanted generic form.
Wed, Jul 17
Sounds good and definitely ways to hack ourselves into the system "faking" that certain categories exist.
So manipulating search terms in the backend would be possible. On the front-end side we could obviously use JS to do fancy stuff on category searches, but that might then interfere with different UIs and gadgets.
Tue, Jul 16
For the first number:
For the autosuggestion in the search form MediaWiki mainly uses ApiOpenSearch in the background. This eventually calls completionSearchWithVariants and completionSearchBackend on the according instance of SearchEngine.
So the general search in core is triggered by using searchText/searchTitle on an instance of SearchEngine. The type of instance is set in the corresponding SearchEngineFactory and depends on configuration. ( by default it's some type of SearchDatabase with CirrusSearch installed it's CirrusSearch.
Mon, Jul 15
Fri, Jul 12
For instance, are there some aspects that should be tackled first?
Just from quickly looking over it:
Tue, Jul 9
Mon, Jul 8
Fri, Jul 5
Thu, Jul 4
Wed, Jul 3
Another file to test this with
This can be tested on beta now
Tue, Jul 2
Mon, Jul 1
So last message I'm missing:
Fri, Jun 28
Just to update this task with the things discussed in the daily today. - The new version of Wikidiff2 will only be deployed to PHP7 servers since HVVM servers will be EOL in the upcoming weeks. The impacts of the new version could therefore not be validate when PHP7 was not explicitly requested.
Just wanted to mention here, that this also does not work when AdvancedSearch is "disabled" by deactivating JS. So this is probably not a problem, that is specific to the AdvancedSearch UI and probably lies further down.