| Revision as of 23:53, 11 September 2022 editNaomiAmethyst (talk | contribs)Edit filter managers, Extended confirmed users, Rollbackers, Template editors6,269 editsm →Did I break the ClueBot III archiving?: Add note about updating the docs.← Previous edit | Revision as of 23:53, 11 September 2022 edit undoAndreJustAndre (talk | contribs)Extended confirmed users40,404 edits →Did I break the ClueBot III archiving?: ReplyTag: ReplyNext edit → | ||
| Line 54: | Line 54: | ||
| :If this solves the problem, we should update the documentation to note that only a subpage of the page being archived is valid for the archiveprefix. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 18:35, 11 September 2022 (UTC) | :If this solves the problem, we should update the documentation to note that only a subpage of the page being archived is valid for the archiveprefix. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 18:35, 11 September 2022 (UTC) | ||
| ::ClueBot III indeed only allows archiving to subpages. It's to prevent against people from copying the archival configuration template verbatim and ending up with two unrelated pages being archived to one set of archives. If it isn't a subpage, it'll pick the default <tt>{{subst|FULLPAGENAME}}/Archives/</tt>. This is touched on in the ] of <tt>archiveprefix</tt> ("This parameter must be set to a fully qualified page name '''under the page you wish to archive'''.") and later under the optional <tt>key</tt> parameter ("The value of this parameter must match an internally generated key in order for the archives to be stored anywhere other than as subpages of the page being archived."), but could definitely be better explained. Perhaps you'd like to have a go at ]? The <tt>key</tt> parameter was designed to support more complex archive setups for bigger noticeboards, but was never really used because generating a key has to be done by me or someone else with direct access to the running bot's process, and only really useful in extremely narrow use-cases. -- ]<sup>(]|]|])</sup> 23:50, 11 September 2022 (UTC) | ::ClueBot III indeed only allows archiving to subpages. It's to prevent against people from copying the archival configuration template verbatim and ending up with two unrelated pages being archived to one set of archives. If it isn't a subpage, it'll pick the default <tt>{{subst|FULLPAGENAME}}/Archives/</tt>. This is touched on in the ] of <tt>archiveprefix</tt> ("This parameter must be set to a fully qualified page name '''under the page you wish to archive'''.") and later under the optional <tt>key</tt> parameter ("The value of this parameter must match an internally generated key in order for the archives to be stored anywhere other than as subpages of the page being archived."), but could definitely be better explained. Perhaps you'd like to have a go at ]? The <tt>key</tt> parameter was designed to support more complex archive setups for bigger noticeboards, but was never really used because generating a key has to be done by me or someone else with direct access to the running bot's process, and only really useful in extremely narrow use-cases. -- ]<sup>(]|]|])</sup> 23:50, 11 September 2022 (UTC) | ||
| :::Thanks for the info. Yes, I saw the key thing and thought about whether that would solve the problem. And I guess the documentation is accurate too, I just didn't understand it. Waiting to see if everything is fixed now that we mass-renamed the pages to match that default. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 23:53, 11 September 2022 (UTC) | |||
Revision as of 23:53, 11 September 2022
| Skip to table of contents |
False positives and false negativesIf you believe that ClueBot NG has mistakenly identified a good edit as vandalism, please follow the directions in the warning it gave or click here. Please do not report it on this talk page. It takes less time to report the case to the correct location, and we can handle it more effectively there.If you believe that ClueBot NG has missed an edit that is vandalism, again do not report it here. ClueBot is unable to catch all vandalism. Just revert the edit and warn the editor. ClueBot NG Links!Report False Positives • Frequently Asked Questions Purpose of this PageThis page is for comments on or questions about the ClueBots.
The current status of ClueBot NG is: Running
The current status of ClueBot III is: Running
Praise should go on the praise page. Barnstars and other awards should go on the awards page.
Use the "new section" button at the top of this page to add a new section. Use the link above each section to edit that section.
This page is automatically archived by ClueBot III.
The ClueBots' owner or someone else who knows the answer to your question will reply on this page.
| ClueBots | |
|---|---|
| ClueBot NG/Anti-vandalism · ClueBot II/ClueBot Script |  |
| ClueBot III/Archive · Talk page for all ClueBots |
 | Beware! This user's talk page is monitored by talk page watchers. Some of them even talk back. |
Did I break the ClueBot III archiving?
I finally moved my manual archives to ClueBot the other day and I was feeling pretty proud of myself for getting it to work. However, it has conducted its first run of archiving and it seems to have disregarded my archiveprefix and broken its previous good work. Anyone can help or point me where I need to go? Andre🚐 14:47, 1 September 2022 (UTC)
- It's still not working right sadly. It ignores my archiveprefix and tries to archive to the wrong page. Andre🚐 14:09, 7 September 2022 (UTC)
- There are a couple of things I spotted. The first one, which I don't think is the reason, is the format parameter documentation reports a space in it like, format= %%i. The second is that you are hard coding your archive prefix to your main user page not your talk page. I would recommend trying archiveprefix={{subst:FULLPAGENAME}}/Archive as written in the documentation so that it automatically captures your talk page. Hope that helps. Inomyabcs (talk) 01:05, 11 September 2022 (UTC)
- Hi, I'm sorry, this isn't going to solve the problem. The issue is that I already have 54 talk page archive pages with the format User:Andrevan/Archive54 so it's correct to those to have the %%i without a space and to have it be under my main User page, at least, it has been able to generate the index User:ClueBot III/Master Detailed Indices/User talk:Andrevan. But actually, the problem I have now is that the bot is creating the User talk:Andrevan/Archives/1 page almost like the archiveprefix is being ignored. Andre🚐 01:08, 11 September 2022 (UTC)
- OK, thanks for the clarification. I wonder if it is trying to prevent overriding of your already existing archive pages. Your start page number is 1, but maybe it should start at 55. Inomyabcs (talk) 01:13, 11 September 2022 (UTC)
- Hm, OK, I'll try that. Andre🚐 01:24, 11 September 2022 (UTC)
- That didn't work. The bot created User talk:Andrevan/Archives/55 Andre🚐 16:23, 11 September 2022 (UTC)
- Oh. Sorry that didn't work out. The code for the archive bot is a little beyond my ability to try and see where the issue is. I hope someone else is able to help narrow this down. Good luck. Inomyabcs (talk) 16:57, 11 September 2022 (UTC)
- Thanks for trying to help anyway. I'm asking if someone on AWB/Tasks with pagemover can mass move my old archives to the right form. Andre🚐 17:00, 11 September 2022 (UTC)
- Oh. Sorry that didn't work out. The code for the archive bot is a little beyond my ability to try and see where the issue is. I hope someone else is able to help narrow this down. Good luck. Inomyabcs (talk) 16:57, 11 September 2022 (UTC)
- That didn't work. The bot created User talk:Andrevan/Archives/55 Andre🚐 16:23, 11 September 2022 (UTC)
- Hm, OK, I'll try that. Andre🚐 01:24, 11 September 2022 (UTC)
- OK, thanks for the clarification. I wonder if it is trying to prevent overriding of your already existing archive pages. Your start page number is 1, but maybe it should start at 55. Inomyabcs (talk) 01:13, 11 September 2022 (UTC)
- Hi, I'm sorry, this isn't going to solve the problem. The issue is that I already have 54 talk page archive pages with the format User:Andrevan/Archive54 so it's correct to those to have the %%i without a space and to have it be under my main User page, at least, it has been able to generate the index User:ClueBot III/Master Detailed Indices/User talk:Andrevan. But actually, the problem I have now is that the bot is creating the User talk:Andrevan/Archives/1 page almost like the archiveprefix is being ignored. Andre🚐 01:08, 11 September 2022 (UTC)
- There are a couple of things I spotted. The first one, which I don't think is the reason, is the format parameter documentation reports a space in it like, format= %%i. The second is that you are hard coding your archive prefix to your main user page not your talk page. I would recommend trying archiveprefix={{subst:FULLPAGENAME}}/Archive as written in the documentation so that it automatically captures your talk page. Hope that helps. Inomyabcs (talk) 01:05, 11 September 2022 (UTC)
- If this solves the problem, we should update the documentation to note that only a subpage of the page being archived is valid for the archiveprefix. Andre🚐 18:35, 11 September 2022 (UTC)
- ClueBot III indeed only allows archiving to subpages. It's to prevent against people from copying the archival configuration template verbatim and ending up with two unrelated pages being archived to one set of archives. If it isn't a subpage, it'll pick the default {{subst:FULLPAGENAME}}/Archives/. This is touched on in the documentation of archiveprefix ("This parameter must be set to a fully qualified page name under the page you wish to archive.") and later under the optional key parameter ("The value of this parameter must match an internally generated key in order for the archives to be stored anywhere other than as subpages of the page being archived."), but could definitely be better explained. Perhaps you'd like to have a go at updating the docs? The key parameter was designed to support more complex archive setups for bigger noticeboards, but was never really used because generating a key has to be done by me or someone else with direct access to the running bot's process, and only really useful in extremely narrow use-cases. -- Cobi 23:50, 11 September 2022 (UTC)
- Thanks for the info. Yes, I saw the key thing and thought about whether that would solve the problem. And I guess the documentation is accurate too, I just didn't understand it. Waiting to see if everything is fixed now that we mass-renamed the pages to match that default. Andre🚐 23:53, 11 September 2022 (UTC)
- ClueBot III indeed only allows archiving to subpages. It's to prevent against people from copying the archival configuration template verbatim and ending up with two unrelated pages being archived to one set of archives. If it isn't a subpage, it'll pick the default {{subst:FULLPAGENAME}}/Archives/. This is touched on in the documentation of archiveprefix ("This parameter must be set to a fully qualified page name under the page you wish to archive.") and later under the optional key parameter ("The value of this parameter must match an internally generated key in order for the archives to be stored anywhere other than as subpages of the page being archived."), but could definitely be better explained. Perhaps you'd like to have a go at updating the docs? The key parameter was designed to support more complex archive setups for bigger noticeboards, but was never really used because generating a key has to be done by me or someone else with direct access to the running bot's process, and only really useful in extremely narrow use-cases. -- Cobi 23:50, 11 September 2022 (UTC)