Template talk:Retrieved

Function taken from {{Cite web}} and refined by Conrad T. Pino 09:44, 15 October 2007 (UTC)[reply]

This says "Retrieved on" but Template:cite web and Template:cite news just write "Retrieved". Probably easiest to change this but would be better if they were consistent. -- Horkana (talk) 00:32, 7 January 2010 (UTC)[reply]

i agree, consistency would be nice. 65.88.88.127 (talk) 18:44, 7 April 2012 (UTC)[reply]

A new version has been added with documentation. Template Data code and Lua version will follow in the near future, hopefully. 204.19.162.34 (talk) 21:59, 31 August 2024 (UTC)[reply]

Template data added. 204.19.162.34 (talk) 17:29, 2 September 2024 (UTC)[reply]

Implementation note for the current sandbox revision: the deleted parameters registration and subscription (replaced by parameter link-access in sandbox) appear in 3 instances of the production template {{Retrieved}}. 204.19.162.34 (talk) 17:51, 2 September 2024 (UTC)[reply]

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Rewrite of template code and documentation currently in {{Retrieved/sandbox}}, this revision. The diff below compares the current sandbox version with the {{Retrieved}} version imported in the sandbox 5 October 2021, which is functionally the current production version:

diff

Request sync from the sandbox version. Per the section above, only 3 transclusions are affected (by replaced parameters). 65.88.88.201 (talk) 21:49, 3 September 2024 (UTC)[reply]

Note documentation changes. Comparison between production code & sandbox code (current revisions):

diff

Edit Requester from different IP. 50.75.226.250 (talk) 15:34, 4 September 2024 (UTC)[reply]

Clarifying that this revision is the final revision for this edit request. Edit requester from a different IP 65.88.88.47 (talk) 21:49, 6 September 2024 (UTC)[reply]

Code additions (revision), do not foresee more. 64.18.11.7 (talk) 13:32, 12 September 2024 (UTC)[reply]

Not done for now: Please resolve the the failing "5 November" test case. Aaron Liu (talk) 02:01, 7 November 2024 (UTC)[reply]

Thank you for looking into this. The test case you referred to is an error case (the date is missing the year component, an error). The test case below it adds a parameter (|df=dmy) that correctly displays the date in 'day month year' format, using default parser function behavior. 98.7.84.118 (talk) 13:47, 8 November 2024 (UTC)[reply]

Logic revisions added in sequence, with latest revision in the bottom. Changes+additions is green, deletions stricken out. Logic revisions and doc revisions are not necessarily in sync date wise, however the sandbox has the latest revisions of both. 204.19.162.34 (talk) 18:47, 23 October 2024 (UTC)[reply]

Revision

1. If parameter 'access-date'/'accessdate' is missing/mistyped, or there is no access date, display error message, categorize the page and exit.
2. If there is an 'access-info' parameter (paywall access categorizes page) present it unless incorrectly entered; optionally display error message.
3. If there is an 'access-info' and a 'source-info' parameter decide on displaying punctuation+whitespace as 'source-info' leading separator, or just whitespace.
4. Display selected presentation mode; applies globally.
5. If there is no 'access-info' parameter but there is a 'source-info' parameter do not display 'source-info' leading separator.
6. If there is a 'format' parameter and either or both of the two previous parameters display only whitespace as 'format' leading separator ('format' punctuated by parentheses).
7. If there is a 'format' parameter but neither 'access-info' nor 'source-info' parameters, do not display 'format' leading separator.
8. Diplay static text "Retrieved" per the presentation mode; if invalid presentation mode has been entered, do not display mode-related punctuation anywhere; optionally suppress static text with error message.
9. If today's date is autoinserted, display; else
   1. Time-condition the access date to be up to parser's "today" datestamp (practically, less than 2 days in the future).
   2. If there is a date format selected (parameter 'df'), apply it to the access date unless incorrect; if the latter, optionally display error message.
   3. If there is no 'df' parameter, display the access date; if not in an acceptable format display error message and categorize the page.
   4. If access date fails the time condition display error message instead, and categorize the page.
   5. If access date is partial or fails parser date checks display error message instead, and categorize the page.
10. End else; present 'via' parameter if there is one.
11. If there is a 'via' parameter and a 'note' parameter, use whitespace as parameter 'via' trailing separator (link note punctuated by parentheses).
12. If there is a 'note' parameter and no 'via' parameter, present 'note' parameter with whitespace as its leading separator.
13. If there is non-default terminal punctuation display it and exit; else exit.

A tracking category for template errors has not been created as of today (commented out in code, and fake-linked in the doc). 65.88.88.57 (talk) 21:15, 3 October 2024 (UTC)[reply]

Updated (with revision link) following rename of |prepend= to |source-info=. 172.56.166.83 (talk) 18:40, 9 October 2024 (UTC)[reply]

Updated rev. lnk. 71.247.146.98 (talk) 13:06, 15 October 2024 (UTC)[reply]

The following reflects changes to try current-date-substitution in a simple manner. Text in green indicates the change in branch logic (replaced subbranch with branch)

Revision

