Wikipedia talk:CommonsTicker

This page is for discussion about the Wikipedia:CommonsTicker page. For techical information on CommonsTicker, go to meta:User:Duesentrieb/CommonsTicker. For urgent (technical) requests, contact de:Benutzer:Duesentrieb. Local contact admin is User:Freshstart.

---

e replication lag we currently see on the toolserver (it's more than a day behind). While I hope this will not happen again in the future, I have been working on improving CommonsTicker so it handles out-of-sync entries gracefully.

I plan to activate a new version of CommonsTicker tonight or tomorrow - so look out for any new problems. Here are the most relevant changes:

• fix handling of out-of-sync records (see above); added "latecomer" parameter to TickerEntry template (may be ignored)

id=377144 like this]. ikimedia.org/w/index.php?title=User%3ADuesentrieb%2FCommonsTicker&diff=377180&oldid=377144 here] for an example that strikes out the entry if status is set to "done".

For the future, I'm planning to let CommonsTicker post warnings to the talk page of articles that use an image das is (about to be) deleted. I'll post another announcement when that feature is ready.

This message was posted automatically by the CommonsTicker bot. For feedback and discussion, please go to meta:User talk:Duesentrieb/CommonsTicker -- CommonsTicker 14:16, 20 June 2006 (UTC)Reply

Hello - sorry, the privious message was a bit broken. Below is a full repost. Sorry again -- CommonsTicker 14:49, 20 June 2006 (UTC)Reply

---

