[04:52:35] q [08:51:15] Hi [08:51:31] I have questions about Media Viewer [15:34:08] Hi All, currently setting up a wiki and when I download the LocalSettings.php it save as `index.php?localsettings=1` If I move the file to where LocalSettings.php should be the wiki act as if there is no config. How can i solve that ? Thanks [15:50:44] Just rename the file to LocalSettings.php [18:52:15] is there an easy way to export/import a specific list of pages from a wiki, but also pull in the images and the history (metadata, old revisions) for those images? [18:52:48] (I am trying to break up a monolithic wiki into multiple wikis) [19:04:53] hey jorisdarlington [19:05:04] how's it going ? [19:06:21] fdarling: Not really... At least, not without using 3rd party tools. MW will export the file history pages, but not the files themselves [19:06:21] NickServ [19:07:29] Reedy: using the file history import/export, can I somehow manually upload the image/file so it's effectively migrated? At least on a file-by-file basis? [19:07:58] You can upload the files to the new wiki in the same way you'd upload files normally [19:08:08] I guess it depends how many you're wanting to move [19:15:35] NickServ [19:18:17] #freenode [19:21:54] Reedy: If I upload a file normally, it'll have have a brand new file history and upload date. How do I replace that "metadata" with the history from the other wiki? [19:22:08] Reedy: does the import feature have the ability to overwrite a page? [19:23:20] It can overwrite, yes [19:23:32] I don't think anyone usually cares about the files exact upload history/date [19:36:28] I wonder if the file part of imports even works correctly [19:37:03] Like given that wikimedia doesnt support exporting the files in xml format, does anyone even test that? [20:11:52] I have an RL module that has CSS and JS. It depends on another module, also with syles and JS. When I call \ParserOutput::addModules, the JS of both modules is loaded fine, but the styles of the dependency are ignored. Any advice? [20:45:04] FoxT: i don't see how that could happen… are you absolutely positive that the styles in the dependency module actually work as expected? can you add something silly there like `body { background: red; }` and confirm that these styles don't load? [20:45:40] (also, i've once spent a long time debugging a style loading issue only to find out i didn't list the CSS file in the module definition) [20:46:11] If I add the style file directly to the depending module it loads fine. [20:48:32] Hmm. Just tried the red background and guess what... [20:51:37] Ok, I think this is actually a probem with some other extension using the same name for a similar (but different) module. [20:51:54] If I change the module name, everything works fine. [20:52:01] Thanks for the help!