1. If parameter 'access-date'/'accessdate' is missing/mistyped, or there is no access date, display error message, categorize the page and exit.
2. If there is an 'access-info' parameter (paywall access categorizes page) present it unless incorrectly entered; optionally display error message.
3. If there is an 'access-info' and a 'source-info' parameter decide on displaying punctuation+whitespace as 'source-info' leading separator, or just whitespace.
4. Display selected presentation mode; applies globally.
5. If there is no 'access-info' parameter but there is a 'source-info' parameter do not display 'source-info' leading separator.
6. If there is a 'format' parameter and either or both of the two previous parameters display only whitespace as 'format' leading separator ('format' punctuated by parentheses).
7. If there is a 'format' parameter but neither 'access-info' nor 'source-info' parameters, do not display 'format' leading separator.
8. Diplay static text "Retrieved" per the presentation mode; if invalid presentation mode has been entered, do not display mode-related punctuation anywhere; optionally suppress static text with error message.
9. If today's date is autoinserted, display
10. Else, time-condition the access date to be up to parser's "today" datestamp (practically, less than 2 days in the future).
11. If there is a date format selected (parameter 'df'), apply it to the access date unless incorrect; if the latter, optionally display error message.
12. If there is no 'df' parameter, display the access date; if not in an acceptable format display error message and categorize the page.
13. If access date fails the time condition display error message instead, and categorize the page.
14. If access date is partial or fails parser date checks display error message instead, and categorize the page; end else.
15. Present 'via' parameter if there is one.
16. If there is a 'via' parameter and a 'note' parameter, use whitespace as parameter 'via' trailing separator (link note punctuated by parentheses).
17. If there is a 'note' parameter and no 'via' parameter, present 'note' parameter with whitespace as its leading separator.
18. If there is non-default terminal punctuation display it and exit; else exit.

— Preceding unsigned comment added by 50.75.226.250 (talk) 14:52, 22 October 2024 (UTC)[reply]

Factored Sinebot entry only. 65.88.88.201 (talk) 19:44, 22 October 2024 (UTC)[reply]

Updated revision. 50.74.109.2 (talk) 12:40, 23 October 2024 (UTC)[reply]

Minor code+doc changes

Revision

1. If parameter 'access-date'/'accessdate' is missing/mistyped, or there is no access date, display error message, categorize the page and exit.
2. Else, (wiki)substitute value of 'access-date'/'accessdate'.
3. If there is an 'access-info' parameter (note: paywall access categorizes page) present it unless incorrectly entered; optionally display error message.
4. If there is an 'access-info' and a 'source-info' parameter decide on displaying punctuation+whitespace as 'source-info' leading separator, or just whitespace.
5. Display selected presentation mode; applies globally.
6. If there is no 'access-info' parameter but there is a 'source-info' parameter do not display 'source-info' leading separator.
7. If there is a 'format' parameter and either or both of the two previous parameters display only whitespace as 'format' leading separator ('format' punctuated by parentheses).
8. If there is a 'format' parameter but neither 'access-info' nor 'source-info' parameters, do not display 'format' leading separator.
9. Diplay static text "Retrieved" per the presentation mode; if invalid presentation mode has been entered, do not display mode-related punctuation anywhere; optionally suppress static text with error message.
10. If today's date is autoinserted (wiki)substitute and display; if parameter 'df' also exists ignore it and optionally display related error message.
11. Else, time-condition the access date to be up to parser's "today" datestamp (practically, less than 2 days in the future).
12. If there is a date format selected (parameter 'df'), apply it to the access date unless incorrect; if the latter, optionally display error message.
13. If there is no 'df' parameter, display the access date; if not in an acceptable format display error message and categorize the page.
14. If access date fails the time condition display error message instead, and categorize the page.
15. If access date is partial or fails parser date checks display error message instead, and categorize the page; end else (manually entered date).
16. Present 'via' parameter if there is one.
17. If there is a 'via' parameter and a 'note' parameter, use whitespace as parameter 'via' trailing separator ('note' punctuated by parentheses).
18. If there is a 'note' parameter and no 'via' parameter, present 'note' parameter with whitespace as its leading separator.
19. If there is non-default terminal punctuation display it and exit; else exit. End else (punctuation).
20. End else (parameter 'access-date'/'accessdate').

4.30.91.142 (talk) 00:34, 27 October 2024 (UTC)[reply]

Minor markup edit in code: 'en dash' punctuation mark changed to 'spaced en dash' html escape sequence (x4).

Revision

65.88.88.237 (talk) 21:03, 12 November 2024 (UTC)[reply]

Template code: minor markup edit (x4); hard space between "Retrieved" & access date (x1).

Revision

98.7.84.118 (talk) 14:06, 15 November 2024 (UTC)[reply]

It is requested that an edit be made to the extended-confirmed-protected template at Template:Retrieved. (edit · history · last · links · sandbox · edit sandbox · sandbox history · sandbox last edit · sandbox diff · test cases · transclusion count · protection log) This template must be followed by a complete and specific description of the request, that is, specify what text should be removed and a verbatim copy of the text that should replace it. "Please change X" is not acceptable and will be rejected; the request must be of the form "please change X to Y". The edit may be made by any extended confirmed user. Remember to change the |answered=no parameter to "yes" when the request has been accepted, rejected or on hold awaiting user input. This is so that inactive or completed requests don't needlessly fill up the edit requests category. You may also wish to use the {{EEp}} template in the response. Consider making changes first to the template's sandbox and test them thoroughly here before submitting an edit request. To request that a page be protected or unprotected, make a protection request.

This is a re-submission of the edit request to sync the template to the sandbox, which was described here: "Extended-confirmed-protected edit request on 3 September 2024". The resubmit is due to numerous edits in both the code and the documentation. The previous request was marked as "answered - not done" I believe because of mistaking an intentional error case as a genuine template case in the template's testpage.

Please note that the documentation subpage should also be synced from the sandbox. Also, the new template code requires creation of the maintenance category "Category:Template Retrieved errors", which should be concurrently created in order to trap fatal template errors.

An effort will be undertaken to make sure existing instances can handle the new code properly following sync. Thank you. 65.88.88.237 (talk) 22:52, 21 November 2024 (UTC)[reply]