Hi - you may have noticed some problems with CommonsTicker lately - namely, some entries about deletions went missing, and some entries arrived several days late (messing up the date headings for ticker pages using append mode). This is caused by the massive replication lag we currently see on the toolserver (it's more than a day behind). While I hope this will not happen again in the future, I have been working on improving CommonsTicker so it handles out-of-sync entries gracefully.

I plan to activate a new version of CommonsTicker tonight or tomorrow - so look out for any new problems. Here are the most relevant changes:

• fix handling of out-of-sync records (see above); added "latecomer" parameter to TickerEntry template (may be ignored)
• deleted images can be restored now. To reflect this, I have added a "restored" action to CommonsTicker. To use it, you need to change your templates and/or CSS like this.
• for pages in append-mode, there an empty "status" parameter is now handed to the TickerEntry template - this parameter can be set manually to trigger some type of marking or highliting, depending on how you set up your template and CSS. See here for an example that strikes out the entry if status is set to "done".

For the future, I'm planning to let CommonsTicker post warnings to the talk page of articles that use an image das is (about to be) deleted. I'll post another announcement when that feature is ready.

This message was posted automatically by the CommonsTicker bot. For feedback and discussion, please go to meta:User talk:Duesentrieb/CommonsTicker -- CommonsTicker 14:49, 20 June 2006 (UTC)Reply

Hello. A new version of CommonsTicker will be rolled out soon (probably tomorrow). Please have an eye on what the bot is doing, and report any problems to m:User_talk:Duesentrieb/CommonsTicker. Some of the changes are:

• the ticker can now post warnings to the talk page of articles that are using "endangered" images. This is not enabled per default, and you can select for which namespaces it is done. If you want this feature, please request it at m:User:Duesentrieb/CommonsTicker#Change_Requests.
• in append mode, there are now three empty template parameters: status, editor, and notic. The ticker does not use them itself, but you can use them in the TickerEntry template, for example to strike through entries that have been fixed. en:wikinews has already been using this for a while now.
• if the ticker fails to post an update, a warning is posted to your and the ticker's talk page. In append mode, the ticker will also re-try to post the update on the next pass. Until now, failed updates where simply ignored.
• edit summaries become a bit more informative.

I hope these changes will help to make CommonsTicker more used and more useful.

On a related note: you may have noticed that on long pages, entries near the bottom of the page are sometimes not expanded but rendered just as {{TickerEntry}} or similar. This is due to a new limit to template expansion - see bugzilla:7005. To avoid it, try to keep the page short and/or try to simplify the TickerEntry template.

This message was posted automatically by the CommonsTicker bot. For feedback and discussion, please go to meta:User talk:Duesentrieb/CommonsTicker -- CommonsTicker 23:18, 20 August 2006 (UTC)Reply

CommonsTicker was unable to post the latest update to the ticker page. This may happen if there is a temporary problem with the servers or the network, or if the page has grown verry big.

If you use "append" mode, please keep the page reasonably short, perhaps by moving old entries that still need attention to a separate page, which could be included in the main ticker page. Note that CommonsTicker will re-try to post the update on the next run.

If you use "replace" mode, please consider requesting a shorter interval (less days) to watch. CommonsTicker will not try to re-post the update, since it will replace the entire page on the next run anyway.

(this is an automated message) -- CommonsTicker 19:06, 18 September 2006 (UTC)Reply

CommonsTicker was unable to post the latest update to the ticker page. This may happen if there is a temporary problem with the servers or the network, or if the page has grown verry big.

If you use "append" mode, please keep the page reasonably short, perhaps by moving old entries that still need attention to a separate page, which could be included in the main ticker page. Note that CommonsTicker will re-try to post the update on the next run.

If you use "replace" mode, please consider requesting a shorter interval (less days) to watch. CommonsTicker will not try to re-post the update, since it will replace the entire page on the next run anyway.

(this is an automated message) -- CommonsTicker 16:34, 3 October 2006 (UTC)Reply

CommonsTicker was unable to post the latest update to the ticker page. This may happen if there is a temporary problem with the servers or the network, or if the page has grown verry big.

If you use "append" mode, please keep the page reasonably short, perhaps by moving old entries that still need attention to a separate page, which could be included in the main ticker page. Note that CommonsTicker will re-try to post the update on the next run.

If you use "replace" mode, please consider requesting a shorter interval (less days) to watch. CommonsTicker will not try to re-post the update, since it will replace the entire page on the next run anyway.

(this is an automated message) -- CommonsTicker 18:47, 23 November 2006 (UTC)Reply

CommonsTicker was unable to post the latest update to the ticker page. This may happen if there is a temporary problem with the servers or the network, or if the page has grown verry big.

If you use "append" mode, please keep the page reasonably short, perhaps by moving old entries that still need attention to a separate page, which could be included in the main ticker page. Note that CommonsTicker will re-try to post the update on the next run.

If you use "replace" mode, please consider requesting a shorter interval (less days) to watch. CommonsTicker will not try to re-post the update, since it will replace the entire page on the next run anyway.

(this is an automated message) -- CommonsTicker 02:46, 26 November 2006 (UTC)Reply

CommonsTicker was unable to post the latest update to the ticker page. This may happen if there is a temporary problem with the servers or the network, or if the page has grown verry big.

If you use "append" mode, please keep the page reasonably short, perhaps by moving old entries that still need attention to a separate page, which could be included in the main ticker page. Note that CommonsTicker will re-try to post the update on the next run.

If you use "replace" mode, please consider requesting a shorter interval (less days) to watch. CommonsTicker will not try to re-post the update, since it will replace the entire page on the next run anyway.

(this is an automated message) -- CommonsTicker 14:57, 28 November 2006 (UTC)Reply

CommonsTicker was unable to post the latest update to the ticker page. This may happen if there is a temporary problem with the servers or the network, or if the page has grown verry big.

If you use "append" mode, please keep the page reasonably short, perhaps by moving old entries that still need attention to a separate page, which could be included in the main ticker page. Note that CommonsTicker will re-try to post the update on the next run.

If you use "replace" mode, please consider requesting a shorter interval (less days) to watch. CommonsTicker will not try to re-post the update, since it will replace the entire page on the next run anyway.

(this is an automated message) -- CommonsTicker 15:05, 29 November 2006 (UTC)Reply

CommonsTicker was unable to post the latest update to the ticker page. This may happen if there is a temporary problem with the servers or the network, or if the page has grown verry big.

If you use "append" mode, please keep the page reasonably short, perhaps by moving old entries that still need attention to a separate page, which could be included in the main ticker page. Note that CommonsTicker will re-try to post the update on the next run.

If you use "replace" mode, please consider requesting a shorter interval (less days) to watch. CommonsTicker will not try to re-post the update, since it will replace the entire page on the next run anyway.

(this is an automated message) -- CommonsTicker 06:52, 30 November 2006 (UTC)Reply

Hello

As you may have noticed, there have been some problems with CommonsTicker lately:

• first, the toolserver was down. After it was back up, we had to wait for fresh database dumps.
• also, many updates where failing because ticker pages where growing too large. Updates that went through half-way somtimes also caused entries to be posted multiple times, making the problem worse.
• when I tried to improve performance, I introduced a bug that caused the ticker to post trash sometimes. I disabled the ticker again when I was told about it, and I have fixed all effected pages yesterday (I hope I didn't miss any).

To sort this out completely, I have to rewrite parts of CommonsTicker. For now, I will enable the ticker again for most wikis, but not for the ones that where having most trouble - namely de-wikipedia, en-wikinews, eo-wikipedia, es-wikipedia, fr-wikipedia, ja-wikipedia, ru-wikipedia, simple-wikipedia and zh-wikipedia. I'll have to investigate those more closely.

So please keep an eye on CommonsTicker in the next days - if there is any more trouble, please tell me, preferrably on meta:User_talk:Duesentrieb/CommonsTicker.

Regards -- meta:User:Duesentrieb 13:37, 5 January 2007 (UTC)Reply

This message was posted automatically by the CommonsTicker bot. For feedback and discussion, please go to meta:User talk:Duesentrieb/CommonsTicker -- CommonsTicker 13:37, 5 January 2007 (UTC)Reply