Unfortantly I am going to have to decline it for privacy reasons.

Hi everyone, I'd like to apologize on my delayed response. Unfortunately I think I will have to take back my request for the time being, I don't think I'll be able to spend any time reviewing extensions, as life/college is getting really busy. I hope in the future that I will have some time, but right now doesn't seem like a good time. I wish everyone the best! Thank you.

Yay! Looks like the screenshot helped. I'm glad I pushed you to look into fixing this. I think the fix you implemented was a reasonable one. Thanks! :)

Yes I do

Also, may I ask why titlekey extension won't work for you? It seems to provide same functionality.

Sync is declined since it's unmaintained. Given this, do you still need the Push extension?

I'm concerned this extension would have a few performance risks, due to the way it queries the DB. I am not outright declining it, but I do think that warrants an extra look before approving

Testing backups:

mysql -S /var/run/mysqld/mysqld.c4.sock -e 'stop slave'

dbbackup1 is replicating all clusters now.

renamed

MariaDB instances became corrupted due to my own fault. Recloning.

Done. Works everywhere. See https://git.io/JtvA3 if I missed anywhere for how to fix.

Thank you very much!

Special:Export can be used to export pages, however, information such as emails will never be able to exported. I'm going to say until/if this ext makes it possible to not allow private info to be exported this will never be installed.

I agree with @Dmehus. Exporting emails will not be possible and unless the extension proposes a way to disable that this will not be possible for privacy reasons.

Stability wise, this is a stable extension, but given that it proposes to export the private e-mail addresses of users, I'm going to say this cannot be done, unless there's a way to disable the exporting of e-mail addresses. If it were just exporting of user pages, this would be fine. Any system administrator may feel free to revert, if in error.

this does not Require any Additional extensions for what I am using it for.

4xx/5xx alert was a user making a lot of requests for content that doesn't exist.

Here is a screenshot of RecentChanges-

All done!

Report made by freenode oper. It acts like a spammer.

Done!

Done!

No response in a few days. Please re-open if you still require this import.

Awesome. Thank you!

In T6714#132228, @LukaIbrisimovic wrote:

I'm afraid I'm going to need your help with this. Currently my name servers are set to "ns1.miraheze.org" and "ns2.miraheze.org".

I had discussion the other day about this here: https://meta.miraheze.org/wiki/User_talk:Reception123#Changing_custom_domain.

If I understood correctly, it was said that I didn't need to change anything with my domain registrar since this could be accomplished by making changes to my domain's zone file, hosted with Miraheze.

If I do need to make changes to name servers, could you point me in the right direction since I don't quite understand https://meta.miraheze.org/wiki/Custom_domains, i.e. I don't understand how to setup multiple subdomains with custom domain.

Thank you!

I'm afraid I'm going to need your help with this. Currently my name servers are set to "ns1.miraheze.org" and "ns2.miraheze.org".

I have added cname, kindly check now.

@LukaIbrisimovic it seems that you have not pointed your domains/subdomains (except www.petrawiki.org which is already connected to a wiki it seems) correctly to Miraheze's servers. Please make sure to read https://meta.miraheze.org/wiki/Custom_domains and let us know when you have pointed your domains to us. Thank you!

Hello, it seems that you have not pointed your new domain correctly to Miraheze's servers. Please make sure to read https://meta.miraheze.org/wiki/Custom_domains and let us know when you have pointed your domain to us. Thank you!

Import completed. Let us know if anything is still missing

In T6716#132207, @RhinosF1 wrote:

You can also have a multilingual wiki using the translate extension.

You can also have a multilingual wiki using the translate extension.

Fixed with https://github.com/miraheze/DataDump/pull/17

In T6716#132203, @Nyl wrote:

So the only possible way to do this is to create a new wiki altogether?

So the only possible way to do this is to create a new wiki altogether?

This can be done from Special:ManageWiki/core on your wiki. Or by selecting another language when requesting a wiki on Special:RequestWiki on meta

https://github.com/miraheze/ManageWiki/pull/226/

In T6699#132194, @Dmehus wrote:

In T6699#132191, @Universal_Omega wrote:

In T6699#132185, @Dmehus wrote:

In T6699#132128, @Universal_Omega wrote:

If you can only generate one dump at a time then why is this needed?

@Universal_Omega Well, that's precisely the issue. Because we can only generate one dump at a time, it causes an issue with having to click the special page "refresh" link at the bottom of the page, which is sub-optimal from the perspective of wanting to generate all three dumps. Moreover, as you noted on T6698, if I'm remembering correctly, the issue with the duplicate log entries is likely related to clicking on that refresh link. So, I'm just saying, let's do away with that rudiamentary refresh link, which was fine when we hacked the extension together, and improve the overall user interface and design. Hope that helps and makes sense.

I mean you can only generate one dump total. Not one dump at a time. Only 1 dump can exist at the same time, of each type. Because you would only have to return back to the page after doing the generation the first time, twice, the effort to do this task may simply not be worth it. In order to do this, DataDump would need a significant rewrite.

Yeah, if a significant rewrite is required, well, that's okay, I'm fine with us triaging this as very low priority, but let's keep it on our radar?

In T6698#132195, @Dmehus wrote:

In T6698#132192, @Universal_Omega wrote:

Interesting I don't see that log entry like that.

Hrm, really? On Vector?

In T6698#132192, @Universal_Omega wrote:

Interesting I don't see that log entry like that.

In T6699#132191, @Universal_Omega wrote:

In T6699#132185, @Dmehus wrote:

In T6699#132128, @Universal_Omega wrote:

If you can only generate one dump at a time then why is this needed?

@Universal_Omega Well, that's precisely the issue. Because we can only generate one dump at a time, it causes an issue with having to click the special page "refresh" link at the bottom of the page, which is sub-optimal from the perspective of wanting to generate all three dumps. Moreover, as you noted on T6698, if I'm remembering correctly, the issue with the duplicate log entries is likely related to clicking on that refresh link. So, I'm just saying, let's do away with that rudiamentary refresh link, which was fine when we hacked the extension together, and improve the overall user interface and design. Hope that helps and makes sense.

I mean you can only generate one dump total. Not one dump at a time. Only 1 dump can exist at the same time, of each type. Because you would only have to return back to the page after doing the generation the first time, twice, the effort to do this task may simply not be worth it. In order to do this, DataDump would need a significant rewrite.

In T6577#132134, @Universal_Omega wrote:

@Dmehus can you please try to give more detail what you mean? They way you describe this task takes it seem like what I said above, and is a bit unclear.

Interesting I don't see that log entry like that.

In T6699#132185, @Dmehus wrote:

In T6699#132128, @Universal_Omega wrote:

If you can only generate one dump at a time then why is this needed?

@Universal_Omega Well, that's precisely the issue. Because we can only generate one dump at a time, it causes an issue with having to click the special page "refresh" link at the bottom of the page, which is sub-optimal from the perspective of wanting to generate all three dumps. Moreover, as you noted on T6698, if I'm remembering correctly, the issue with the duplicate log entries is likely related to clicking on that refresh link. So, I'm just saying, let's do away with that rudiamentary refresh link, which was fine when we hacked the extension together, and improve the overall user interface and design. Hope that helps and makes sense.

@Universal_Omega I'm reopening this task because in reference to: