[04:42:59] is it possible to deploy specific versions of extensions on specific wikis [04:43:01] on bets [04:43:03] beta [06:01:19] Not on specific wikis. We can only have one version installed per MW version. But we can pin that to a certain commit or something. [11:00:45] Would be good to see that in the future as something that's possible through managewiki [11:31:41] I don't think that would work well with the localization cache [12:54:37] would be a headache to maintain from a security perspective as well [13:35:35] [1/2] I'm gonna do a bit more expansion on the usage of Bucket, as well as trying to expand on PetraMagna's `Bucket/put` to make migration from Cargo easier [13:35:35] [2/2] There's still a problem with https://exttest.mirabeta.org/wiki/Bucket:Bucket_issues not existing. it's meant to be defined at https://github.com/weirdgloop/mediawiki-extensions-Bucket/blob/REL1_45/sql/issues-table.sql . [13:38:09] The migration needs to be added to the `install` section of the extension in ManageWikiExtensions [13:49:26] I'm not sure what you mean by this [13:51:20] [1/8] I'm not sure which branch you're running on beta so I can't look at what you currently have, but you need to specify the SQL files that should be run, similarly to e.g. [13:51:20] [2/8] ```php [13:51:20] [3/8] 'install' => [ [13:51:21] [4/8] 'sql' => [ [13:51:21] [5/8] '' => 'extensions/', [13:51:21] [6/8] ], [13:51:22] [7/8] ], [13:51:22] [8/8] ``` [13:52:10] [1/7] I already have ```php [13:52:10] [2/7] 'install' => [ [13:52:10] [3/7] 'sql' => [ [13:52:11] [4/7] 'bucket_pages' => 'extensions/Bucket/sql/tables-generated.sql', [13:52:11] [5/7] 'bucket_schemas' => 'extensions/Bucket/sql/tables-generated.sql', [13:52:11] [6/7] 'bucket__bucket_issues' => 'extensions/Bucket/sql/issues-table.sql', [13:52:11] [7/7] ],``` [13:52:31] Then the table should exist [13:52:47] the table exists but the bucket doesn't [13:53:08] my theory is it autocreates when there actually is an issue but idk shit [13:53:23] nah I deliberately made an issue and it didn't show up [13:53:30] damn [13:53:40] maybe try running createInitialSchemaForBucketIssues on installation [13:53:48] [13:54:17] ugh I guess it would need to be extracted into a maintenance scrip [13:54:36] [1/17] The table does exist though. [13:54:36] [2/17] ``` [13:54:37] [3/17] petramagna@test151 ~> sql exttestwikibeta [13:54:37] [4/17] Will execute: [13:54:37] [5/17] sudo -u www-data php /srv/mediawiki/1.45/maintenance/run.php sql --wiki=exttestwikibeta [13:54:37] [6/17] > describe bucket__bucket_issues; [13:54:38] [7/17] stdClass Object [13:54:38] [8/17] ( [13:54:38] [9/17] [Field] => _page_id [13:54:39] [10/17] [Type] => int(10) unsigned [13:54:39] [11/17] [Null] => NO [13:54:40] [12/17] [Key] => PRI [13:54:40] [13/17] [Default] => [13:54:41] [14/17] [Extra] => [13:54:41] [15/17] ) [13:54:42] [16/17] ... [13:54:42] [17/17] ``` [13:54:43] I wonder if you could run update.php just for Bucket, that would be easier [13:54:45] yes but the rest of the migration is not applied [13:54:54] there's a PHP part to it [13:55:00] Oh never mind then [13:56:49] sending wwr to the mirahezemagic mines [13:58:23] ideally it should be fixed upstream so we don't have to duplicate the code and update it every time upstream adds it [13:59:38] or we run update.php but scope it if that's possible [14:00:49] doesnt look like it is [14:01:21] ugh [14:01:36] that should really be supported [14:01:47] doesn't seem to be impossible based on DatabaseUpdater.php but everything is private [14:01:58] but that isn't feasible as a solution in this case [14:02:32] i was rooting for wg so much :( and then they pull a grant all on me :( [14:02:55] let's use a local patch for now that turns it into a maintenance script, and I'll see if I can upstream it [14:04:07] the issues table doesn't affect core functionality so not in a huge hurry with that, should rather focus on testing every other functionality [14:04:29] im also on vacation apparently [14:04:58] I can do that, just wanted to make sure the installation wasn't completely borked [14:05:05] vacation from what [14:05:13] okay I'm gonna fix it upstream [14:05:27] my school is on break therefore so am i [15:21:24] localization cache pisses me off too [15:21:39] I have to have a separate one for each wiki rn because I haven't figured it out yet and it's not worth my time [15:38:08] hi tech ! a wiki of mine recently switched domains and we cant seem to place the new site's sitemap into google search console due to the sitemap still using the old domain. is there a fix or do i need to wait for a week or so [15:39:10] (superstarracerswiki, superblox64wiki, ablocksjourneywiki) [16:07:24] iirc sitemaps are regenerated weekly [16:46:18] You can [16:48:27] you just gotta create your own instance of the HookContainer, load the schema update hook onto the container, then override the hook container on a fresh instance of DatabaseUpdater and voila [20:12:10] [1/2] looks like my minimal Bucket example works as expected. now onto some more complex things [20:12:10] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1478485154799550514/image.png?ex=69a89219&is=69a74099&hm=34e018d602f721790a3fb243d5f2a60840e6d8da1c2f90742098beb3a9183637& [20:33:05] Niiiiiice [20:33:24] Bucket - coming soon to a MH near you [20:34:07] we are borrowing Weird Gloop's bucket extension aren't we [20:53:26] Weird Gloop are the developers, yes