Since the backend work is all done here, I am therefore resolving this task.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 2 2018
Jul 22 2018
Jun 27 2018
May 15 2018
Looking at implementing variables, could use json_encode() to store in MySQL then using json_decode(), manipulate and retrieve as needed. Though how to manage it with respect to all.dblist will be interesting.
May 11 2018
Bolding taking.
Extensions can now be managed (in theory) by using Special:ManageWiki.
Apr 2 2018
Going to mark this as resolved as I have just published a base extension which will begin to replace this extension.
Apr 1 2018
Mar 19 2018
In T194#53864, @John wrote:That’s the sole purpose of this task/project.
Mar 17 2018
That’s the sole purpose of this task/project.
Yes. I don't mean raw text. I mean checkboxes which are directly applied to the LS. Give full power of LS to wiki admin, but with safety layer.
Direct editing of LS would be difficult to do properly. The most I'd say could be done would be a series of checkboxes, instead of direct code editing. As otherwise, incorrect code or data leaks are likely to occur. The way we have in mind would be both user-friendly and safe.
my suggestion was merged to this task. But maybe different.
Mar 16 2018
Jan 18 2018
In T218#49631, @MacFan4000 wrote:https://phabricator.wikimedia.org/T140941 is a task for making SiteMAtrix even less WMF specific.
https://phabricator.wikimedia.org/T140941 is a task for making SiteMAtrix even less WMF specific.
Jan 1 2018
Dec 31 2017
Dec 30 2017
Dec 23 2017
Dec 6 2017
Nov 27 2017
Oct 29 2017
@labster Any updates? Do you think you'll be able to work on this sometime soon?
Sep 14 2017
Sep 1 2017
This is for Semantic MW, but it is an interesting example for what we could do: https://www.mediawiki.org/wiki/Extension:Semantic_Drilldown
Aug 29 2017
Puppet only manages stuff in puppet anyway so this can't be in puppet.
@labster I didn't mean "easy", but I meant if, you would do one setting, like "wgLogo" adding all the rest would be trivial (just copy it and replace the values) but of course programming the initial code would not be close to easy.
Aug 28 2017
On thinking about it, we can't have a single CDB for all of the wikis, because CDB files are immutable. I keep thinking it's like BerkeleyDB or something. I still feel like serialized blobs should be faster, because there's less overhead for something we'll just slurp into memory. (CDB is still a better option for LC, because you only need a few values for each request, not the whole thing.)
If we could only just get the CDB file issue sorted out and configured, applying the rest should be easy. The priority is for "the developers" (@Southparkfan, @labster) to sort out this issue.
Aug 22 2017
@labster that is probably. It's better to have all values for every request, but we need to be sure there is no negative performance impact.
Aug 20 2017
@Southparkfan this still needs an answer.
Aug 13 2017
Tasks that go on for ever and ever are bad.
Jul 24 2017
It was unintentional. But anyway, doubt it'll be started in this goal period.
Why remove the goal?
https://meta.miraheze.org/wiki/Tech:Projects/Miraheze_Wiki_List I wrote this up for GSOC a while ago.
It would be nice to have a place where wikis are sorted into topics, or something. It's sad to see many wikis with good content, but only one editor.. I'm sure if other users interested in the topic knew about it, they would contribute
Jul 21 2017
More wikis (also in deleted.dblist) can now be dropped.
dragonwiki dsiguidewiki elo131wiki englishlanguagewikiwiki evlerwiki fcswiki filowiki fluxwiki h2751903wiki hendrickswiki hivemindwiki hrodrwiki humanumwiki jakeperswiki joongs14wiki juliesnoteswiki lgproduktsupportwiki lucilekbtwiki minecraftaddonswiki mylogicwiki mywiki ndnwiki oneclanwiki orbiswikiwiki rimworldwiki modelusgovwiki tufuswiki cosmoswiki
Jul 18 2017
libertywiki dump is on /home/revi. It can be dropped, though it can wait until I provide a new list.
@revi needs to act on libertywiki.
Jul 16 2017
dropped:
teachingsecondswiki telegramvtwiki tennisdbwiki testrbcmdoewiki thamilwiki theseabeneathwikki tiddlywikiwiki tumblenetwiki videogameswiki vifakswiki vvwiki warbinwiki wcwiki weeglifewiki wethepediawiki wijoumedwiki wikislandswiki wikixrlianwiki xyzwiki yourovisionwiki zaffwltestwiki zonwiki zuersnetwiki zvtwiki wiki1776wiki 17huberkwiki 2l1v3swiki 5awiki adwiki aevumkathwiki anatoruswiki anet3dwiki asellwiki ashishwiki boss429wiki buswikiwiki casualtywiki cats11thstreetwiki cerhisdevwiki chgkirkwiki citywiki criptanawiki csstestwiki datawiki daudtwikiwiki dh8257wiki dndwiki nationstateswiki conworldwiki
not dropped:
libertywiki
I have a question about using CDB files. Assuming that we'll have to load every value in the configuration to process a request, is there a reason to use a key-value store at all? If we need to iterate through all of the keys in the file, why not just store a serialized array and just load that file? Or have a CDB for all the wikis, mapped as ( wikiwiki => [ serialized settings ] )?
Jul 10 2017
already dropped (before I tried to):
reriawiki
already dropped (before I tried to):
metaauntonomywiki
In T1987#37042, @revi wrote:Can I have a dump of libertywiki (private)? I made that wiki in the past, and would like a dump (if possible).
Can I have a dump of libertywiki (private)? I made that wiki in the past, and would like a dump (if possible).
Jul 9 2017
Hello! This ManageWiki is very handy and I cannot wait to see the features in store. I would just like to make a few suggestions about the ManageWiki form.
List of wikis to be deleted currently:
Jul 1 2017
May 20 2017
May 6 2017
May 3 2017
May 2 2017
Great! Now, where would you change the config so that on WikiCanada the managewiki userright is restricted to the "founder" group? I'd assume overrides, but I'm just being sure
Yes.
So does this mean that managewiki-restricted will no longer be required to change public/private settings?
managewiki-restricted exists to keep some settings solely for sysadmins, so I'm going to say no. At the minute, "public/private" is a side affect and 100% not the intended use of it.
This is legacy and it's currently undecided if this is a smart idea. It is up for discussion but it has been brought up that people can unintentionally (or intentionally) make their wiki public and then blame and put liability on Miraheze.
In T194#32415, @Amanda wrote:
- The Special:ManageWiki page does not contain settings for user groups/extensions yet
This still requires a lot of work and is 100% dependent on SPF. We reached a point where the shell was there that it only required a little bit of effort to deploy it globally. There is still a lot of come but his time restraints are unfortunately quite high.
@John Currently I've noticed the following:
Been looked over and okay'd by labster and ndkilla so will enable globally shortly.
I've made some changes to ManageWiki:
- metawiki is classed as a GlobalWiki and can change configuration of all wikis;
- each wiki (where ManageWiki is enabled) is able to change its own configuration only;
- changed wfGetDB to wfGetLB so it works with our multi-database setup.
Apr 22 2017
https://www.mediawiki.org/wiki/Extension:External_Data#.23get_db_data_-_retrieve_data_from_a_database - this might be interesting
I was also thinking that for this we could add a special page called Special:WikiStats where users can search for how many closed wikis there are, how many open, what different languages there are, etc instead of a sysadmin having to provide this data.
Apr 18 2017
@Amanda Obviously if this task is still here it has not been completed. The page is there because SPF added it for some reason, but that does not mean it is operational yet. Also it is not a "technical error" it is just not actually enabled on wikis other than Meta and and Extload.
Apr 17 2017
Has this been completed yet? On WikiCanada I noticed that there is a Special:ManageWiki page but accessing it throws an internal technical error.
Jan 8 2017
Looks like @NDKilla got a new cert working. FYI, it was always possible, and still is, to visit the site using https://test.miraheze.org/wiki/Main_Page
Anything else redirects to publictestwiki.com
Certificate expired. Site is completely down and inaccesible due to HSTS. If cert is not renewed today I will temporarily make it go back to test.miraheze.org .
This is expiring today - important to fix ASAP.
Update @NDKilla? publictestwiki.com is throwing NET::ERR_CERT_DATE_INVALID
Jan 1 2017
It was worked on in that time so it's really for tracking.
Why is the old project goal still here?
Dec 31 2016
Adopted and added to Special:CreateAccount
Please open a new ticket or go to wiki, as your question is unrelated to implementing TOS/Privacy Policy/Contents Policy/...
@DeltaQuad The second link tells you what system messages are used where on each page. The idea is that you now know which system message(s) you would want to edit to include the text.
No, what I wanted to do was make a PR for the requested link to the new polices. That's why I was asking where the configuration was located. BTW, @Void that second page you linked doesn't have an "edit" option, so no changes can be made to it via that interface.