Hello,
I wonder if some of you could maybe take a look at https://phabricator.wikimedia.org/T119791 and the archivebot.py script in general?
It'd be good if the script supported some other functions such as different n=x archiving and immediate archiving if a template is there in a thread.
Best regards, M.
Hi,I should also use a modified version of an older archivebot.py because the "official" version can not handle cases such a chapter marked with a template (For example in hungarian: Sablon:függöben), which "to be continue" and should not be archived. See the source from the line #Postpone archiving if thread's marked with {{fuggoben}} here: http://tools.wmflabs.org/ato/archivebot_hu.py.txtor here:https://hu.wikipedia.org/wiki/Szerkeszt%C5%91:Atobot/archivebot_hu.py Would be nice to implement something similar in to the official version too. Before someone ask, unfortunately I do not know python enough to solve things like this.Regards, Attila MarcoAurelio strigiwm@gmail.com írta:
Hello, I wonder if some of you could maybe take a look at https://phabricator.wikimedia.org/T119791 and the archivebot.py script in general? It'd be good if the script supported some other functions such as different n=x archiving and immediate archiving if a template is there in a thread. Best regards, M.Hello,I wonder if some of you could maybe take a look at https://phabricator.wikimedia.org/T119791 and the archivebot.py script in general?It'd be good if the script supported some other functions such as different n=x archiving and immediate archiving if a template is there in a thread.Best regards, M. _______________________________________________ pywikibot mailing list pywikibot@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikibot
Hi,
Maybe configure the template to substitute the text and a timestamp with a far future, like 23:59, 31 December 2099 (UTC) (or same for your language)? Any reason you can't do that?
That's what enwiki's DNAU template essentially does. -- Yongmin Sent from my iPhone https://wp.revi.blog Text licensed under CC BY ND 2.0 KR Please note that this address is list-only address and any non-mailing list mails will be treated as spam. Please use https://encrypt.to/0x947f156f16250de39788c3c35b625da5beff197a.
2017. 6. 23. 18:24 ato ato@freemail.hu 작성:
Hi, I should also use a modified version of an older archivebot.py because the "official" version can not handle cases such a chapter marked with a template (For example in hungarian: Sablon:függöben), which "to be continue" and should not be archived.
See the source from the line #Postpone archiving if thread's marked with {{fuggoben}} here:
http://tools.wmflabs.org/ato/archivebot_hu.py.txt or here: https://hu.wikipedia.org/wiki/Szerkeszt%C5%91:Atobot/archivebot_hu.py
Would be nice to implement something similar in to the official version too.
Before someone ask, unfortunately I do not know python enough to solve things like this. Regards,
Attila
MarcoAurelio strigiwm@gmail.com írta: Hello,
I wonder if some of you could maybe take a look at https://phabricator.wikimedia.org/T119791 and the archivebot.py script in general?
It'd be good if the script supported some other functions such as different n=x archiving and immediate archiving if a template is there in a thread.
Best regards, M. Hello,I wonder if some of you could maybe take a look at https://phabricator.wikimedia.org/T119791 and the archivebot.py script in general?It'd be good if the script supported some other functions such as different n=x archiving and immediate archiving if a template is there in a thread.Best regards, M. _______________________________________________ pywikibot mailing list pywikibot@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikibot _______________________________________________ pywikibot mailing list pywikibot@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikibot
2017-06-23 11:59 GMT+02:00 Yongmin H. lists@revi.pe.kr:
Maybe configure the template to substitute the text and a timestamp with a far future, like 23:59, 31 December 2099 (UTC) (or same for your language)? Any reason you can't do that?
That's an ugly workaround. The script should handle it properly, and by that time we can still use the older version.